[01:49] <DiegoTc> hi
[01:49] <DiegoTc> Is someone available right now?
[01:57]  * mhall119 is available but not a motu
[02:26] <nigelb> !ask | didrocks
[02:26] <nigelb> ugh!
[02:26] <nigelb> !ask | DiegoTc
[02:29] <wrapster>  in the postinst script i cannot execute how do i execute shell commands?coz one in particular called 'update-ca-certificates' fails if written inside the postinst scrip
[02:30] <wrapster> but anywhere else if i write its working fine.
[02:30] <wrapster> http://pastie.org/900511
[02:33] <sistpoty> wrapster: got the package a depends on ca-certificates?
[02:55] <wrapster> sistpoty: one sec let me see
[02:57] <wrapster> yes there are quite a few pkgs that depened on ca-certificates
[02:58] <wrapster> sistpoty: but why is that important?
[02:59] <sistpoty> wrapster: if the packages uses a command found in ca-certificates (i.e. update-ca-certificates), it needs to have the package providing the command installed prior to it
[02:59] <wrapster> sistpoty: apt-get install ca-certificates is giving me this error http://pastie.org/903294
[03:00] <wrapster> hmm.. ok let me verify that .. one sec pls.
[03:00] <wrapster> sistpoty: yes that pkg is already installed.
[03:02] <sistpoty> wrapster: then, s.th. went wrong? not too sure how to debug that in the first place, I guess running the commands of the postinst by hand could shed further lights
[03:02] <sistpoty> s/lights/light/
[03:04] <wrapster> sistpoty: yes i kinda did that and was able to see that the shell command here ' http://pastie.org/900511 ' that is update-ca-certificates is the probelm.. I was able to deduce so by actually removing that line from the postinst script .. then the pkg was installed cleanly. so its definitely the case with this cmd.
[03:04] <sistpoty> wrapster: did you check what went wrong with that command yet?
[03:05] <wrapster> sistpoty: i cannot find that out.. coz i ran the cmd independently and it works fine.
[03:05] <wrapster> its only within the script.
[03:06] <wrapster> and secondly 'update-ca-certificates' binary comes from 'ca-certificates' pkg .. and this pkg's postinst script itself is calling the update-ca-certificate cmd ... Will this cmd be initialized by the time postinst is run?
[03:06] <wrapster> could that be the reason?
[03:08] <sistpoty> wrapster: there's no state of initialized/uninitialized for a *command*, however the command might need data provided by a package
[03:08] <wrapster> hmm..
[03:08] <wrapster> but i see it working on a lot of debian machines already.
[03:09] <wrapster> my own ubunutu has it working.
[03:09] <wrapster> this pkg working.. its on another machine im trying to install this and its failing.
[03:09] <sistpoty> wrapster: just a wild guess, but maybe update-ca-certificates checks some data and fails if e.g. a certificate is not in the right format?
[03:10] <wrapster> hmm.. let me check that..
[03:10] <wrapster> thanks..
[03:10] <sistpoty> yw
[03:40] <DiegoTc> I got this erro https://wiki.ubuntu.com/PackagingGuide/Complete when I  am doing the debuild command
[03:40] <DiegoTc> I am really lost here :S
[03:40] <ScottK> What error?
[03:42] <DiegoTc> Scottk this one http://pastebin.com/qSuibTZR
[03:43] <DiegoTc> sorry i got confuse of link
[03:43] <ScottK> No problem.  Looking
[03:45] <ScottK> DiegoTc: Does your package build-depend on qmake?
[03:45] <DiegoTc> Scottk yes it does, its a small app I did using QT4c++
[03:45] <ScottK> Is qmake installed?
[03:46] <ScottK> What is "No hay ninguna regla para construir el objetivo" in English?
[03:47] <DiegoTc> "there is no any rule for building the objective"
[03:47] <DiegoTc> Scottk I suppose its build because I am compiling it on my computer right now
[03:48] <ScottK> I'm not sure exactly what the problem is.
[03:49] <DiegoTc> :S
[03:49] <ScottK> What happens if you run make -f debian/rules clean from the source directory of your package?
[03:50] <DiegoTc> ScottK, you mean to do this  make -f debian/rules
[03:50] <ScottK> DiegoTc: Close.
[03:50] <ScottK> make -f debian/rules clean
[03:50] <ScottK> That should just run the clean rule.
[03:51] <ScottK> Which is where the error you showed me was.
[03:53] <DiegoTc> ScottK,  HERE http://pastebin.com/hhbWMJWn
[03:53] <DiegoTc> i put the translation down
[03:54] <ScottK> Right.
[03:54] <ScottK> So I guess there is some qmake problem here.
[03:54] <ScottK> Unfortunately it's not something I know about.
[03:56] <DiegoTc> ScottK, so what you will recommend me ??
[03:57] <ScottK> Figure out why you don't have the Makefile parts that qmake is saying are needed.  I have no idea what those are.
[03:57] <ScottK> Sorry I can't be more help.
[03:58] <DiegoTc> thanks
[04:16] <DiegoTc> ScottK,
[04:17] <DiegoTc> ScottK, I found this link http://pkg-perl.alioth.debian.org/debhelper.html#module__build__compat
[04:17] <DiegoTc> and i add this to the rules debhelper 7.0.17.
[04:19] <DiegoTc> and when i do the  sudo make -f debian/rules clean I got this message http://pastebin.com/VVjqTa6A
[04:32] <thewho> hi all
[04:43] <kobrien> hey guys
[04:43] <kobrien> looks like debian fixed the public_html problem Bug: 554903
[04:44] <kobrien> how exactly do their fixed get into our builds?
[04:44] <ScottK> Bug 554903
[04:45] <kobrien> I can make a patch if that helps?
[04:45] <ScottK> kobrien: Generally once the new package is in Debian, someone would prepare an updated merge.
[04:45] <ScottK> kobrien: It would.
[04:46] <ScottK> The most preferred patch would be a merge debdiff (unless their upload has other invasive changes).
[04:46] <ScottK> But any form of patch attached to a bug would be a help.
[04:46] <kobrien> ScottK: how would I go about "merge debdiff". take their debdiff and apply?
[04:47] <ScottK> !merge
[04:47] <ScottK> Have a look there.
[04:47] <kobrien> ScottK: will do. thanks
[04:57] <kobrien> ScottK: when I run grab-merge it fails
[04:58] <kobrien> with "unexpected operator"
[04:59] <RoAkSoAx> kobrien, as ../grab-merge.sh <package_name> ?
[04:59] <kobrien> yes
[04:59] <kobrien> well
[04:59] <kobrien> ./grab-merge.sh php5
[05:00] <kobrien> in an empthy dir, correct?
[05:00] <kobrien> empty*
[05:01] <RoAkSoAx> kobrien, yep. But check in merges.ubuntu.com/universe.html or merges.ubuntu.com/main.html for which packages are available for ".grab-merging"
[05:03] <kobrien> it's really libapache2-php5 I'm after, but it's not listed
[05:04] <RoAkSoAx> kobrien, libapache2-mod-php5 ?
[05:04] <ScottK> RoAkSoAx: That's only work for things in Testing.
[05:05] <ScottK> He's looking for something just uploaded.
[05:05] <kobrien> ScottK: please advise
[05:06] <kobrien> RoAkSoAx: yes
[05:06] <RoAkSoAx> ScottK, since he was using grab-merge that's why I thought he was looking to merge a package from debian in testing :)
[05:07] <ScottK> kobrien: You mean libapache2-mod-php5?
[05:07] <kobrien> ScottK: yes
[05:07] <ScottK> That's part of the php5 source package.
[05:07] <RoAkSoAx> kobrien, poh o just read backlog. You would have to do: 'apt-get source libapache2-mod-php5', which is actually in php5 source package. So it will download the source package and you can start working from there
[05:08] <kobrien> RoAkSoAx: ok so
[05:08] <kobrien> that's how I'd normally patch, but debian have released a fix, I was gonna merge their fix, but I can easily just implement it in a patch
[05:08] <kobrien> of my own
[05:09] <ScottK> Better to get Debians.
[05:09] <ScottK> (for consistency)
[05:09] <RoAkSoAx> yep
[05:09] <kobrien> right, so can I apply their debdiff directly?...how to proceed?
[05:10] <ScottK> kobrien: I don't see anything new uploaded yet: http://packages.qa.debian.org/p/php5.html
[05:10] <ScottK> "There are 64 open security issues, please fix them."
[05:10] <kobrien> basing off this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571714
[05:11] <ScottK> kobrien: We should have that in Lucid already
[05:11] <ScottK> Are you wanting a fix for Karmic?
[05:12] <kobrien> nope, Lucid
[05:14] <ScottK> We already it then (at least in theory).
[05:14] <ScottK> It could have been a bad merge.
[05:15] <ScottK> So I'd grab the Ubuntu source (apt-get soure php5) and then check too see if it's there already.
[05:15] <kobrien> righteo
[05:15] <kobrien> 2 secs
[05:31] <kobrien> ScottK: It appears that in the current lucid version, the behaviour of not serving php from public_html is known. It gives details of how to enable it, but it's not default. surely it should be
[05:32] <kobrien> do you agree?
[05:32] <ScottK> kobrien: I'd ask zul on #ubuntu-server when he's working tomorrow.
[05:32] <ScottK> Personally I've never failed to avoid dealing with php and prefer to keep it that way.
[05:33] <kobrien> ScottK: ;) no probs. I'll see what I can do. The fix is easy, but I'll consult zul. thanks
[05:56] <nigelb> ok, so in my .pbuilderrc I have this line UBUNTU_MIRROR="http://ubuntuarchive.hnsdc.com/" unfortunately, pbuilder is not using that mirror even after source .pbuilderrc
[05:57] <nigelb> any thoughts on what I'm doing wrong ?
[06:00] <ScottK> I don't see any mention of UBUNTU_MIRROR in man pbuilder
[06:00] <nigelb> I use this https://wiki.ubuntu.com/PbuilderHowto#Multiple%20pbuilders
[06:05] <ScottK> OK.
[06:05] <nigelb> and its still not working :D
[06:05]  * kobrien compiles the hell out of php
[06:10] <ScottK> nigelb: If you want to figure out how to get this one to build, that'd be nice too: https://launchpad.net/ubuntu/+source/php-imlib/0.7-1build1
[06:12] <nigelb> ScottK, was that for me or kobrien ?
[06:12] <kobrien> probably me, I'll look into ot
[06:12] <ScottK> nigelb: Actuall kobrien.  Thanks.
[06:12] <ScottK> ../
[06:12] <ScottK> y
[06:12] <kobrien> :)
[06:12]  * ScottK goes to bed.
[06:12] <kobrien> nn
[06:12] <ScottK> Good night.
[06:12] <nigelb> good night :)
[06:12] <kobrien> thanks for the help
[06:14] <kobrien> ooh, that bug looks good.
[06:15] <wrapster> vi and vim are not a part of any pkg?
[06:16] <nigelb> it is
[06:16] <wrapster> dpkg -S didnt show anything.
[06:16] <wrapster> why so then?
[06:16] <nigelb> you dont have it installed?
[06:17] <kobrien> it lists fine when it's installed
[06:18] <kobrien> wrapster: install with "sudo apt-get install vim"
[06:18] <wrapster> kobrien: and how about vi?
[06:18] <kobrien> hmm, can't vim work in vi mode
[06:19] <nigelb> vim-tiny perhaps?
[06:19] <wrapster> no..
[06:19] <wrapster> Im acutally curious to know about 'update-alternatives' for my own reasons.. thats why asking you guys.. as i see that both vi and vim point to the same file eventually.
[06:20] <wrapster> and that is 'vim.basic'
[06:20] <kobrien> :set compatible?
[06:20] <kobrien> I think that'll put vim in vi mode
[06:21] <wrapster> kobrien: no i dont have issues using the editor nor do i want info on using it.. I want to know just how both vi and vim manage to point to the same file.
[06:21] <wrapster> i need to just take a look at it thats all.
[06:22] <kobrien> oh...cause vi isn't packaged. only vim is availible but it acts just like vi
[06:22] <kobrien> if you want it to. that's why both point to it
[06:22] <wrapster> ah.. ok..
[06:22] <wrapster> I got that..
[06:24] <wrapster> kobrien: so by default debian does not ship vi at all.. Is that what your telling me?
[06:24] <nigelb> yup
[06:24] <wrapster> thank you.
[06:24] <wrapster> guys
[06:24] <kobrien> yup
[06:24] <kobrien> cool
[06:24] <kobrien> there's no need as vim provides its functionality
[06:26]  * kobrien still compiling...
[07:07] <kobrien> if I make a patch, is it useful for me to upload more than a debdiff?
[07:09] <persia> kobrien: Not really, no.  Also, does your patch fix an issue generally, or is it just an aggregation of currently available patches?
[07:10] <kobrien> it is a single fix for default configuration of apache2
[07:11] <persia> Ah, for that just the debdiff is fine then.
[07:13] <kobrien> cool, thanks.
[07:20] <nigelb> how do I unapply a patch?
[07:20] <nigelb> is there a way?
[07:20] <maco> nigelb: diff -r, i think
[07:20] <persia> What sort of patch?
[07:20] <nigelb> well, I was going to patch with quilt, but forgot quilt add
[07:20] <nigelb> so, now I have to remove applied patch and do a quilt add and then patch again
[07:21] <persia> How did you apply the patch?
[07:22] <nigelb> patch -p1 < blablabla.pach
[07:22] <maco> brain not working sorry
[07:23] <nigelb> maco, I did wonder
[07:23] <maco> nigelb: have you learned about "quilt import" yet?
[07:23] <nigelb> um, no
[07:23]  * nigelb goes to man pages
[07:23] <nigelb> ah, never knew this one.. this is cool :)
[07:24] <persia> diff -r ought work for that case, but quilt import is better.
[07:24] <nigelb> so no need to do a quilt new when using quilt import?
[07:25] <persia> Right.
[07:25] <persia> Instead, you need to use -f or -d when you want not to have a new patch.
[07:26] <maco> persia: you mean like if you want to combine 2 or 3 external patches into 1 quilt patch?
[07:26] <persia> maco: Or you want to merge/overwrite some quilt patch with some external patch.  man quilt :)
[07:27] <maco> ooh alrighty. i only ever used it for adding 1 patch at a time
[07:27]  * nigelb glares at maco 
[07:27] <nigelb> you taught me quilt :D
[07:27] <maco> nigelb: what?
[07:27] <maco> nigelb: i taught you a long way round?
[07:27] <nigelb> yeah
[07:28] <maco> nigelb: was possibly before i learned about import
[07:28] <nigelb> ahhh
[07:29] <maco> ive only done the new, add, edit, <manually edit things without the patch command>, refresh thing once, i think
[07:30] <maco> having a patch to import is much more common
[07:30] <nigelb> generally I did new, add, (then manually patch -p1...), quilt refresh
[07:30] <maco> yeah thats what i did til i learned about import
[07:31] <nigelb> so if the patch is improperly formatted, I guess I have to manually do it
[07:31] <maco> hmmm? well i hope you dont normally add patches that dont apply...
[07:32] <nigelb> I'm doing patch review... well.. a lot of patches dont apply properly
[07:32] <maco> yeah
[07:32] <maco> patch --dry-run
[07:32] <nigelb> I do that first always
[07:33] <nigelb> I guess I have to manually correct the directory structure
[07:34] <persia> Did you use the right -pN argument?  That's my most frequent mistake.
[07:35] <nigelb> naah.  the patch author hasn't referenced the file (s)he wants to patch correctly
[07:35] <nigelb> instead of share/applications/vlc.desktop its just vlc.desktop
[07:36] <nigelb> someday, someone will write a script to properly tag patches
[07:36] <nigelb> until then, I'll just crib about it I guess
[07:39] <nigelb> is normal for series file to have $patch_name -p$ ?
[07:39] <nigelb> i.e. after importing
[07:40] <maco> if the patch has a p number other than 1, sure
[07:40] <maco> (1 is default i believe)
[07:40] <nigelb> I think if I specify something it turns up there
[07:40]  * maco waits for persia to say she's wrong
[07:41] <nigelb> 1 is default :)
[07:41] <persia> maco is wrong
[07:41] <nigelb> persia, which part?
[07:41] <persia> No, the default is not to do nested trees.
[07:42] <nigelb> -p num - Number of directory levels to strip when applying (default=1)
[07:42] <nigelb> ^ from man quilt
[07:42] <persia> The default is for the directory hierarchy in the patches to be ignored, and for it to apply to patches in the local directory.  Under certain circumstances, this is indistinguisable from p1
[07:42] <persia> Oh, sorry.  I'm describing patch behaviour.  quilt is likely saner
[07:42] <nigelb> ah :)
[07:50] <nigelb> why is my pbuilder not accepting a mirror from the .pbuilderrc file :(
[07:59] <nigelb> is this part of a mirror problem? http://paste.ubuntu.com/409379/
[08:03] <persia> nigelb: That does indicate a mirror problem.  I recommend adding *multiple* entries to sources.list for each component.  Put the ones network-closest to you first, followed by those further away, and with archive.ubuntu.com/ports.ubuntu.com at the end of the list.
[08:03] <nigelb> persia, well, its from my pbuilder build log
[08:03] <persia> apt will try them in order, so you get the advantages of mirroring where the mirror works, and fall back to something trusted if the mirror doesn't work.
[08:03] <persia> There too :)
[08:03] <nigelb> I set the mirror as my closest one, but it just refuses to accept that one :x
[08:04] <nigelb> persia, pbuilder seems adamant on using the mirrors.kernel.org one
[08:05] <nigelb> I did a source .pbuilder and still didn't change
[08:06] <persia> That's hacked into pbuilder-dist
[08:06] <nigelb> no no
[08:06] <nigelb> I use this https://wiki.ubuntu.com/PbuilderHowto#Multiple%20pbuilders
[08:06] <persia> No idea then.
[08:06] <persia> Have you considered sbuild?
[08:06] <nigelb> no
[08:07] <nigelb> is there a how-to somewhere?
[08:07] <persia> Are you running lucid?
[08:07] <nigelb> nope... ugh.. sbuild needs lvm?
[08:07] <persia> Not in lucid.
[08:07] <nigelb> I'm running karmic
[08:07] <persia> Upgrade!
[08:08]  * kobrien slaves over lucid bugs
[08:08] <nigelb> I'm not a fan of Upgrade.  I always do clean installs
[08:08] <persia> lucid is stable enough that if there's anything that doesn't work, you want to know *now* so you have a chance of fixing it.
[08:08] <persia> Mind you, I run karmic on some of my machines, but most certainly not on my development machines.
[08:10] <persia> upgrade should just work.  If something doesn't work, that's a fixable bug.
[08:10] <kobrien> lucid is quite stable
[08:10] <nigelb> still I'm curious as to why pbuilder doesn't work
[08:12] <persia> I can't help you with that.  My experience with pbuilder is limited to patching pbuilder-dist a couple times.
[08:12] <nigelb> I'll just try override-config and if that doesnt work pbuilder-dist
[08:13] <persia> pbuilder-dist hardcodes the mirror in a way I think non-optimal
[08:13] <persia> And I believe lool was working upstream to try to obsolete pbuilder-dist
[08:14] <nigelb> sigh.  I guess I have to upgrade then
[08:21] <geser> lfaraone: http://paste.ubuntu.com/409383/ I hope this finally fixes it
[08:32]  * kobrien face palm. a static type, qualified by static when declared in a function.
[08:39] <kkszysiu> is package freeze now? Or I can upload new packages?
[08:40] <nigelb> kkszysiu, we are in feature freeze for lucid now.  If you really want your package in, you need a feature freeze exception
[08:40] <kobrien> ScottK: successfully compiled https://launchpad.net/ubuntu/+source/php-imlib/0.7-1build1
[08:41] <nigelb> kobrien, you work magic :)
[08:41] <kkszysiu> nigelb, ah
[08:41] <nigelb> kkszysiu, I would suggesting getting the package into debian, it will be synced into lucid then
[08:41] <nigelb> urm... lucid+1
[08:42] <kkszysiu> yeah, thats my plan :P
[08:42] <kobrien> nigelb: I just code C. :). It compiles anyway.
[08:42] <nigelb> kobrien, :)
[08:43] <kobrien> nigelb: I'm unsure as to how to proceed. It's not like there's a report I can attach a patch to. How do I commit my change?
[08:43] <nigelb> just make a bug report
[08:43] <kobrien> nigelb: cool
[08:43] <nigelb> attach a debdiff and subscribe sponsors
[08:44] <nigelb> if you're unsure how to make a debdiff.. attach a simple patch and ping me I'll make a debdiff for ya :)
[08:44] <kobrien> I can debdiff :), cheers
[08:44] <nigelb> cool :)
[08:44] <kobrien> oh wait
[08:44] <kobrien> no, I can debdiff
[08:45] <kobrien> :D
[09:07] <kkszysiu> hmm anyone have idea how to change libexecdir in package? I mean it should be /usr/telepathy/telepathy-sunshine but is /usr/telepathy-sunshine/telepathy-sunshinee. Its strange because if I compile it uusing make & make  install it  see that llibexecsir is /usr/lib/telepathy/telepathy-sunshine
[09:24] <geser> kobrien: for php-imlib?
[09:25] <geser> there is a patch from me waiting in the Debian BTS
[09:25] <geser> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569118
[09:26] <nigelb> geser, for the vlc bug, I got hit with glibc error
[09:26] <geser> have you an error message?
[09:27] <nigelb> ouch...lost it... 2 mins
[09:30] <kobrien> geser: didn't see that. my patch does the same thing...
[09:31] <geser> kobrien: just a hint for the next time: look if there is a bug (with patch) in LP or in the Debian PTS just waiting on someone uploading it, it can save you time
[09:33] <kobrien> geser: noted
[09:34] <geser> kobrien: can you test if the package still works? I don't have a setup ready to test it and didn't had time yet to setup one.
[09:36] <kobrien> geser: other than installing it, how can I test?
[09:37] <geser> http://packages.ubuntu.com/lucid/i386/php-imlib/filelist shows that it contains some examples
[09:38] <kobrien> geser: ok, I'll have a look now.
[09:38] <geser> with apache + php + php-imlib you should be able to run them
[09:38] <kobrien> geser: yeah, I'll copy them and see if they work
[09:42] <geser> thanks
[09:47] <nigelbabu> geser, so this error I got had something to do with glib c and I got a trace output, etc
[09:47] <nigelbabu> I'm rebuilding right now to get a log
[09:50] <kobrien> geser: package is broken
[09:50] <geser> kobrien: :(
[09:51] <kobrien> geser: it's "fatal error" in the logs is that it can't "imlib_create_image" which is kinda necessary for it, as an image library, :(
[10:00] <nigelb> geser, something strange just happened... twice.. everytime I build vlc again, my system shuts down :(
[10:02] <geser> oh
[10:03] <nigelb> any clue whats going wrong?
[10:03] <kobrien> nigelb: weird
[10:03] <nigelb> kobrien, definitely
[10:03] <geser> sorry no idea
[10:03] <nigelb> I'll try pushing to a PPA
[10:03] <nigelb> that should give an idea if somethings wrong only locally :)
[10:04] <geser> have you checked your logs for a kernel oops or a out-of-memory case?
[10:04] <nigelb> how do I do that?
[10:06] <geser> check /var/log/messages or /var/log/syslog
[10:06] <geser> and hope your system was still enough alive to log something
[10:07] <geser> anyone interested in merging "xpdf"? It contains some security fixes and would be nice to have in lucid.
[10:07] <nigelb> neither exists
[10:56] <nigelb> oh, success.. vlc builds :)
[14:25]  * hyperair tickles james_w. banshee-community-extensions is NEW again :-)
[14:57] <cnd> I've got a fix for gnome-settings-daemon bug 484186, I've proposed merging my fix branch, and linked the bug to the branch
[14:57] <cnd> should I also be subscribing ubuntu-sponsors?
[15:04] <dyfet> cnd: I gather you have a patch?  I have seen this issue also, and had wondered about it :)
[15:04] <cnd> dyfet: I've actually created a bzr branch in lp with the fix
[15:04] <cnd> it's ready to be merged
[15:19] <persia> cnd: Yes, subscribing ubuntu-sponsors is potentially helpful, although you'd want to check the sponsoring report source to be sure.  You might also see if anyone is around in #ubuntu-desktop who can push it quickly (most of us don't have upload rights to that package).
[15:20] <cnd> persia: check the sponsoring report for what? (and where is the sponsoring report?)
[15:21] <persia> cnd: Check the code to see if subscribing ubuntu-sponsors does anything at all, and https://code.launchpad.net/~dholbach/ubuntu-sponsoring/trunk
[15:22] <cnd> persia: I'm not following you, what should I be checking in this code for?
[15:23] <nigelb> persia, the bug does show up in the sponsoring report
[15:24] <persia> nigelb: So subscribing ubuntu-sponsors when performing a merge request is superfluous?
[15:25] <cnd> if you're referring to here: http://qa.ubuntu.com/reports/sponsoring/, then the merge request is enough to get on there
[15:25] <nigelb> persia, I believe so, yes
[15:25] <cnd> is that all I need to do then? (outside of maybe bringing it up in #ubuntu-desktop)?
[15:26] <persia> If it appears at qa.ubuntu.com/reports/sponsoring then yes.
[15:26] <cnd> persia: ok, thanks!
[15:28] <c_korn> does the source format 3.0 (quilt) need an explicit build dependency for quilt ?
[15:28] <ScottK> c_korn: No.
[15:28] <ScottK> (mostly)
[15:29] <persia> ScottK: mostly?
[15:29] <c_korn> because lintian warned me that a quilt is missing in build-depends. but maybe because I had "include /usr/share/quilt/quilt.make" in the debian/rules file. is this also required or is patching now done automatically ?
[15:30] <james_w> not unless you call quilt while building
[15:30] <james_w> c_korn: you should be able to drop that
[15:30] <ScottK> persia: Depending on the exact version of dpkg(-dev) involved if you ship a quilt .pc file (I think that's it), the build-dep on quilt is still required.
[15:31] <ScottK> I think, but am not certain, that's not an issue anymore.
[15:31] <persia> ScottK: Ah, yes.  That's not an issue anymore in sid/squeeze/lucid
[15:31] <matttbe> Hello james_w
[15:31] <matttbe> I've a question about this branch https://code.launchpad.net/~ubuntu-branches/ubuntu/lucid/cairo-dock/lucid : cairo-dock packages have been updated but not this branch, is there a problem?
[15:31] <c_korn> is README.source required in 3.0 (quilt) ?
[15:32] <ScottK> Not due to having quilt and patches
[15:32] <matttbe> (cairo-dock-plug-ins branch has been updated => https://code.launchpad.net/~ubuntu-branches/ubuntu/lucid/cairo-dock-plug-ins/lucid )
[15:32] <persia> c_korn: And please don't reference quilt in the build for format 3.0(quilt) : if you rely on some obscure behaviour related to how patches are applied at build time using quilt, use format 3.0(native).
[15:33] <james_w> hyperair: you never replied to my mail, is the part without any license statements sorted?
[15:33] <james_w> matttbe: probably
[15:34] <hyperair> james_w: ah sorry about that. yes, everything's now documented in debian/copyright.
[15:34] <james_w> matttbe: yeah, there's a bug in the importer that this package is hitting
[15:34] <hyperair> james_w: lirc still is missing copyright statements, but i've mentioned in a comment where the original code came from, plus a debian/copyright that upstream did before  b-c-e was founded.
[15:35] <c_korn> persia: ok, thanks for the warning
[15:35] <matttbe> james_w: ok, I'd seen this problem and somebody tells me to ping you
[15:40] <matttbe> I also have another question: I've added 'apport' support in 'cairo-dock' packages but all needed informations are located in a private bug report. How can I access to this private bug? e.g. bug #553265
[15:41]  * Pici looks at bot error
[15:44] <persia> matttbe: Your best plan for getting access to that class of bugs is to work with the bugsquad long enough to gain Bug Control.  They usually hang out in #ubuntu-bugs and are always happy to help new folks learn the processes.
[15:44] <persia> matttbe: Alternately, I believe you can subscribe to *all* bugs for the package of interest, but I'm not absolutely sure that works.
[15:45] <matttbe> I subscribed to all bugs for these packages but it didn't work
[15:46] <persia> Yeah, then you need to be in bug control.
[15:46] <persia> I can inspect that bug in particular, and maybe make unprivate, but that's not a general solution.
[15:46] <matttbe> yes but can I only access to cairo-dock's bugs ?
[15:47] <persia> No, bug control is for access to *all* apport bugs.
[15:47] <matttbe> :) strange
[15:50] <lfaraone> Hm. Does updating a packages' protocol support count as "new features"? I'm eyeing http://www.wireshark.org/docs/relnotes/wireshark-1.2.7.html right now.
[15:52] <persia> lfaraone: Can it introduce new bugs?
[15:54] <persia> matttbe: bug #539889 is no longer private
[15:57] <soren> I'm trying to use mk-sbuild to build me a debian chroot. It fails because apparantly apt is not build-essential in Debian. I can't get that to make sense to me.
[15:57] <persia> soren: Which part doesn't make sense?
[15:58] <soren> persia: Good question :)
[15:58] <persia> soren: And I believe the solution was in debootstrap, although if I'm wrong, I'm happy to hint apt in mk-sbuild.
[15:58] <soren> persia: Probably that apt is not build-essential in Debian (even though it is in Ubuntu).
[15:59] <persia> It won't be in Ubuntu much longer, I think.  Personally, I don't see any reason for it to be build-essential.
[15:59] <soren> persia: Except that buildd's won't work very well without it.
[15:59] <persia> It's not safe to call apt *during* a build, after all.
[16:00] <persia> That's an artifact of how the buildds are configured.
[16:00] <soren> I suppose.
[16:00] <persia> There's no reason one can't set the right apt arguments, and complete the build-deps in the chroot *before* entering the chroot to run the build.
[16:01] <persia> It just doesn't happen to be implemented that way.
[16:03] <ScottK> lfaraone: I'd call it bug fix.
[16:03] <ScottK> We definitely want the latest wireshark anyway.
[16:10] <lfaraone> ScottK: okay then :)
[16:33] <DktrKranz> I prepared a list of orphaned packages with Ubuntu changes: http://merkel.debian.org/~dktrkranz/ubuntu_QA   It could be interesting uploading such changes to Debian as QA uploads if feasible, thoughts?
[16:34] <ScottK> It's a good idea.  I've been doing that as I run across such packages.
[16:35] <DktrKranz> some packages could be candidate for removal as well, but at least there's a chance to reduce deltas a bit. Any idea how to spread it?
[16:36] <nigelb> DktrKranz, I've been uploading to debian and requesting sync when debian qa is the maintainer
[16:37] <DktrKranz> nigelb: do you have uploads yet to be sponsored?
[16:38] <nigelb> nope.  all done and synced
[16:38] <DktrKranz> good .)
[16:38] <DktrKranz> _=
[16:38] <DktrKranz> :) (\o/)
[16:38] <nigelb> I can try and help with this btw, giving back upstream is nice :)
[16:39] <DktrKranz> definitely :)
[16:46] <nigelb> DktrKranz, anyway to agree to fix a particular package?
[16:46] <nigelb> i.e. mark as I will be fixing it
[16:47] <DktrKranz> nigelb: wiki page? upload on mentors.d.n, so PTS is informed?
[16:48] <nigelb> DktrKranz, ah, I wanted to delay uploading to mentors.  well, I guess I'll have to do it sooner than later
[16:49] <DktrKranz> nigelb: no need to use it, I can sponsor them as well, just give me a pointer to a .dsc or a debdiff :)
[16:49] <nigelb> ok, I'll get to work :)
[16:50] <DktrKranz> thanks!
[17:00] <nigelb> DktrKranz, I'll move that table onto a wiki.  some of the ubuntu changes need not be moved back upstream
[17:35] <nigelb> DktrKranz, https://wiki.ubuntu.com/Debian/QADelta
[17:42] <wrapster> in the postinst script i cannot execute how do i execute shell commands?coz one in particular called 'update-ca-certificates' fails if written inside the postinst script
[17:42] <wrapster> but anywhere else if i write its working fine.
[17:43] <wrapster> http://pastie.org/900511
[17:43] <wrapster> i've been at it with no result.. would really appreciate help
[17:55] <geser> wrapster: then find out why it fails (edit that shell-script to show you what it's doing and where it fails)
[17:55] <geser> even if you post it once more, we can't tell you what's wrong because we don't know why the script fails
[18:02] <stevecrozz> I've just built a new package 'uwsgi' which provides one binary, should I copy the binary to /usr/bin in debian/rules?
[18:03] <stevecrozz> and how would apt no to remove it during apt-get remove?
[18:04] <geser> why would you want to remove the package but not the binary?
[18:05] <stevecrozz> geser: you wouldn't want that of course, but I don't know how to provide that
[18:07] <stevecrozz> if I just "cp uwsgi26 $(CURDIR)/debian/$(package)/usr/bin" in install: build ... will that work?
[18:08] <geser> yes, that will make it part of the deb
[18:09] <DktrKranz> nigelb: nice, thanks
[18:10] <wrapster> geser: i did all those.. i was able to find out that command 'update-ca-certificte' was failing
[18:10] <wrapster> and thats about it.
[18:10] <nigelb> DktrKranz, some changes are not required to be sent to debian, so people can comment :)
[18:10] <wrapster> I tried with 'set -x' to figure it out but nothing was helpful
[18:11] <wrapster> geser: I can also confirm that this cmd is the problem as i removed this from the postinst script and the pkg was installed cleanly.
[18:11] <geser> wrapster: you added "set -x" to update-ca-certificates? that should show you where it failed so you can try to figure out why
[18:11] <stevecrozz> geser: Is there any reading you can point me to on how to do this right? I'm seeing this type of stuff: mkdir: cannot create directory `/home/stevecrozz/src/uwsgi/uwsgi-0.9.4.3/debian/uwsgi/usr/bin': No such file or directory
[18:12] <wrapster> geser: yes i added it to that command.. as such in the postinst script.. I cannot add it else where.
[18:13] <wrapster> geser: and it didnt work.. http://pastie.org/904051
[18:14] <geser> stevecrozz: either mkdir $(CURDIR)/debian/$(package)/usr/bin or put "usr/bin/" debian/dirs and use dh_installdirs
[18:14] <slytherin> Can anyone think of any reason why liboscache-java is missing from archive even though it is listed on LP - https://edge.launchpad.net/ubuntu/+source/oscache
[18:15] <geser> wrapster: you have to add "set -x" to update-ca-certificates to see where it fails. without this nobody can help you as we don't know where and why it fails
[18:15] <wrapster> but thats a command right and its provided by the same pkg that is failing.. namely 'ca-certificates'
[18:16] <geser> slytherin: see the mail from slytherin on u-d-a (see also https://edge.launchpad.net/ubuntu/lucid/i386/liboscache-java)
[18:17] <geser> wrapster: you have to temporarily modify that script else you don't figure out why it fails (once you know why it fails, you can undo those changes again)
[18:17] <geser> I don't know an other way to debug this
[18:18] <wrapster> ok thanks.. i try to do something and get back to you.
[18:18] <slytherin> geser: Thanks. I missed the mail.
[18:19] <geser> slytherin: once you resolved the FTBFS the package can come back
[18:19] <slytherin> geser: Checking why it FTBFS
[18:20] <wrapster> geser: yes got it.. thanks .. here is the problem..
[18:20] <wrapster> http://pastie.org/904060
[18:23] <geser> wrapster: now you have to figure out what c_rehash does and why it fails
[18:23] <geser> slytherin: http://people.ubuntuwire.org/~lucas/ubuntu-nbs/32/oscache_2.4.1+dak1-1_llucid32.buildlog
[18:24] <slytherin> geser: Found that. Looks like problem with target JVM version set during compilation.
[18:24] <slytherin> Or probably problem with GCJ
[18:25] <stevecrozz> geser: it looks like this works: "cp uwsgi26 $(CURDIR)/debian/tmp/usr/bin"
[18:25] <stevecrozz> I was using "cp uwsgi26 $(CURDIR)/debian/$(package)/usr/bin
[18:25] <geser> stevecrozz: depends on which debhelper level you use
[18:26] <stevecrozz> geser: is that why I'm getting these messages? "Compatibility levels before 5 are deprecated."
[18:26] <geser> yes
[18:26] <slytherin> geser: We now have uninstallable circular build-deps. :-( oscache build-deps on libhibernate3-java which in turn depends on liboscache-java.
[18:26] <stevecrozz> geser: how do I change that?
[18:27] <geser> put the debhelper level you want to use in debian/compat. Current is 7
[18:32] <geser> slytherin: crap
[18:33] <slytherin> checking if it build without hibernate
[18:33] <geser> ScottK: on the next round of binaries removals in universe we should be more careful with -java packages as they like to have circular build-dependencies
[18:34] <ScottK> geser: There was all kinds of warning for people to check this stuff.
[18:34] <geser> I know
[18:34] <geser> and yet slipped it though but we should try to not make it worse
[18:36] <ScottK> Agreed.
[18:36] <stevecrozz> geser: that works great thanks.. now if I want to provide a symlink to uwsgi26 named uwsgi should I do "ln -s /usr/bin/uwsgi26 $(CURDIR)/debian/$(package)/usr/bin/uwsgi"
[18:38] <ScottK> stevecrozz: dh_link is preferred.  See man dh_link for details.
[19:11] <slytherin> geser: oscache fixed.
[19:11] <geser> \o/
[19:17] <ScottK> accepted too
[19:18] <slytherin> ScottK: Thanks
[19:22] <slytherin> ScottK: FYI... Package built and is in NEW queue now.
[19:22] <ScottK> OK.
[19:22] <ScottK> Hopefully slangasek will have a chance to work on New today.
[19:23] <slytherin> ok
[19:23]  * slytherin moves on to other packages.
[19:25] <slangasek> oh, ace is back?
[19:35] <ScottK> slangasek: Yep.  Debian had a fixed revision.
[19:36] <ScottK> That's the one I hit that made another package unbuildable.
[19:36]  * slangasek nods
[19:48] <simar> bound mara
[19:48] <mhall119> when does the window for FFe close?
[19:48] <simar> fuck u aassss holes
[19:48] <simar> i ama asshole
[19:50] <mhall119> yeah, that doesn't really answer my question, but thanks for trying
[19:53] <simar> i am an asshole
[19:53] <simar> fuck u assholes
[20:26] <lfaraone> geser: Does Debian also use pkgstriptranslations for handling ".mo"s? (I'm considereing whether to submit https://edge.launchpad.net/ubuntu/+source/rbot/0.9.14-1ubuntu1 upstream)
[20:38] <mhall119> when does the window for FFe close?
[20:38] <mhall119> is it open until Beta2 is released?
[20:43] <arand> mhall119: I think it's open until the very final, just increasingly stricter..: https://wiki.ubuntu.com/FreezeExceptionProcess
[20:45] <mhall119> arand: thanks
[20:45] <mhall119> now I just need someone to review my packages
[20:45] <mhall119> any Motu's willing to help?
[20:46] <mhall119> no compiling required, honest
[20:53] <RoAkSoAx> mhall119, which ones
[20:55] <mhall119> qimo-session, qimo-games and qimo-wallpaper
[20:56] <RoAkSoAx> mhall119, where are they
[20:56] <RoAkSoAx> revu?
[20:57] <mhall119> yes
[20:57] <mhall119> I've also created bugs for each, with needs-packaging, and attached orig.tar.gz and diff.gz
[20:58] <RoAkSoAx> i'll try to take a look on them later today
[21:00] <RoAkSoAx> but I dont usually woprk with new packages
[21:01] <mhall119> there's not a whole lot to them
[21:01] <mhall119> mostly graphics and config files being copied into the filesystem
[21:02] <RoAkSoAx> mhall119, i'll take a look at them, but wouldn't have been easier to create one source apckages with several binary packages?
[21:02] <mhall119> in theory, maybe
[21:02] <mhall119> in practice, I have no idea what that even means
[21:03] <mhall119> this is my first time making packages, so I'm pretty green
[21:04] <RoAkSoAx> mhall119, i.e. qimo-extras source package, which means only 1 .tar.gz and several binary packages that install the necessary from the source
[21:04] <RoAkSoAx> unless ytou maintain those differently
[21:04] <RoAkSoAx> (or in different sources)
[21:14] <geser> lfaraone: pkgstriptranslations is Ubuntu-specific
[21:22] <arand> joaopinto: Hia, currently checking out bloodfrontier from playdeb, is there currently anything blocking that from making it into the debian and ubuntu repos? (For 10.10 in ubutnus case...)
[21:23] <joaopinto> arand, nothing that I know
[21:24] <joaopinto> it's Sauerbraten based, there should be no problem with the license
[21:24] <arand> joaopinto: Would you mind if I took a stab at it at some point?
[21:25] <joaopinto> feel free
[21:28] <arand> joaopinto: By the way, is the current playdeb version based off 0.85-beta2 (dates seem to indicate that), I didn't find any references in the package.
[21:29] <joaopinto> it is
[21:30] <arand> joaopinto: Okay, cheers for info.
[22:09] <mhall119> RoAkSoAx: I'll look into that for the M cycle
[22:43] <tsimpson> anyone want to apply a fix to a 3 year-old bug? (bug #86685)
[23:12] <bencrisford> ive created a patch for bug #555422 and uploaded the debdiff, set status to confirmed, unassigned myself and subscribed the ubuntu-sponsors
[23:12] <bencrisford> is that correct?
[23:12] <bencrisford> because i havent submitted any fixes for a few months
[23:13] <ScottK> Sounds right.
[23:19] <bencrisford> ScottK: :)