[05:09] <LucidFox> Ugh, Compiz in Karmic is seriously unstable.
[05:09] <lifeless> as compared to what ? :)
[05:09] <LucidFox> Jaunty.
[05:09] <LucidFox> It keeps crashing.
[05:12] <LucidFox> Guess what, X crashed. May be the NVIDIA drivers...
[05:13] <StevenK> LucidFox: Nvidia drivers + compiz + Karmic for me has been solid ?
[05:14] <LucidFox> Not for me.
[05:14] <StevenK> File a bug with a backtrace from compiz, if one is obtainable?
[05:17] <fabrice_sp_> hmm, surelly a dumb question, but why MOTU can't upload sync from Debian to the archive as a normal package?
[05:18] <StevenK> fabrice_sp_: Because Ubuntu doesn't have a distribution called 'unstable'
[05:18] <lifeless> StevenK: well, you can override that in genchanges
[05:18] <StevenK> Ssshh!
[05:19] <lifeless> fabrice_sp_: because, over-all, we find it easier this way :)
[05:19] <lifeless> fabrice_sp_: there are a number of autoamted changes we make to syncs
[05:19] <lifeless> like the X-Original-blah fields
[05:19] <lifeless> so a sync really means 'make only the expected programmatic changes'
[05:20] <fabrice_sp_> Ok, but they could be made by a script also. I was just trying to remove some work from our lovelly archive admin :-)
[05:20] <fabrice_sp_> admins
[05:20] <lifeless> they have a script ;)
[05:21] <fabrice_sp_> seeing what they paste in the sync request bug report, I can imagine that :-)
[05:52] <micahg> what's the command to make debuild continue a build?
[05:53] <lifeless> there isn't one
[05:53] <lifeless> perhaps you mean something different to what you asked though?
[05:57] <micahg> hmmm
[06:46] <LucidFox> Why is xchat-gnome in main?
[08:31] <fcuk112> https://bugs.edge.launchpad.net/ubuntu/+source/cpufire-applet/+bug/482155 just checking if this is the correct way to do a sync: apt-get source xxx; download new source from debian and extract; cp -r debian from old source to new source; debuild -S -kxxx...  is that the correct way?
[08:38] <directhex> no. a sync re-uses the source package from debian
[08:41] <fcuk112> you mean using uscan -verbose?  what if it can't find anything?  should i be editing something to point to the correct location?
[08:52] <directhex> fcuk112, i mean a sync is something an archive admin does - literally copy-pasting the .orig.tar.gz, .diff.gz and .dsc from debian, into ubuntu
[08:55] <fcuk112> directhex: oic, so we should leave sync requests alone?
[08:56] <directhex> after making them, yes
[08:56] <fcuk112> directhex: i thought it was the same as an upgrade.
[09:02] <porthose_> fcuk112, maybe this will help https://wiki.ubuntu.com/UbuntuDevelopment/Merging  https://wiki.ubuntu.com/SyncRequestProcess
[09:21] <fcuk112> porthose_: thanks, it's a bit clearer to me now :)
[09:53] <fcuk112> heh so how is an upgrade different from a sync or merge?
[09:57] <geser> what you mean with "upgrade"?
[09:58] <fcuk112> eg. https://bugs.edge.launchpad.net/ubuntu/+source/libgphoto2/+bug/414949 https://bugs.launchpad.net/ubuntu/+source/libavg/+bug/474004 update/upgrade...
[10:00] <geser> if there is a new version of a package in Debian we cans sync it (if there are no Ubuntu changes) or merge it (when there are Ubuntu changes)
[10:01] <geser> if a new upstream version isn't yet pacakged in Debian, we can either wait till it happens or do it ourselves (as ...-0ubuntu1)
[10:01] <ari-tczew> geser: no, libgphoto2 2.4.7 isn't in Debian
[10:02] <siretart`> a change is a change is a change. - IOW: morning, folks!
[10:02] <geser> I know, therefor we have to either wait till it's there (and could sync/merge then) or do it ourselves now
[10:02] <geser> Hi siretart`
[10:02] <ajmitch> hello siretart`
[10:02] <ari-tczew> fcuk112: do you need this quickly? if not, we should fix this in Debian first, then sync
[10:03] <siretart`> hey geser & ajmitch & * :-)
[10:03] <fcuk112> ari-tczew: i'm just looking for stuff to do.  well i guess i'd better start looking at merges then.
[10:06] <fcuk112> siretart`: how long u been working with ubuntu?  i thought i saw a very old bug with your name in it =)
[10:07] <siretart`> fcuk112: I think my first own uploads were for hoary. not sure if I signed them myself or if they were sponsored at that time..
[10:08] <siretart`> I believe that they were sponsored and my key was added during the breezy cycle
[10:12] <fcuk112> old-timer =)
[10:13] <siretart`> ;-)
[10:13] <\sh> harhar...the next time I'll met siretart, I'll just say hello like "Hello Old Man" ;)
[10:13] <\sh> s/met/meet/
[10:14] <\sh> he'll kick me ;)
[10:14] <siretart`> wah! :-)
[10:14] <siretart`> \sh: btw, are you going to fosdem?
[10:16] <av`> ari-tczew, hi
[10:16] <ari-tczew> hi av`
[10:17] <av`> ari-tczew, feel free to do agg merge, or better feel free to forward any patch / delta to Debian so I can include it at next upload :)
[10:17] <av`> ari-tczew, didnt look at Ubuntu's package yet
[10:17] <av`> so not sure what's the delta actually
[10:18] <ari-tczew> ok
[10:18] <\sh> siretart, dunno...when I still do my job here, eventually...if not, then I have other priorities ;)
[10:19] <siretart`> oh
[10:19] <siretart`> i really feel like. oh well
[10:20] <\sh> siretart, first I need to fix my personal issues...tomorrow I have an appointment with a psychotherapist...I'm close to a real nice burn out...
[10:20] <highvoltage> so what exactly is the future of motu? it will continue to exist when all the archive shuffeling is done right?
[10:21] <geser> highvoltage: nobody really knows yet. There is a session scheduled at UDS to discuss this
[10:22] <highvoltage> geser: ok
[10:24] <siretart`> \sh: alles gute!
[10:25] <\sh> siretart, danke :)
[10:25] <geser> highvoltage: the session is on friday, 11am local time if you want to participate remotely
[10:26] <\sh> siretart, btw...if you and your wife do have nothing else to do on 31st Dec 2009, blank invitation to Carine and mine end of year party :)
[10:27] <highvoltage> geser: I'll come and listen in!
[10:28] <highvoltage> geser: yeah I've just been wondering if there are any knowns yet, it seems like an hour is an awefully short amount of time to discuss it, but hopefully it will work out
[10:32] <geser> I assume there will be some small discussions off-sessions and that the sessions is to collect all ideas and proposals from all interested
[10:45] <sebner> geser: ~aloha~ :)
[10:51] <geser> Hi sebner
[10:59] <ari-tczew> av`: bug 484694
[11:12] <siretart`> \sh: oh, thank you for the invitation, but we are already invited for silvester :-(
[11:33] <nicoInattendu> Hi I'm a dev on a sw called Luciole ( https://launchpad.net/ubuntu/karmic/+source/luciole). The sw was aprroved since karmic in the universe. Bur I have a major bug, who makes it unusable.
[11:33] <nicoInattendu> How I can summit a fix for the package ? I have the solution almost released
[11:35] <directhex> nicoInattendu, is the package in karmic unusable?
[11:35] <mok0> nicoInattendu: File a bug on the package in Launchpad. Then, attach the patch to the bug.
[11:36] <nicoInattendu> Yes is a bug on karmic.
[11:36] <nicoInattendu> I filled the bug https://bugs.launchpad.net/ubuntu/+source/luciole/+bug/481732
[11:37] <nicoInattendu> How I can attach a patch ?
[11:37] <mok0> nicoInattendu: You can attach a file to the bug report
[11:38] <nicoInattendu> So the modified files only ?
[11:38] <mok0> nicoInattendu: there's a button that will open up a dialogue box, then you choose your patch file
[11:38] <mok0> nicoInattendu: uhm, no
[11:38] <mok0> nicoInattendu: the output of "diff -u"
[11:39] <mok0> nicoInattendu: the output of "diff -u" old_file new_file
[11:39] <mok0> nicoInattendu: or: diff -Nur old_directory new_directory
[11:40] <nicoInattendu> ok . But I dont see the button for patch. I have only the bug attachment.
[11:40] <nicoInattendu> Ok I add the diff to the bug
[11:40] <mok0> nicoInattendu: great, thanks
[11:40] <mok0> nicoInattendu: can you paste the bug number?
[11:41] <nicoInattendu> Yes : #481732
[11:41] <mok0> bug 481732
[11:42] <mok0> nicoInattendu: At the bottom, bolow the box that says "Add comment", there's a little green "plus" and the text "Add an attachment"
[11:43] <mok0> s/bolow/below
[11:45] <nicoInattendu> ok thanks
[11:45] <mok0> nicoInattendu: do you have a fix for bug 481732 as well?
[11:57] <goshawkATPoliMi> hi, is there a more convenient way of knowing what is my arch during package creation instead of testing `uname -m`?
[11:59] <directhex> goshawkATPoliMi, dpkg-architecture ?
[12:00] <goshawkATPoliMi> directhex: how can i sue int my rulez? show i put dpkg-architecture before the test i'll do?
[12:04] <Laney> DEB_BUILD_ARCH
[12:05] <goshawkATPoliMi> thx
[12:10] <nicoInattendu> mok0 : I have a patch for both problems . I go to update It right now
[12:11] <mok0> nicoInattendu: Thanks, please be sure to mention both bugs in the comment
[12:12] <mok0> nicoInattendu: finally, subscribe ubuntu-universe-sponsors (right column, near the top)
[12:16] <nicoInattendu> I create a separate patch for both bugs? Is that correct ?
[12:16] <mok0> nicoInattendu: That's fine
[12:17] <nicoInattendu> I added ubuntu-universe-sponsors . What I do with the bug status ? I set to fix committed ?
[12:17] <nicoInattendu> For the package I meant
[12:17] <mok0> nicoInattendu: Set to "New"
[12:18] <nicoInattendu> Ok , and no assignee so ?
[12:18] <mok0> nicoInattendu: right
[12:18] <mok0> nicoInattendu: a sponsor will pick it up and get an SRU permission for it
[12:18] <nicoInattendu> Thanks a lot for the help.
[12:19] <mok0> nicoInattendu: thank you for the patches
[12:19] <nicoInattendu> I go to google SRU :)
[12:32] <LucidFox> Kubuntu doesn't install PulseAudio by default, does it?
[12:33] <AnAnt> Hello, do the builder on launchpad use sbuild or pbuilder ?
[12:35] <directhex> i think the PPA's use pbuilder? i think?
[12:37] <nicoInattendu> mok0 : Do I attach the verification-needed tag to both bugs ?
[12:38] <geser> sbuild (probably a modified version)
[12:39] <LucidFox> Both the PPA and Ubuntu archive builders use sbuild.
[12:39] <LucidFox> I think they even use the same build servers, no?
[12:39] <tsimpson> servers can either be for PPA use or for distro use
[12:40] <geser> don't know as PPA uses virtualised buildds while the official buildds use non-virtualised ones
[12:40] <tsimpson> but they can be changed between those
[12:40] <directhex> s' all virtualized anyway, so it hardly makes a difference
[13:15] <AnAnt> thanks
[13:19] <EzraR> anytime a Makefile is entered by rules the includes and variables in the makefile get initialized right?
[13:32] <goshawk> in a debian/rules i've         ifeq  ($(DEB_BUILD_ARCH),amd64) but it gives me /bin/sh: Syntax error: word unexpected (expecting ")")
[13:32] <goshawk>  what's wrong?
[13:34] <tsimpson> do you have "#!/usr/bin/make -f" as the first line of debian/rules?
[13:34] <goshawk> yes
[13:35] <goshawk> tsimpson: yes
[13:35] <tsimpson> well /bin/sh is giving the error, so it's running in a shell for some reason
[13:36] <tsimpson> "ifeq ($(DEB_HOST_ARCH),amd64)" should work
[13:37] <goshawk> so just substitute BUILD with HOST
[13:37] <goshawk> nope, same thing
[13:37] <tsimpson> well I just copied that from another makefile
[13:37] <goshawk> ifeq  (amd64,amd64)
[13:37] <goshawk> /bin/sh: Syntax error: word unexpected (expecting ")")
[13:38] <tsimpson> it should not be running in /bin/sh though, for some reason it is
[13:38] <goshawk> -.-
[13:38] <tsimpson> what if you just try "make -f debian/rules", does that give the same error?
[13:39] <goshawk> goshawk@earth:~/libtango-0.99.8+svn5149~exp1.dfsg$ make -f debian/rules
[13:39] <goshawk> dh_testdir
[13:39] <goshawk> ifeq (,amd64)
[13:39] <goshawk> /bin/sh: Syntax error: word unexpected (expecting ")")
[13:39] <goshawk> make: *** [build-stamp-ldc] Error 2
[13:40] <mok0> goshawk: if that statement is in a target and indented, it will be treated as a shell command
[13:40] <mok0> goshawk: put the statement before any targets
[13:40] <goshawk> mok0: yes it's indended in build-stamp-%:
[13:41] <goshawk> ah understood
[13:42] <Laney> goshawk: you need to have something like---
[13:42] <Laney> DEB_HOST_ARCH := $(shell dpkg-architecture -qDEB_HOST_ARCH)
[13:42] <mok0> goshawk: good :-)
[13:44] <goshawk> Laney: it worked withouth the DEB_HOST_ARCH set
[13:44] <goshawk> :D
[13:44] <goshawk> thanks mok0, tsimpson, Laney
[13:45] <Laney> ¬_¬
[13:45] <mok0> \O/
[14:04] <fcuk112> bit confused on which patch to upload, possible options are debdiff x.dsc y.dsc, diff -Nur old_dir new_dir, or the diff.gz created by debuild -S.  what are the differences?
[14:06] <directhex> fcuk112, depends on which type of upload it is
[14:06] <directhex> fcuk112, debdiff preferred for new ubuntu revisions, diff.gz for upstream updates
[14:09] <StevenK> fcuk112: And the first two options you gave ought to produce the same diff.
[14:10] <fcuk112> cool, thanks.
[14:29] <EzraR> finally i fixed this bug but it feels dirty :(
[14:47] <EzraR> this package takes a generic config file and puts it through sed to change vales depending on what platform you are running
[14:47] <EzraR> but its broken
[14:48] <EzraR> the variables dont get pased to the makefile and it leaves blanks instead of values, which causes the program to not work at all
[14:50] <EzraR> im just going to put a good default config file in debian dir install it with a .install and remove the call to the broken makefile
[14:51] <EzraR> does that sound reasonable?
[15:59] <AnAnt> Hello, could someone help me with this build error: http://launchpadlibrarian.net/35826090/buildlog_ubuntu-karmic-amd64.pcb_20091103-2%7E2.gbpedd967_FAILEDTOBUILD.txt.gz
[16:00] <AnAnt> funny thing is that it does not happen in i386 arch
[16:00] <AnAnt> why does dh_install behave differently with non-i386 archs ?
[16:30] <LucidFox> Holy cow, PulseAudio drama on Planet Ubuntu.
[16:40] <Laney> rolleyes
[16:49] <dennis_> hi@all
[16:52] <dennis_> I have a question: How do I package a program wich lib (I am packaging it too) needs the program too?
[16:53] <geser> are the programm and the library two different sources?
[16:53] <dennis_> yes
[16:54] <geser> then package the library first and let the programm build-depend on the -dev package from that library
[16:56] <dennis_> but thats the problem the library needs the program to compile
[16:56] <dennis_> and the program the library^^
[16:57] <geser> oh
[16:57] <dennis_> but they are two sources but one upstream
[16:57] <geser> how does upstream solve this bootstraping problem?
[16:58] <dennis_> I think he has his folders on his pc and so his library finds the program source
[16:58] <dennis_> folder structure
[17:00] <AnAnt> wierd could it be that dh_install -Xstring- could be not working right in non-i386 archs ?
[17:00] <geser> dennis_: does the lib need the source files from the program or the compiled program itself?
[17:01] <dennis_> geser, it needs the program source code
[17:03] <dennis_> geser, how do I package only the source code, is this possible? So maybe the lib could depend on this?
[17:07] <geser> that gets tricky and I don't have currently a good idea how to get it done
[17:09] <dennis_> geser, ok thanks. Good that I am not the only one who is wondering about this ;-)
[17:22] <\sh> dennis_, tell the guy he should write better code ;)
[17:23] <dennis_> \sh, hehe I am not quite sure if he will like that ;)
[17:25] <dennis_> If someone would like to make my day better, please have a look at my packages on revu. My name is dennis-benndorf there....
[17:25] <dennis_> I have uploaded them a few minutes ago
[18:15] <jetienne> q. where can i find the pre-removal script of a already installed package ?
[18:19] <jdong> jetienne: /var/lib/dpkg/info
[18:19] <geser> /var/lib/dpkg/info/$pkgname.prerm
[18:19] <jetienne> jdong: thanks
[18:19] <jdong> sure thing
[18:26] <corp186> At the top of the REVU site it mentions the Next REVU Day is TBD
[18:26] <corp186> what is a REVU day?
[18:28] <fcuk112> REVU is the tool used to vet and check new packages before they are uploaded in the Ubuntu system. We’re told that the idea for the day will be to green-light as many new packages as possible.
[18:30] <corp186> that's what I figured... any idea when it will be determined?
[18:30] <corp186> I have a new package in REVU, and I'm trying to figure out how to get advocates, or even just comments, on it
[19:52] <EzraR> when you purge a dpkg it should not fail because the directory is empty right?
[19:59] <StevenK> EzraR: It really depends what fails and how
[20:06] <EzraR> StevenK: dpkg: warning: while removing gw6c, directory '/etc/gw6c' not empty so not removed
[20:14] <StevenK> EzraR: Oh, that's okay.
[20:19] <EzraR> StevenK: ok...just seems un-tidy
[21:24] <lfaraone> I'm using CDBS with makefile.mk. How do I have the files that the makefile installes in $LIBDIR be moved into /lib? (LIBDIR as set by cdbs puts them in /usr/lib)
[22:30] <yml> good evening I am in the process of creating a package of uWSGI and I am a bit stuck the plan to to create it and upload it to launchpad PPA.
[22:31] <yml> but for now I am stuck at the creation step
[22:31] <yml> I am following this doc : https://wiki.ubuntu.com/PackagingGuide/Complete
[22:32] <yml> I think I have done more or less all the paperwork
[22:32] <yml> I am now at the modification of the rules
[22:34] <yml> I have created a branch where I have added the debian directory
[22:35] <yml> all this is stored here : http://bitbucket.org/yml/uwsgi/src/tip/
[22:35] <yml> it would be amazing if someone could give me a hand
[22:40] <Laney> aw
[22:41] <yml> Laney: is that for me ?
[22:41] <Laney> oh no sorry I didn't even read what you said
[22:41] <Laney> I was 'aw'ing at the latest sound rants
[22:41] <Laney> berating contributors is bad bad form
[22:41]  * Laney hugs dtchen_ 
[22:42]  * Laney reads what yml has to say
[22:42] <yml> Thanks
[22:42] <Laney> what's the problem?
[22:42] <yml> yes me too because since 9.10 my sound work again
[22:43] <yml> Laney: the main problem is in fact I reach the point where I don't know what to do next.
[22:43] <yml> I think I would need some hand holding
[22:43] <Laney> here's what you should do
[22:44] <yml> in order to compile it from source I need to run make -f Makefile.linux.py26
[22:45] <Laney> rm *.ex *.EX rules docs dirs; cp /usr/share/doc/debhelper/examples/rules.tiny rules
[22:45] <yml> where I think that I can't make the assumption that python level is 2.6
[22:45] <yml> Laney: http://bitbucket.org/yml/uwsgi/src/tip/debian/
[22:45] <Laney> yep
[22:45] <yml> here it is where I stand
[22:45] <Laney> I saw that
[22:46] <Laney> dh_make generates a load of stuff you don't want
[22:46] <yml> I have already removed the one that I am sure I don't want
[22:46] <Laney> go on, take the dive
[22:47] <yml> know I am left with the files that might be useful.
[22:47] <yml> s/know/now/
[22:48] <Laney> good
[22:49] <yml> this sounds like I am not completely off
[22:49] <Laney> so the first thing to do is to set up the build-depends and depends in the control file
[22:49] <yml> Laney: you are in the rules file, right ?
[22:50] <Laney> I'm talking about the control file
[22:50] <Laney> http://www.debian.org/doc/maint-guide/ch-dreq.en.html#s-control
[22:50] <Laney> read this
[22:52] <yml> Laney: I have added this in control : Depends: python, libxml2
[22:55] <Laney> you need to understand more clearly what to put here
[22:55] <Laney> *Build*-depends is very very important to get right first of all
[22:55] <Laney> but I'm going to bed, maybe someone else can help you
[22:55] <Laney> nn
[22:56] <yml> Laney: thanks
[22:56] <yml> I will hang around here and see if someone can help me
[23:11] <ajmitch> hey dholbach