[00:07] <cody-somerville> sparr, It doesn't appear a conflict was actually added
[00:08] <cody-somerville> http://launchpadlibrarian.net/23145334/boost_1.34.1-15ubuntu2_1.34.1-15ubuntu3.diff.gz
[00:08] <cody-somerville> http://launchpadlibrarian.net/24456406/python2.6_2.6.1-1ubuntu6_2.6.1-1ubuntu7.diff.gz
[00:21] <sparr> cody-somerville: even worse?
[00:43] <cody-somerville> sparr, It looks like maybe he fixed it
[00:43] <imbrandon> ugh, i need to relocate to cali
[00:43] <imbrandon> heh
[00:43] <cody-somerville> Ugh is right.
[00:44] <imbrandon> i really want to :)
[00:44] <cody-somerville> I wouldn't want to : (
[00:45] <imbrandon> need to get out of the midwest
[00:45] <imbrandon> wonder what the job market right now is like in san fran
[00:46]  * imbrandon opens google
[00:46] <sparr> trying to decide if im selfless enough to spend an hour removing python and reinstalling it from intrepid then jaunty to see if all parts of that bug are really fixed
[00:46] <imbrandon> where is jono where ya need him :)
[00:47] <imbrandon> sparr: go for it :)
[00:49] <dtchen> sparr: virtual machines are nice, too.
[00:50] <imbrandon> as are chroot's
[00:50] <dtchen> or {,s}chroots
[00:58] <sparr> either way i would have to either make a fresh installation, or roll back an existing installation
[00:58] <sparr> no time saved
[01:06] <dtchen> maco posted a jaunty 6 vm on thepiratebay, so at least there's a bit of time saved if you want to use that
[01:07] <dtchen> (i.e., alpha 6)
[01:08] <dtchen> hmm, it would be worth investigating offering vbox images
[01:11] <sparr> alpha 6 already has python 2.6.1, no?
[03:50] <imbrandon>  /join #drupal
[03:50] <imbrandon> err
[03:56] <ripps> I'm trying to make my ppa packages up to debian standards by including by including an package-version.orig.tar to the packages. I implemented this using cdbs tarball.mk, becuase it always seemed to ingnore the orig.tar otherwise, the problem is that whenever I try to do a test build with pdebuild, I get this error "tar: build-tree: Cannot chdir: No such file or directory"
[04:14] <Amaranth> ripps: tarball.mk is for tarball-in-tarball packages
[04:15] <ripps> How do I get dput,pdebuild,etc to recognize package.orig.tar.gz then?
[04:15] <ripps> Amaranth: ^
[04:16] <Amaranth> ripps: you create that before you build the package
[04:16] <ripps> I've tried having one in my source directory and my ../source, but dput never recognizes and uploads it.
[04:17] <Amaranth> ripps: it should be like alacarte_0.11.10.orig.tar.gz
[04:17] <Amaranth> and it should not have your debian/ dir in it
[04:17] <Amaranth> it should be a clean tarball from upstream
[04:18] <Amaranth> so for that alacarte package the package is alacarte 0.11.10-0ubuntu1 or whatever, the working directory is alacarte-0.11.10
[04:18] <ripps> Amaranth: I know, does the version matter? I use git to update my source dirs, so I tend to just copy the source and remove all the debian stuff when I make orig tarballs
[04:18] <Amaranth> the version should correspond to your package version
[04:19] <ripps> brb
[04:20] <nenolod> TheMuso: nice patches on alsa-devel
[04:21] <TheMuso> nenolod: thanks
[04:21] <TheMuso> nenolod: That script needs a bad cleanup, and I'll probably sit down and do it one day. :)
[04:31] <ripps> Amaranth: how much of the version has to correspond with the changelog? I use a fairly long version number libmpd_0.18.0+git090318-0ubuntu2~ripps
[04:32] <Amaranth> libmpd_0.18.0+git090318.orig.tar.gz
[04:45] <ripps> Amaranth: I use several debian.distro folders that I individually symlink to debian depending on which package I'm building today, but this seems to cause issues with debuild -S.
[04:51] <ripps> Amaranth: http://paste.ubuntu.com/140501/
[05:00] <ripps> Amaranth: did you see my pastebin?
[05:01] <Amaranth> ripps: Nope, but I really don't have any more time to help right now, sorry
[05:01] <Amaranth> ripps: In 2-3 hours more people should be around
[05:07] <ripps> Amaranth: I thinked I figured out an alternative, I changed my backporting script to make the debian directory a copy instead of symlink. dput seems to work correctly now.
[05:08] <ripps> Hmm... Now I need some way for the script to save changes to debian to the old debian.distro directory.
[06:14] <dholbach> good morning
[06:38] <ripps> I written a script that automates creating an orig tarball, building a source package, and uploading to a repository (using dput). I called it dshove: http://paste.ubuntu.com/140531/
[06:38] <ripps> Anything blatanly wrong with it?
[07:01] <ripps> Actually, it doesn't work right. Does anybody know how to cut the "0ubuntu1~ppa" from a version string?
[07:16] <imbrandon> morning dholbach
[07:16] <dholbach> hiya imbrandon
[07:16] <dholbach> how are you doing?
[07:16] <imbrandon> when i see you come online i know its (local)time for me to sleep :)
[07:16] <imbrandon> heh good good
[07:17] <dholbach> hehe :-)
[07:17] <imbrandon> u?
[07:17] <dholbach> sleep tight then :)
[07:17] <dholbach> I'm waking up slowly, but I'm good - thanks
[07:23] <tsimpson> ripps: something like "dpkg-parsechangelog | grep '^Version:' | sed -e 's/^Version: //' -e 's/-[^\-]*$//'"
[07:23] <ripps> tsimpson: actually, I figured it out in #ubuntu+1, my new script version: http://paste.ubuntu.com/140545/
[07:26] <tsimpson> ripps: that assumes the upstream version won't contain a '-', which is possible (if bad form)
[07:30] <ripps> tsimpson: well your version works too, so I don't see why not to add it.
[07:36]  * Amaranth seems to remember i.mbrandon saying he slept on european time
[07:45] <ripps> Should I create a launchpad bzr branch containing all the devscripts I've come up with?
[07:52] <tsimpson> ripps: you could branch ubuntu-dev-tools https://code.launchpad.net/ubuntu-dev-tools
[08:07] <ripps> https://code.edge.launchpad.net/~ripps818/ubuntu-dev-tools/ripps-scripts
[08:17] <Toadstool> good morning
[09:00] <gordonsyme> Hello
[09:00] <gordonsyme> I'm not sure if this is the right place but I have a question about packaging
[09:00] <gordonsyme> I have a Python package and some scripts
[09:01] <gordonsyme> I'm using dist-utils to build the Python package and CDBS to build the .deb package
[09:01] <gordonsyme> At this point I want to build three .deb packages.
[09:02] <gordonsyme> The Python package is to be common to each .deb package
[09:02] <gordonsyme> Actually, scratch that
[09:02] <gordonsyme> I probably really want to build four packages
[09:02] <gordonsyme> The python package and one for each script/config
[09:03] <gordonsyme> Is this possible with CDBS?
[09:06] <directhex> just write appropriate .install files and debian/control entries
[09:09] <gordonsyme> directhex: CDBS seems to do magic with the tarball from Python's dist-utils, if I add to the control file will CDBS pick this up and do the right thing?
[09:10] <directhex> dunno. Python is sluggish interpreted black magic to me
[09:10] <gordonsyme> directhex: Ah :)
[09:10] <gordonsyme> I suppose there is nothing to do but experiment, thanks for the help
[11:21] <goshawk> does anyone know why this cdbs debian/rules calls build/ldc twice? http://paste.ubuntu.com/140634/
[11:35] <hyperair> goshawk: i have no idea why, but why do you ahve a call to bash?
[11:35] <goshawk> hyperair: yes, debug
[11:35] <hyperair> lol i see
[11:35] <goshawk> hyperair: i put it to track that it's really called twice
[11:35] <goshawk> :)
[11:35] <hyperair> hahah
[11:35] <hyperair> i have no idea why
[11:36] <hyperair> what's DEB_BUILDDIR again?
[11:36] <goshawk> hyperair: the first one copies a directory in the debian build direcotry
[11:37] <goshawk> and the other one compiles the previous copied
[11:37] <hyperair> nono what doies it refer to
[11:37] <hyperair> debian/?
[11:37] <hyperair> debian/tmp?
[11:37] <hyperair> no wait that's DEB_DESTDIR
[11:37] <hyperair> so what's DEB_BUILDDIR?
[11:37] <hyperair> is it CURDIR?
[11:37] <goshawk> no, it's obj-gnu-archblablablasl
[11:37] <hyperair> .___________.
[11:38] <goshawk> it's the dir in which all in compiled by default
[11:38] <goshawk> in cdbs
[11:38] <hyperair> i see
[11:39] <hyperair> why don't you just link it
[11:39] <hyperair> ln -s tango/ $(DEB_BUILDDIR)/tango
[11:40] <goshawk> yep...
[11:40] <goshawk> i don't wanna make the tree dirty
[11:40] <goshawk> so all the changes are in DEB_BUILDDIR
[11:40] <goshawk> if i link
[11:40] <goshawk> the tree will be dirty
[11:40] <goshawk> :)
[11:41] <goshawk> build/ldc:: build-runtime-stamp
[11:41] <goshawk> build-runtime-stamp:
[11:41] <goshawk> 	cp -a tango/ $(DEB_BUILDDIR)/tango/
[11:41] <goshawk> 	cd $(DEB_BUILDDIR) && $(MAKE) runtime
[11:41] <goshawk> i'm trying this one
[11:41] <goshawk> i look in a forum
[11:41] <goshawk> maybe it works
[11:41]  * goshawk compiles
[11:44] <hyperair> that's one hell of a hack =\
[11:45] <hyperair> goshawk: you'd be better off not using cdbs
[11:46] <hyperair> goshawk: another thing.. build/ldc:: is called _after_ building ldc
[11:46] <goshawk> yep it's what i want
[11:46] <goshawk> make and then make runtime
[11:48] <goshawk> yep... i should NOT use cdbs...
[11:49] <goshawk> ok time to go for me
[11:49] <goshawk> thansk for your help hyperair
[11:49] <goshawk> see you
[11:50] <hyperair> goshawk: no prob
[12:20] <AnAnt_> Hello, is there a way to make pbuilder update from intrepid to jaunty , but get the updates from the alternate CD rather than the internet ?
[12:35] <directhex> AnAnt_, much easier to create a new pbuilder
[12:35] <AnAnt_> directhex: well, same question, how do I make it get the packages from CD instead of internet ?
[12:35] <hyperair> deb-cdrom?
[12:35] <hyperair> or something?
[12:36] <directhex> you should be able to use the cd in your --mirror line
[12:37] <AnAnt_> directhex: what makes new pbuilder easier that --update ?
[12:37] <directhex> updates may not end up being 100% clean between releases
[12:38] <directhex> if your pbuilder is unclean, you defeat the purpose of using it
[12:39] <AnAnt_> directhex: so I use --create , and it will overwrite the existing base.tgz ?
[12:40] <directhex> if your system is set up to only use one base.tgz, then probably
[12:40] <AnAnt_> directhex: will that remove packages already existing in  /var/cache/pbuilder/result/ ?
[12:41] <hyperair> AnAnt_: the only way to remove those is rm them manually =p
[12:42] <AnAnt_> ok, good
[12:42] <AnAnt_> thanks
[14:59] <cbx33> anyone know who is going GSoC this year for Ubuntu?
[15:02] <jpds> cbx33: I don't think we are.
[15:02] <cbx33> oh
[15:04] <jpds> There's stuff at https://wiki.ubuntu.com/GoogleSoC2009 , no idea what the status is.
[15:05] <cody-somerville> Ubuntu isn't participating
[15:06] <cbx33> ahh ok
[15:06] <cbx33> thanks guys
[15:10] <thekorn> wow, that's surprising, I'm sure I've seen a list with ubuntu beeing one of the accepted organisations for this year
[15:14] <stefanlsd> Anyone familiar with a QT .ui file. Im trying to use <includehints> and i'm getting Unexpected element includehints.
[15:17] <bddebian> Heya gang
[16:33] <goshawk> in a debian/rules that use cdbs, what is the difference between build/foo: and build/foo:: ?
[16:37] <directhex> :: appends to an existing rule
[16:38] <goshawk> directhex: thanks :)
[16:45] <goshawk> so why if i redefine CMakeCache.txt:: if get debian/rules:13: *** target file `obj-x86_64-linux-gnu/CMakeCache.txt' has both : and :: entries.  Stop.
[16:45] <goshawk> ?
[17:03] <kees> jpds: why do you have these lines in the pidgin profile?
[17:03] <kees> +       deny /etc/kernel rm,
[17:03] <kees> +       deny /etc/passwd rm,
[17:04] <jpds> kees: Cos pidgin kept asking for them and I wanted to silence it.
[17:04] <kees> pidgin was asking for "m" on passwd ?
[17:04] <jpds> Yeah.
[17:04] <kees> that's very very odd.
[17:05]  * kees will poke at that -- that's either a bug in pidgin or a regression in the kernel.
[17:05] <kees> jpds: you did this on i386 or amd64?
[17:06] <jpds> kees: i386, lemme check my logs again.
[17:06] <kees> cat you give me the output of two commands:  sudo cat /proc/1/personality; cat /proc/$$/personality
[17:07] <kees> I would expect both to be "00000000"
[17:07] <jpds> kees: http://paste.ubuntu.com/140802/
[17:08] <jpds> kees: Both are: "00000000" - latest Jaunty.
[17:08]  * kees scratches his head
[17:09] <kees> okay, I'll poke around some more later today
[17:18] <jpds> kees: http://paste.ubuntu.com/140818/
[17:19] <kees> jpds: right, getpwuid shouldn't be mapping "m".
[17:19] <kees> can you cat the personality of your pidgin process?
[17:20] <jpds> Same, 0000000
[17:20] <kees> totally weird!
[17:21] <kees> do you have any warnings in your logs for cups complaining about the need for "m" on /etc/passwd when it prints?
[17:21] <jpds> Haven't used cups.
[17:23] <Legendario> I am having problens when trying to create a package... can ayone help me out with that: http://ubuntu.pastebin.com/d5c95419d
[17:40] <goshawk> Legendario: i don't see any error line from the source, except the one by pbuilder
[17:40] <Legendario> goshawk... i am having another problem now... on debuild...
[17:43] <Legendario> no... not at all
[17:43] <goshawk> let me see
[17:43] <Legendario> goshawk
[17:43] <Legendario> could debuild it again
[17:43] <Legendario> the problem is on compiling the package with pbuilder really
[17:45] <Legendario> goshawk, what king of error can it be?
[17:45] <goshawk> Legendario: maybe some make returns a value which is recognized as an error to pbuilder
[17:47] <Legendario> goshawk, do u think this bug maybe affecting my build? https://bugs.launchpad.net/ubuntu/+source/cdbs/+bug/138981
[17:47] <Legendario> but i don't see that going on in it
[17:48] <Legendario> cause i am not using cdbs...
[17:48] <goshawk> Legendario: i don't think so
[17:48] <goshawk> if you were affected by the same problem
[17:48] <goshawk> debuild should not work too
[17:49] <Legendario> yeah... everything ok with debuild
[17:49] <Legendario> the problem seem to be when compiling this libweed...
[17:54] <Legendario> goshawk, could give me any suggestion? I am lost?
[17:54] <Legendario> lost!
[17:55] <goshawk> can you please past me the output of debuild?
[17:55] <goshawk> paste
[17:58] <Legendario> goshawk, http://ubuntu.pastebin.com/d591711ea
[17:59] <goshawk> Legendario: with debuild -S -sa you are preparing a source package
[17:59] <goshawk> you are not compiling
[17:59] <goshawk> to compile
[18:00] <goshawk> just run debuild
[18:00] <goshawk> but i think
[18:00] <goshawk> that you will have to download a lot of dependencies
[18:00] <Legendario> i think i have done that already... gonna try againg
[18:01] <Legendario> goshawk, error. gonna paste for u
[18:02] <goshawk> Legendario: is it a new package the one you are trying to compile?
[18:02] <Legendario> goshawk, http://ubuntu.pastebin.com/dada0e48
[18:02] <Legendario> yes
[18:03] <goshawk> Dependências de construção não satisfeitas: libgtk2.0-dev libsdl1.2-dev libtool automake1.9
[18:03] <goshawk> i'm not spanish
[18:03] <goshawk> but it says to install those packages ;)
[18:03] <imbrandon> looks like missing build deps
[18:03] <Legendario> goshawk, it is not spanish. it is portuguese... :-)
[18:04] <goshawk> ah sorry :D
[18:04] <imbrandon> sudo apt-get install libgtk2.0-dev libsdl1.2-dev libtool automake1.9
[18:04] <imbrandon> :)
[18:05] <Legendario> goshawk, it's been a time since I last tried to build a package... I didn't need to do this in the past... pbuilder used to download those packages to the check enviromment... Did things changed?
[18:05] <goshawk> no
[18:05] <goshawk> Legendario: the things are the same
[18:06] <goshawk> Legendario: but we can figure out what's the error in pbuilder
[18:06] <goshawk> so you have two solutions
[18:06] <goshawk> 1) find a log in which there is the error (from pbuilder's logs)
[18:06] <goshawk> 2) compile it in your environment with debuild
[18:06] <Legendario> goshawk, i am downloading them... let's just wait a bit...
[18:07] <Legendario> my connection is kind of slow
[18:07] <goshawk> in the meantime try to find the error in the pbuilder logs
[18:08] <Legendario> goshawk, where is the log located?
[18:09] <goshawk> Legendario: it depends if you are using pbuilder or pbuilder-dist
[18:09] <Legendario> pbuilder
[18:10] <goshawk> the first one is in goshawk@earth:/var/cache/pbuilder$ ls
[18:10] <goshawk> aptcache  build  pbuildd  pbuilder-mnt  pbuilder-umlresult  result
[18:10] <goshawk> /var/cache/pbuilder
[18:10] <goshawk> in build
[18:10] <goshawk> you should find the build logs
[18:10] <goshawk> no, wrong
[18:11] <Legendario> yeahh, i am not finding them there...
[18:12] <Legendario> goshawk, i've made a search for *.log in the /var/cache/pbuilder but found no thing at all
[18:13] <goshawk> yep, i said that it's wrong that's not the correct dir
[18:14] <goshawk> sorry i don't know
[18:14] <Legendario> goshawk... i don't know if there is such a log...
[18:15] <goshawk> pbuilder-dist does it :P
[18:16] <Legendario> well, i've never use pbuilder-dist... how diferent is that?
[18:16] <goshawk> pbuilder-dist is just a wrapper that makes you able to have multiple pbuilders for multiple distributions
[18:16] <goshawk> you create a smb link in /usr/local/bin of pbuilder-dist named pbuilder-intrepid for example
[18:16] <goshawk> pbuilder-intrepid create
[18:17] <goshawk> pbuilder-intrepid build file.dsc
[18:17] <goshawk> it builds
[18:17] <goshawk> like normal pbuilder
[18:17] <goshawk> pbuilder-sid build file.dsc builds for debian sid
[18:17] <goshawk> and so on
[18:18] <Legendario> i see here it really has the option to log or not the builds
[18:19] <Legendario> but does it change debian/changelog?
[18:19] <Legendario> for the chosen distro?
[18:20] <goshawk> no
[18:20] <goshawk> it justs tests build-depends
[18:20] <goshawk> in different environments
[18:21] <goshawk> it's not used in production where you need to do packages to distribute, pbuilder is to check that the build depends are satisfied
[18:21] <Legendario> but u must have a chroot envirommento for each distro, right?
[18:21] <goshawk> yep
[18:21] <goshawk> pbuilder-intrepid create
[18:21] <goshawk> pbuilder-sid create
[18:21] <goshawk> and so on
[18:22] <Legendario> goshawk, tried to debuild here
[18:22] <Legendario> do u want the hole thing or just the end...
[18:23] <goshawk> start from the end :)
[18:26] <Legendario> goshawk, big one: http://ubuntu.pastebin.com/d31c1394e
[18:28] <goshawk> well
[18:28] <goshawk> finally
[18:28] <goshawk> :)
[18:28] <goshawk> from line 420
[18:29] <goshawk> they are all errors
[18:29] <goshawk> /home/kemel/Downloads/source/Empacotados/Lives2/lives-0.9.9.7/libweed/weed.c:260: undefined reference to `weed_malloc'
[18:29] <goshawk> the sources are broken IMHO
[18:29] <Legendario> i see, but i can't know why...
[18:29] <goshawk> it's reference problem
[18:30] <goshawk> it seems that in weed.c some libraries are missed
[18:30] <goshawk> weòò
[18:30] <goshawk> well
[18:31] <Legendario> goshawk, what is IMHO?
[18:31] <goshawk> only that file has undefined reference for weed_malloc weed_memcpy weed_free, memset and many otehrs
[18:31] <goshawk> IMHO = In my honest opinion
[18:31] <quentusrex> Can someone tell me how I can more quickly get a patch into a package?
[18:32] <broonie> humble, normally.
[18:32] <quentusrex> or how I can update my own package while I wait?
[18:32] <Legendario> goshawk, is that an upstream problem?
[18:32] <goshawk> ye
[18:32] <goshawk> yep
[18:32] <quentusrex> I have hit an issue with an upstream(debian package) bug. I have found the proper patch from the software project, but now it needs to be applied to the package.
[18:33] <quentusrex> What do I do now?
[18:33] <Legendario> goshawk, but i believe the author has no problem to compile it...
[18:33] <goshawk> Legendario: are you sure that you have the correct version? i mean the same he compiled
[18:34] <broonie> quentusrex: Does the package fail to build in Debian?
[18:34] <Legendario> goshawk, i don't know... at least it is the last stable version that is available
[18:35] <quentusrex> broonie: the package does not fail to build
[18:35] <Legendario> i am in touch with him... gonna ask him tough
[18:35] <quentusrex> it fails to properly detect the capabilites of the server...
[18:35] <quentusrex> it detects all processors as 686, and not about to detect x86_64....
[18:36] <broonie> quentusrex: Is there an existing Debian bug for this issue?
[18:36] <quentusrex> I just filed it
[18:36] <quentusrex> broonie: it is a brand new bug...
[18:36] <broonie> quentusrex: Then send the patch to the bug as well.
[18:36] <quentusrex> debian only applied one of the two patches...
[18:36] <quentusrex> I did :) http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521785
[18:37] <quentusrex> now what?
[18:37] <quentusrex> I'm a bit worried because my whole network is down because of this bug... :(
[18:38] <broonie> Wait for the maintainer to react.
[18:38] <quentusrex> :)
[18:43] <quentusrex> broonie: could you walk me through modifying the package myself? I have compiled it locally to install it
[18:43] <quentusrex> now I just need to download the source, then compile and reinstall it myself...
[18:45] <broonie> This article has a walkthrogh of rebuilding: http://www.debian-administration.org/articles/20
[18:45] <broonie> When you download the source check if there's a directory debian/patches in the source.
[18:49] <quentusrex> ok
[19:10] <Legendario> goshawk, tell me something... i included a file called GETTING.STARTED on the debia/docs. Where is it going to be included in the end? /usr/share/doc/package-name/GETTING.STARTED?
[19:11] <goshawk> no
[19:11] <goshawk> Legendario: in debian.docs you put the filenames
[19:12] <goshawk> Legendario: that you want to have in /usr/share/doc/ldc
[19:12] <goshawk> oops
[19:12] <goshawk> remove ldc
[19:12] <goshawk> :)
[19:13] <goshawk> eg
[19:13] <goshawk> goshawk@earth:~/Documents/Projects/MOTU/ldc/d1/ldc-0.9/debian$ cat docs
[19:13] <goshawk> CMakeLists.txt
[19:13] <goshawk> readme.txt
[19:13] <goshawk> readme.txt
[19:13] <goshawk> goshawk@earth:/var/cache/pbuilder$ cd /usr/share/doc/ldc/
[19:13] <goshawk> goshawk@earth:/usr/share/doc/ldc$ ls
[19:13] <goshawk> changelog.Debian.gz  CMakeLists.txt.gz  copyright  readme.txt
[19:13] <goshawk> goshawk@earth:/usr/share/doc/ldc$
[19:14] <Legendario> goshawk, no, i just want to write on the README.debian that there is this file called GETTING.STARTED, which is actually a FAQ and tell the location of it
[19:15] <Legendario> goshawk, so i suppose it is going to be /usr/share/doc/package-name/GETTING.STARTED, right?
[19:15] <goshawk> if ypu put his name in debian/doc yes
[19:16] <Legendario> goshawk, that's what i did... ;-) thanks...
[19:17] <lfaraone> quadrispro: thanks btw for updating those sugar packages in jaunty.
[19:17] <Legendario> goshawk, well, i asked the author to try to compile it himself and see if he gets the same problem...
[19:20] <goshawk> Legendario: ;)
[19:21] <Legendario> goshawk, thanks a lot man. gotta go now...
[19:21] <goshawk> you are welcome Legendario
[19:21] <goshawk> Legendario in italian is legend :)
[19:22] <goshawk> yep, with one more g
[19:22] <Legendario> goshawk, are u italian?
[19:22] <goshawk> yep
[19:22] <Legendario> goshawk, half of my family is too...
[19:22] <Legendario> from Trento...
[19:22] <goshawk> ah ;)
[19:22] <Legendario> my mothers side
[19:22] <goshawk> the world is little ;)
[19:23] <Legendario> and the italians travel a lot. ;-)
[19:23] <Legendario> and end up coming to Brazil :D
[19:24] <Legendario> goshawk, well see u. Bye
[19:50] <quadrispro> lfaraone: :) it's a pleasure
[20:03] <lionel> could someone from motu-sru have a look at bug #220136 ?
[20:03] <lionel> cody-somerville ? :)
[20:14] <cody-somerville> lionel, acked
[20:14] <lionel> cody-somerville: thanks!
[20:54] <Legendario> goshawk, can i bother u a second?
[20:54] <goshawk> Legendario: yep
[20:55] <Legendario> a new file appeared at the debian folder after i tryed to debuild it
[20:55] <Legendario> it's calle package-name.debhelper.log
[20:56] <goshawk> seems interesting
[20:56] <goshawk> it's the debhelper log probably
[20:56] <goshawk> are you using cdbs?
[20:56] <Legendario> thereis only this inside: dh_installdirs
[20:56] <Legendario> not using cdbs
[20:57] <Legendario> goshawk, any hint?
[20:57] <goshawk> no
[20:57] <goshawk> btw it's right
[20:57] <goshawk> you don't call debhelper
[20:57] <goshawk> your package dies before reaching all the dh_* scripts
[20:57] <goshawk> so it's normal that a log of all the dh_* scripts is empty
[20:58] <goshawk> at least it's logical
[21:01] <Legendario> goshawk, but my package is dies on build-stamp, doesn't it?
[21:01] <Legendario> dies, sorry
[21:01] <goshawk> yep
[21:01] <goshawk> it dies while building for a problem in the source IMHO
[21:02] <Legendario> so some dh_scripts are called
[21:02] <Legendario> and why is this specific script appearing in the debhelper log
[21:02] <Legendario> ?
[21:05] <Legendario> goshawk
[21:05] <goshawk> wait i read now
[21:05] <goshawk> :)
[21:06] <goshawk> i think your debian/rules sets it
[21:08] <Legendario> goshawk, it does, but is that what may be causing the problem?
[21:10] <goshawk> i dont think
[21:11] <goshawk> phone
[21:20] <Legendario> goshawk, ok
[21:23] <goshawk> back
[21:25] <Legendario> goshawk, so that doesn't offer any help at all, right?
[21:25] <goshawk> yep
[21:26] <goshawk> the error is reported is that the linker does not know which function to reference for the function names it founds
[21:27] <kees> jpds: weird, I can't reproduce the "m" thing for pidgin on jaunty i386
[21:27] <goshawk> Legendario: to make a final prood
[21:27] <goshawk> proof
[21:28] <goshawk> Legendario: compile it from scratch
[21:28] <jpds> kees: Nothing new in my logs, very odd.
[21:28] <goshawk> without debian support
[21:28] <Legendario> goshawk, ok. i will try
[21:28] <Legendario> thanks again :-)
[21:28] <goshawk> Legendario: let me know :)
[21:29] <goshawk> i'm here everyday :P
[21:29] <Legendario> goshawk, ok
[21:32] <Legendario> goshawk, but i think that what i am doing it is packaging from scratch, actually
[21:32] <Legendario> :P
[21:33] <goshawk> yep, but since you still dubt that maybe debian/rules is wrong it's the final proof that the source are broken :)
[21:35] <jpds> kees: Pushed up fixed profile.
[21:37] <Legendario> goshawk, ok... thanks once again
[21:38] <goshawk> good nights
[23:19] <directhex> jcastro, ping?
[23:29] <jcastro> directhex: yo
[23:30] <directhex> jcastro, can we take it to /msg?
[23:30] <jcastro> yep
[23:40] <RyanK> hmm.. haven't seen ubuntu in years, but picked it up over the weekend and impressed with the changes! Want to help, but a bit overwhelmed with where to start!
[23:46] <maxb> Find a bug which bothers you and see it through to being fixed? :-)
[23:48] <directhex> yeah, that's the best way to get stuck in
[23:48] <directhex> it teaches you all the tools, and gives you both s specific thing to work on and tangible results
[23:48] <RyanK> well, I looked through the bugs (and there's a lot) and they seemed overly complex to just getting started
[23:49] <RyanK> was going to work through the example recipies to get familiar, but the issues I was finding seem to require a lot of knowledge of ubuntu
[23:50] <directhex> there are a lot of core concepts you need to be grounded in to feel comfortable working from scratch
[23:50] <directhex> if it's any consolation, i'm still constantly finding things i don't know
[23:50]  * Laney resists smutty comment
[23:51] <jdong> *cough* :)
[23:52] <RyanK> well.. the Universe/Multiverse bitesize bugs from https://wiki.ubuntu.com/MOTU/TODO/Bugs was what I was looking at
[23:52] <RyanK> is that a good recommended starting place?
[23:52] <Laney> the bitesize tag on LP is probably better
[23:53] <Laney> oh, that's a search link
[23:54] <Laney> RyanK: There's a couple on there with mentors listed
[23:54] <Laney> you could speak to those people
[23:55] <RyanK> ahh.. didn't notice the red plus sign... cool!
[23:55] <Laney> there's probably a way to search for all such bugs
[23:56] <RyanK> planning on wiping a laptop tonight and throw the 9.04 beta on there and dig in (assuming everything works on that laptop, reporting any issues, of course!)
[23:56] <Laney> https://edge.launchpad.net/~ubuntu-dev/+mentoring