[02:00] <coppro> wait, is my Launchpad account an OpenID?
[02:01] <nhandler> Yes coppro
[02:01] <coppro> what URL do I use for the signin
[02:01] <coppro> because I'm trying to log into another OpenID site and it's not working
[02:01] <coppro> I tried http://launchpad.net/~coppro, which seemed obvious
[02:01] <boshhead> coppro: https://login.launchpad.net/
[02:02] <coppro> ok ty
[02:07] <coppro> boshhead: nope, not working
[02:07] <coppro> oh wait, I see
[02:07] <coppro> nevermind
[02:11] <boshhead> coppro: How dare you doubt me.
[02:11] <coppro> eh, turns out it isn't working after
[02:11] <coppro> *after all
[02:11] <boshhead> Worked for me :) Are you logged into launchpad?
[02:11] <coppro> yes
[02:12] <coppro> could be I need to be on the beta team
[02:12] <coppro> I like beta stuff so I just applied :)
[02:15] <nhandler> coppro: Go to launchpad.net/~coppro, it should show you your open id url
[02:16] <coppro> where?
[02:18] <coppro> I don't see it
[02:18] <nhandler> coppro: For me, it shows it right below my SSH Keys, and above the map
[02:18] <nhandler> Oh wait, I'm on edge, one sec
[02:27] <boshhead> I didn't have to provide anything specific to me, just login.launchpad.net when I signed up for something.
[02:28] <boshhead> Ahh, apparently that's an OpenID 2.0 thing :) If the site doesn't support it you have to use your specific URL :)
[02:30] <coppro> even using edge I see no openid link :(
[02:30] <coppro> sad, because I can use REVU
[02:30] <boshhead> Time to scrap the whole OpenID thing.
[02:30] <coppro> probably just in beta is the issue
[02:33] <nhandler> coppro: Did you get the OpenID issue sorted out? I just check on the normal Launchpad, and it shows the OpenID url on your profile page if your are logged in.
[02:33] <coppro> nope, don't see it
[02:34] <coppro> and the isntructions just say it's in beta
[02:34] <coppro> no specific other way to enable
[02:36] <nhandler> I could have sworn that Launchpad 2.0 gave OpenID to everyone. That was why REVU switched to using OpenID
[02:37] <Flannel> LP is an openID provider, yes.
[02:39] <nhandler> coppro: Are you logged in to Launchpad?
[02:39] <coppro> yes
[02:40] <nhandler> You could try going to #launchpad. There should be an OpenID URL on your ~coppro page if you are logged in.
[02:40] <coppro> ok ty
[02:41] <nhandler> Sorry I couldn't be more of a help coppro
[02:41] <nhandler> I hope you get the issue sorted out
[02:41] <coppro> no worries
[02:51] <radetsky> Hey motu, anybody in charge of qt/webkit here?
[02:52] <radetsky> libqtwebkit-dev depends on and conflicts with libqt4-dev. I assume this is a bug.
[03:15] <ScottK-laptop> radetsky: This is in Hardy, right?
[03:40] <ScottK-laptop> NCommander: Did you ever come to any conclusions about the svn backport?
[03:42] <ajmitch> ScottK-laptop: 1.5.1 to hardy? I haven't been testing any of the reverse dependencies, but 1.5 appears to work
[03:43] <ScottK-laptop> ajmitch: There's an issue (apparently) with switching from libneon to ligneon-gnutls and SSL certs.
[03:43] <ScottK-laptop> He was investigating.  Everything else seems to be fine.
[03:43] <ajmitch> interesting, I tend to only use it with http:// or svn+ssh
[03:43] <ScottK-laptop> Yeah, it's a minority use case, but I'd like to make it work for everyone.
[03:44] <ajmitch> regressions are bad
[03:44] <ScottK-laptop> Yeah.
[03:44] <ScottK-laptop> In this case it's the result of a deliberate packaging change by the Debian Maintainer.
[04:25] <radetsky> ScottK-laptop: sorry, got distracted
[04:25] <radetsky> yeah, hardy
[04:25] <ScottK-laptop> radetsky: Yes, it's a bug that's been reported, but not fixed.
[04:26] <radetsky> ok
[04:26] <radetsky> thanks
[04:26] <ScottK-laptop> radetsky: Uninstall libqtwebkit-dev and libqtwebkit and then upgrade.
[04:27] <ScottK-laptop> libqtwebkit-dev and such are now included in libqt4-dev and such IIRC.
[04:28] <radetsky> I got " error: QWebKit: No such file or directory" even though I think I included everything correctly
[04:29] <radetsky> but I might have done something wrong
[04:30] <radetsky> anyway, I'm trying the upgrade as you suggested
[04:30] <ScottK-laptop> As I recall, and I don't have time to research it right now, there is a conflict between the Hardy packages and the Intrepid packages that were backported.
[04:30] <persia> If anyone is interested in updating VLC, upstream is in #ubuntu-bugs (j-b), and would like to help with an update, because a lot of bugs are fixed.  See bug #262705 for a hint.
[04:30]  * persia doesn't have any idea wheter it's worth a freeze exception
[04:30] <ScottK-laptop> jdong ^^^
[04:31] <radetsky> ScottK-laptop: you think this has been fixed in intrepid-backports?
[04:32] <ScottK-laptop> radetsky: It has not.  You have to work through it manually.
[04:32] <radetsky> oh boy
[04:33] <ScottK-laptop> radetsky: You might search for the bug.  I think what you need to do is in that.
[04:34] <radetsky> where, launchpad? I'm not an ubuntu dev, so I don't know these things
[04:38] <ScottK-laptop> Yes, in Launchpad.  Sorry I can't be more helpful, I've got about a dozen balls in the air right now.
[04:38] <radetsky> no problem
[04:38] <radetsky> I'm sort of saying stuff for the benefit of anyone else who might be here as well, so if you can't handle it, np
[04:39] <radetsky> in any case, the bug I found (230904) doesn't actually give a fix, it just confirms that the problem does in fact exist. If anyone can point me to the fix, please do
[05:14] <stdin> radetsky: libqtwebkit* is obsolete, just install libqt4-dev and/or libqt4-webkit
[05:18] <StevenK> stdin: I nearly read that as libgtkwebkit* is obsolete
[05:34] <j-b> jdong: ping
[05:42] <superm1> j-b, perhaps for helping to determine which bugs are fixed and to help, you can document some of these bug numbers in the bug that is trying to decide if a Feature Freeze Exception is worth it?
[05:42] <superm1> (in bug 262705)
[05:42] <j-b> superm1: done
[05:45] <j-b> superm1: there is 189575 113927 114539  103741 111615 107899 112076 198916 221428 2722 239431  205325 97721 127594 84098  88487 90603 91679 96978 113922 123589  133528 113922  210354 193445 231621 250041 259025
[05:45] <superm1> j-b, ah very good
[05:45] <j-b> that should be closed with the update
[05:46] <j-b> moreover, if jdong compile with --enable-shout, it will close  127594
[05:46] <j-b> and a few duplicates should follow
[05:46] <superm1> i'll add that information to the bug report
[05:46] <j-b> it is already on it
[05:46] <j-b> Bug 270404
[05:46] <superm1> oh there are a few bug reports, that'd be why
[05:47] <j-b> superm1: one should be in for hardy
[05:47] <j-b> pone for interpid
[05:47] <j-b> one for intrepid
[05:48] <superm1> well they could have both been done as a single bug report for both hardy and intrepid
[05:48] <j-b> superm1: well, they were not :D
[05:48] <j-b> anyway, superm1, 270404 should document most of the bugs that should be closed with update to 0.9.2
[05:48] <superm1> yeah that's what i see
[05:49] <superm1> i'll mark the lesser useful one as a duplicate then
[05:49] <j-b> k
[05:49] <j-b> I strongly advise to update libmpeg2 too
[05:49] <j-b> and to apply a small patch
[05:49] <j-b> to fix an issue
[05:50] <superm1> woo that's a fair deal of CVE's referenced in that bug too
[05:50] <j-b> yeah
[05:50] <j-b> but you can also not put this version in intrepid
[05:51] <j-b> and deal with those issues, that we won't deal with
[05:51] <j-b> superm1: can I ask why vlc is in multiverse ? x264 encoding ?
[05:52] <superm1> j-b, yeah the x264 package is in multiverse, so vlc has to be there too
[05:52] <j-b> k
[05:53] <superm1> wgrant, you were set as the assignee on the old bug before i rearranged the duplicates, do you want me to reassign you, or just let motu-release handle deciding on this?
[05:53] <j-b> Ok, I just hope I didnd't screw your bugsystem
[05:53] <j-b> and that my work was useful
[05:53] <j-b> siretart: if you are around, I did as I promised, to do some vlc bugs cleaning
[05:55] <superm1> j-b, listing all of those bugs will be quite helpful in cleaning up. most appreciated
[05:55] <j-b> superm1: you know where to find me
[05:55] <superm1> the person who ends up doing the packaging will just need to copy that list into the changelog and they will get closed once this upload is done
[05:55] <j-b> I now registered in your launchpad, so you can find me easily
[05:56] <j-b> ok
[05:56] <superm1> very good thank you :)
[05:56] <j-b> I will look at it
[05:56] <j-b> superm1: however, I really advise to add a patch on the released tarball
[05:56] <dholbach> good morning
[05:56] <j-b> where do I do that ?
[05:57] <superm1> j-b, i would recommend attaching that patch to the same bug report for now
[05:57] <superm1> in the future, you can file another bug asking to put that patch in place
[05:57] <j-b> can I link to a git view web ?
[05:57] <superm1> yeah that would be sufficient
[05:57] <j-b> git web
[05:57] <superm1> give a justification for it in the comment
[05:58] <superm1> and then jdong (who i believe was going to be the one packaging) should see it noted there
[05:58] <j-b> ok
[05:59] <j-b> jdong: please enable-shout and patch it
[05:59] <j-b> Done. added
[05:59] <j-b> anyway, C U later
[05:59] <j-b> I am always on #videolan
[05:59] <superm1> okay
[05:59] <superm1> good morning dholbach
[05:59] <j-b> good luck for your work, and thanks. My g/f loves her new "Windows with a cool Heron on it"
[05:59] <dholbach> hiya superm1
[05:59] <j-b> :)
[06:01] <wgrant> superm1: Which one? The 0.8.6i update bug?
[06:01] <hagabaka> what's a heron?
[06:02] <j-b> good night *
[06:02] <ajmitch> dholbach: greetings
[06:02] <dholbach> hi ajmitch!
[06:02] <hagabaka> hmm
[06:02] <hagabaka> there's a heron on ubuntu?
[06:03] <superm1> wgrant, oh that was meant as an SRU bug i see.  nvm then, i'll fix my mistake
[06:03] <wgrant> superm1: Security, but yes.
[06:04] <persia> superm1: One note about the hardy VLC bug was that there was a separate need for a security update for 0.8.6.j
[06:04] <superm1> persia, yeah i saw that j-b added that to the hardy VLC bug
[06:05] <superm1> isn't there a way for LP to indicate this bug is going to be for tracking on hardy only? it's not clear from looking at the bug report at a first glance
[06:05] <wgrant> superm1: Nominate it for Hardy, reject it for Ubuntu.
[06:07] <superm1> ah there we go, okay
[07:48] <NCommander> ScottK-laptop: ?
[07:50] <NCommander> ScottK-laptop: So, w.r.t. to KDE4bindings, do I fail?
[08:10] <AnAnt> Hello, is there anything I should add to this bug report: 269855
[08:10] <AnAnt> bug 269855
[09:27] <AnAnt> is abcdef here ?
[09:27] <slangasek> who?
[09:28] <AnAnt> slangasek: just checking if persia is running a bot
[09:28] <persia> AnAnt: I'm not a bot.  Just in lots of places.
[09:29] <AnAnt> persia: I know that you're not a bot, but on #ubuntu-devel you gave me the same answer that you gave me few weeks ago when I asked about someone else
[09:29] <persia> Anyway, sl-modem needs *lots* of attention, more than just a quick patch for Si3054 modems.
[09:29] <persia> AnAnt: I give everyone that response when they ask for specific people and I know they don't need that person.
[09:29] <AnAnt> persia: well, the patch was for a laptop I ran into
[09:30] <persia> AnAnt: Understood.  Take a look at https://bugs.launchpad.net/ubuntu/+source/sl-modem
[09:30] <AnAnt> persia: I see, well according to sl-modem's changelog, Ian seems the one who worked mostly on sl-modem, that's why I asked about him
[09:30] <persia> There are a *lot* of outstanding patches.  Also, there is a pending merge with upstream that could be done.
[09:31] <persia> Yeah, but it's not been touched in over a year.
[09:31] <persia> Anyway, the point is that if you put together a candidate including all the patches and what not, and tested it, it's much more likely that something would happen.
[09:32] <persia> Until then, it's just waiting for someone (anyone) who cares about the package to make it work.
[09:33] <didrocks> o/
[09:34] <didrocks> I don't understand why I was rejected in my PPA: "PPA uploads must be for the RELEASE pocket" trying to upload to it my iptables backport for hardy
[09:35] <dholbach> didrocks: somebody in #launchpad might have a good answer for you
[09:35] <didrocks> ok, thx dholbach :)
[09:41] <AnAnt> so, why no one cares about sl-modem
[09:42] <persia> AnAnt: That's a hard question.  Personally, I suspect that the wider availability of alternate networking technologies has made modem support less interesting.
[09:43] <persia> I've always been vaguely interested in sl-modem to support computer telephony, but upstream hasn't ever had enough support for that for me to be able to play much.
[09:57] <AnAnt> I think I can see why, it's a headache !
[09:57] <AnAnt> the sl-modem patch system is a real headache
[10:35] <AnAnt_> why is there such a split between Ubuntu & Debian regarding sl-modem package ?
[10:42] <persia> AnAnt_: Mostly because Ubuntu pushed the kernel modules into the kernel, and split the package.  Unfortunately, that large a change is only sensible if someone is watching the package (which isn't the case now).
[10:43] <persia> Personally, I think it might make sense to revert that kernel change, and DKMSify sl-modem (but I'm not going to get around to that)
[10:44] <AnAnt_> persia: sl-modem is orphaned in Debian btw
[10:44] <persia> AnAnt_: Yep.  Nobody really wants to care for it :)
[10:45] <AnAnt_> persia: is it possible that I NMU a new upstream in Debian ?
[10:45] <AnAnt_> persia: I still dunno about DKMS, but is that supported in Debian too ?
[10:45] <broonie> For DKMS check debian-devel over the weekend, there was a thread started about supporting it.
[10:46] <broonie> (the mailing list)
[10:46] <persia> AnAnt_: For NMU, certainly, if you have support from a Debian Developer, and you do a good job.  For DKMS, broonie is much more informed than I.
[10:46] <broonie> If the package is orphaned it's not a NMU to do a new upstream version (it's a QA upload and allowed, though people would prefer that you adopt the package if you care about it.
[10:47] <persia> People in Ubuntu would also prefer that sl-modem be adopted by someone: it needs love
[10:48] <broonie> wv :)
[10:54] <iulian> Good morning.
[12:24] <verwilst> new version of flash 10 is out!
[12:24] <verwilst> new nspluginwrapper'ed version coming up? ;)
[12:25] <laga_> does it *work*?
[12:25] <directhex> flash 10 is better than it was
[12:25] <directhex> though tbh nspluginwrapper i don't trust at all
[12:26] <directhex> i run a tarball i386 firefox these days because nspluginwrapper was so painful
[12:39] <verwilst> don't have a lot of issues with nspluginwrapper though
[12:41] <jimqode> I'm having trouble building smbldap-tools from intrepid .dsc . Could someone look at the output please: http://paste.ubuntu.com/47407/
[12:53] <compengi> when packaging pidgin to deb as a single package using dh_make -s -c gpl, do i need *.ex *.EX dirs docs info README.debian files?
[12:54] <persia> compengi: First, why wouldn't you just start from the existing packaging?  Secondly, you don't want to ship any example files, but you may need to replace them, rather than just deleting them.
[12:54] <compengi> persia, so how do i start?
[12:55] <persia> compengi: apt-get source pidgin is usually a good place to start.
[12:55] <persia> compengi: What is your end goal?
[12:56] <compengi> persia, i want to package a new version of pidgin to change it from source to debian package to be compatible with ubuntu
[12:56] <persia> compengi: OK. For Intrepid?
[12:57] <compengi> persia, as far as a can see that the deadline for intrepid is ended, so i can't upload it to respiratory, so i think hardy would be for now good
[12:58] <persia> compengi: The deadline for hardy was 6 months ago :)
[12:58] <compengi> persia, i know. but could be good uploading it to my launchpad ppa :)
[12:59] <persia> compengi: OK.  In that case, start with apt-get source pidgin in hardy.
[12:59] <persia> Then change the source as you need: if you've a new upstream, this probably means reviewing all the patches applied, and adding a new changelog entry.
[12:59] <persia> Then, once you have it working, debuild -S -sa to prepare a source package.
[13:00] <persia> Build the source package with sbuild or pbuilder to make sure it works cleanly.
[13:00] <persia> Test it.
[13:00] <persia> Then upload to your PPA.
[13:07] <compengi> persia, i downloaded the source pidgin for hardy. now i downloaded the new pidgin release tar.bz2 unpacked and repacked to .orig.tar.bz and commented in the change log. i ran dh_make -s -c gpl and edited changelog, control, copyright files. what would i have to do as the next step as with the pidgin source that i've downloaded and the source that i've got
[13:08] <persia> Throw away everything you have, and start from the hardy source.
[13:08] <compengi> aha
[13:08] <persia> The only part you want to keep is the orig.tar.gz
[13:09] <compengi> from pidgin's new version that i've repacked
[13:09] <persia> Actually, you might even want to drop that.  Try running debian/rules get-orig-source from inside the hardy package.  That ought get a new repacked orig.tar.gz that was repacked in the standard manner.
[13:09] <nxvl> good morning
[13:12] <compengi> persia, $ Debian/rules get-orig-source make:  *** No rule in order to generate „get-orig-source".  End.
[13:12] <persia> compengi: Odd.  I thought all the GNOME packages had that.  In that case, you do want your repacked orig.tar.gz from the new upstream.
[13:12] <wgrant> persia: Pidgin isn't part of GNOME.
[13:17] <ScottK> \sh: How goes Bug 246911?
[13:17] <\sh> ScottK: I'm on it...
[13:23] <Juli_> ScottK: hi! you've commented bug 253016 recently. I wonder how much time it has before it needs to get re-assessed? I mean what is deadline for upload?
[13:27] <compengi> persia, i don't understand what i have to do with the old source
[13:28] <persia> Juli_: I'll upload it within the next three hours.
[13:28] <persia> compengi: You want the contents of debian/ : most importantly the patches.
[13:30] <compengi> persia, aren't those patches old?
[13:30] <persia> compengi: Yes, but some of them may be important, and may not be upstream yet.
[13:30] <compengi> persia, so how do i make sure?
[13:30] <persia> compengi: Review them.
[13:31] <compengi> persia, you mean read them or i need to check somehow if they are still necesary?
[13:32] <persia> compengi: Both.
[13:32] <Juli_> persia: Thanks! but just interesting when FFE expires, in 2 weeks?
[13:33] <persia> Juli_: No fixed deadline, but people get grumpy when it takes too long.  In this case, it's clearly my fault, and as much as anything, I'm being prodded.
[13:33] <persia> Given the current state of things, not uploading retains brokenness that we want to drop.
[13:33] <compengi> persia, btw are those patches from pidgin?
[13:34] <compengi> or wrote by those who had packed to debian?
[13:34] <persia> compengi: Some might be pulled from upstream, some might be written by Debian folk, some by Ubuntu folk, and some pulled from elsewhere.
[13:34] <compengi> hmm..
[13:34] <persia> Also, no matter who wrote them, some of them may have been accepted upstream.
[13:35] <emgent> ScottK: ping
[13:35] <persia> Updating a package isn't easy at all: probably one of the harder tasks done by MOTU.
[13:35] <compengi> persia, isn't better downloading the source package from intrepid's repos?
[13:36] <compengi> since new patches and things had changed from version 2.4.1 to 2.5.0
[13:36] <persia> compengi: You could do that, but it might require intrepid to build the source, or build the binary.  If hardy is your target, pulling from intrepid just makes it more for you to review.
[13:36] <Juli_> persia: understood. and one more little question: should I create a bug for jna's build problem and follow the usual process to upload a fix -  find a sponsor?
[13:36] <persia> You'll get a better quality end-product, but it's more work.
[13:37] <persia> Juli_: jna's build problem?  I thought I fixed that.
[13:37]  * persia looks again
[13:37] <compengi> aha
[13:37] <Juli_> persia: actually may be I missed something
[13:37] <Juli_> checking...
[13:38] <Juli_> persia:  yes, my bad
[13:38] <persia> Juli_: https://launchpad.net/ubuntu/intrepid/+source/libjna-java/3.0.4-0ubuntu2 says it built on everything but hppa, and that's blocked because there is no default-jdk for hppa.
[13:38] <Juli_> everything is ok now, sorry
[13:38] <Juli_> persia: thanks a lot!
[13:39] <persia> Good.  You had me frightened.  I've been busy with other things, and haven't been giving this the attention it needed, but I thought netbeans was ready for upload.
[13:40] <compengi> persia, so how would you recommend to be followed and uptodate with all those things? like what's changed and what patches are needed and what aren't etc. reading a tutorial from wiki doesn't explain much as it is in fact.
[13:40] <Juli_> persia: sorry...
[13:41] <persia> Juli_: No worries.  Small fright only, but fully assuaged by the build page in LP.
[13:41] <persia> compengi: There was an *excellent* session in the most recent developer week on just this topic.
[13:42] <Juli_> persia: I'm a bit absent-minded after vacation:)
[13:42] <compengi> persia, any summary of what have been discussed?
[13:42] <persia> compengi: https://wiki.ubuntu.com/MeetingLogs/devweek0809/PackageUpdates
[13:43] <emgent> pochu: ping
[13:44] <persia> Juli_: No worries.  Welcome back :)
[13:45] <Juli_> persia: Thanks! :)
[13:52] <pochu> emgent: pong
[14:01] <siretart>      
[14:53] <bddebian> Heya gang
[15:10] <geser_> Hi bddebian
[15:11] <bddebian> Heya geser
[15:11] <ScottK-laptop> Heya bddebian.
[15:11] <bddebian> Hi ScottK-laptop
[15:12] <NCommander> morning bddebian
[15:19] <bddebian> Hi NCommander
[15:20] <NCommander> how goes it bddebian
[15:21] <bddebian> OK thanks, you?
[15:21] <NCommander> decafinated :-/
[16:55] <infinito> which is the correct signature for the debian/changelog to close launchpad bugs?
[16:57] <siretart> LP: #1
[17:08] <infinito> siretart: and if it closes several bugs?? LP: #1, #2, #3 ?
[17:09] <persia> infinito: It's a rare case that one thing closes several bugs, but yes, that works.  More common is to expand the changelog entry, explaining each change, and including the relevant LP: #nnnn thereafter
[17:10] <infinito> persia: i'm talking about a new upstream release which closes 3 bugs
[17:10] <persia> infinito: Yes.  Hold on a second, and I'll prepare a pastebin with a sample of how I prefer to read it :)
[17:10] <james_w> infinito: explaining what in the new upstream release fixes each particular bug is preferred
[17:11] <james_w> infinito: if they are just "please update" bugs then that is fine
[17:12] <infinito> james_w: the upstream version has a line for each bug on its NEWS file
[17:12] <james_w> you can probably just copy them and add the bug references then
[17:14] <infinito> james_w: something like this? http://paste2.org/p/74766
[17:15] <james_w> infinito: yeah
[17:15] <james_w> I prefer to see something about what the fix was, but if they are taken from the upstream NEWS file then I can just complain about them
[17:18] <persia> infinito: http://paste.ubuntu.com/47499/ is an example
[17:19] <persia> Notice that it closes lots of bugs, but it also explains what has changed, and how.
[17:21] <siretart> infinito: if a new upstream release closes 3 bugs, then you should still explain what has changed in this version, and not only close the bugs
[17:21] <siretart> infinito: or are all 3 bugs requesting a new upstream release and are in fact duplicates?
[17:21] <infinito> siretart: they are 3 bugs, each related to a different thing, which are solved in new upstream release
[17:22] <siretart> infinito: great
[17:24] <infinito> james_w, persia, siretart: maybe is better this way? http://paste2.org/p/74772
[17:25] <siretart> infinito: perfect
[17:25] <siretart> (perhaps linewrap after 78 colums)
[17:26] <persia> infinito: Indeed, although we avoid bumping the standards version in Ubuntu for packages also in Debian
[17:26] <infinito> persia: this is for uploading into debian, and then sync in ubuntu, that's why i bumped standards
[17:27] <persia> infinito: In that case, perfect :)
[17:28]  * persia wonders if that actually closes the LP bugs: does the manual-sync process generate .changes files that include the right header?
[17:29] <ScottK-laptop> persia: It does.
[17:29] <Laney> IIRC it does
[17:29] <persia> Excellent.  I remember when it didn't, but I don't often see examples.
[17:59] <j-b> where can I find nullack?
[18:00] <james_w> j-b: he doesn't seem to be online right now
[18:00] <persia> j-b: Right now, not much of anywhere.  Usually in #ubuntu-bugs, #ubuntu-testing, #ubuntu-quality, and probably others.
[18:01] <compengi> persia, perfect. i read the wiki page of the perfect session. learned a lot. i erased actually everything and started it from ground. i unpacked the new version of pidgin and renamed it to ubuntu's standarts. then downloaded the source and zcat patches -p1. i need to comment that at the end in dch -i right?
[18:01] <j-b> too bad
[18:02] <persia> compengi: Sounds like you're on the right track.
[18:02] <ScottK-laptop> j-b: He's in Australia, IIRC, so this probably isn't the best time of day in any case.
[18:02] <james_w> j-b: anything anyone else here can help you with?
[18:03] <j-b> well, I think he misunderstood me and my bug report
[18:03] <j-b> about VLC 0.9.2
[18:03] <compengi> persia, thanks and i hope so. i tried to run diff but it's senseless you know why :P. what should be the next step
[18:03] <james_w> j-b: requesting the new version be included in Intrepid?
[18:04] <j-b> yes
[18:04] <persia> compengi: Next step towards what goal?  If your goal is still a PPA, you ought be able to upload.
[18:04] <j-b> he says it is not doable because it needs a newer FFmpeg
[18:04] <j-b> which is totally wrong
[18:04] <persia> compengi: If your next step is to get it in intrepid, you want to talk to the people in #ubuntu-desktop
[18:05] <compengi> persia, ermm.. you think that only unpacking merging the patches from the old release to the new one would be enough?
[18:05] <persia> j-b: Does it not need a newer FFmpeg?  Also, I thought jdong was planning that update with you, but took a break to sleep, wasn't he?
[18:05] <Milyardo> The new FFmpeg does need to included as well, but I do not bielive Video Lan requires it either j-b
[18:05] <j-b> persia: I compile VLC top of the tree with a 1 year old FFmpeg
[18:05] <persia> compengi: Oh, do you not have a source pacakge yet?  In that case, it's `debuild -S -sa`
[18:06] <james_w> j-b: it sounds like he suggests that it is needed for the "best experience"
[18:06] <j-b> james_w: no, it is better to fix two ubuntu bugs
[18:06] <persia> j-b: Then it's just wrong :)  If the conversation is in a bug report, please correct the misconception.
[18:06] <devfil> ScottK-laptop: if a new upstream version add only a translation and fix bugs, is the added translation considerated bugfix or do I need a FFe?
[18:06] <compengi> persia, what you mean by source package?
[18:06] <j-b> persia: no, becaus he said so in the forums...
[18:06] <persia> compengi: A .dsc, a .diff.gz, and an .orig.tar.gz
[18:07] <ScottK> devfil: I'd call a fixed/added translation a bug fix.
[18:07] <persia> j-b: The forums are rarely a good source of developer input.
[18:07] <j-b> Milyardo: the fact that VLC doens't enter Intrepid is one thing
[18:07] <Milyardo> :)
[18:07] <devfil> ScottK: ok thanks
[18:07] <j-b> Milyardo: saying that it doesn't enter BECAUSe of needing newer FFmpeg is wrong
[18:07] <j-b> Milyardo: however, I can assure you that 0.8.6j has security issues
[18:08] <j-b> that are fixed in 0.9.2
[18:08] <j-b> even if they have no CVE
[18:08] <j-b> https://bugs.launchpad.net/bugs/113922 like this one
[18:08] <persia> Well, we caught that one :)
[18:09] <compengi> persia, of the new one nope. i have just merged the patches from the old (2.4.1 hardy) to the new source 2.5.1. btw you noted lately that i need to build this package under intrepid if i want to release it there, and 2. if i want to release it under intrepid i need first to get the newest 2.5.0 source from intrepid's respiratory am i getting right?
[18:09] <j-b> this one http://git.videolan.org/?p=vlc.git;a=commitdiff;h=deedaf8267f7a9c02cbc9aa728a68e5156eabb4c
[18:09] <Laney> j-b: Check bug #270404 - where discussions are going on if you haven't seen it already
[18:10] <j-b> Laney: I mostly wrote all the comments of this bug
[18:10] <Laney> j-b: Ah, that's you
[18:10] <Laney> Nice work - those comments are super helpful
[18:10] <j-b> Milyardo: anyway, I don't care if you don't ship VLC in Interpid
[18:10] <persia> compengi: That sounds right.
[18:10] <j-b> Milyardo: however, I don't like that ubuntu developers blame US
[18:11] <j-b> that is just my point
[18:11] <Milyardo> Ahhh
[18:11] <j-b> http://ubuntuforums.org/showpost.php?p=5791767&postcount=8
[18:11] <j-b> because of that post
[18:12] <j-b> ANd I don't know how to fix http://git.videolan.org/?p=vlc.git;a=commitdiff;h=deedaf8267f7a9c02cbc9aa728a68e5156eabb4c in 0.8.6 branch
[18:12] <j-b> I should try
[18:12] <j-b> anyway, bbl
[18:12] <compengi> persia, so let me just make it clean under hardy, so i would learn abit more of how to package and when i'll get that finished i'll just give it out to pidgin's team for people to use. but first i need to make sure if i'm doing fine
[18:13] <persia> compengi: Sounds like a good plan.
[18:13] <compengi> indeed
[18:13] <Milyardo> VLC doesn't staticly link to SVN, it was packages that way by the MOTUs
[18:15] <persia> Milyardo: Well, by a specific person.  It's not best to blame groups generally.  Often the specific person had a reason, and communication with that person will lead to a mutually acceptable solution.
[18:15] <slytherin> can someone please give back dbus-java?
[18:15] <Milyardo> I know, I wasn't blaming the group, I just don't know who that specific person is
[18:16] <Milyardo> I was just citing another error in Nullack's post
[18:17] <compengi> persia, do i need to add anything in changelog, control or copyright? or in dch -i after i'd comment the changes the script would automatically edit those files
[18:18] <persia> compengi: You need to review the changed files in the new upstream, and if there were any licensing changes, make sure to update debian/copyright.  You need to review the dependencies and build-dependencies, and maybe update debian/control.  Lastly, you must add a new entry in debian/changelog.  dch -i can help.
[18:19] <persia> Milyardo: aptitude changelog $(package) can tell you a lot.  Checking changelogs.ubuntu.com can tell you even more.
[18:27] <persia> slytherin: Just FYI, crevette probably won't have time to update bluez-gnome, if you want to look at it.
[18:28] <slytherin> persia: Nothing is working on my side except phone to pc file transfer. Even if I update the packages I won't be able to test them.
[18:29] <slytherin> persia: superm1 has promise to do a sanity test with current versions.
[18:29] <slytherin> I mean the ones in repository.
[18:29] <persia> slytherin: OK.  crevette seemed to think we really needed to update, at least to 0.27, but if there's another way to fix the bugs :)
[18:30] <slytherin> persia: Yes there is, update to 4.x :-P
[18:30] <persia> slytherin: That's just not going to happen.  0.27 or 0.28 is possible.
[18:31] <persia> (but the time is getting very short indeed, if someone doesn't decide to organise testing and do it)
[18:31] <slytherin> persia: did you see the link I sent yesterday? FF10 is going to include 4.x. :-(
[18:32] <persia> FF10?  What is that?
[18:32] <slangasek> FinalFox
[18:33] <slytherin> sorry I meant Fedora 10
[18:34] <slytherin> And this is probably because Bastien Nocera works for Fedora as well as bluez-gnome. :-)
[18:35] <persia> Could be.  Could also be because someone in Fedora is paying any attention to bluetooth.  For Ubuntu it seems to be mostly yourself and crevette.
[18:36] <slytherin> How about I mail to devel-discuss list so that at least we will know how many are interested.
[18:37] <persia> slytherin: I don't think that's a useful metric.  It only takes one person to prepare the appropriate patches to fix the known issues and call for testing.  So far, nobody has done it.
[18:37] <persia> Asking on devel-discuss will generate discussion, but I'm not sure it will generate 0.28-0ubuntu1, which is the key important bit.
[18:37] <persia> If we have a 0.28-0ubuntu1, discussion and testing is good.
[18:38] <slytherin> persia: No I was talking about 4.x. And the reason that no one has done it yet may be because everyone thought someone was doing it. Like I said tollef headed bluez in hardy cycle. But he doesn't do it anymore.
[18:39] <persia> Right, but nobody is still doing it, and it's now known that nobody is doing it.
[18:40] <compengi> btw is there any specific maintainer to Pidgin packages for ubuntu?
[18:40] <persia> compengi: Ubuntu tends not to have specific maintainers for anything.  While occasionally this causes confusion (as for bluez-gnome as we were just discussion), typically the various teams keep things up to date.
[18:41] <persia> You'll want to ask in #ubuntu-desktop about updating pidgin.
[18:42] <Laney> compengi: seb128 is (was) doing the update
[18:43] <slytherin> persia: I have to go. Got to go early to office early tomorrow.
[18:43] <persia> slytherin: Have a good night.
[18:43] <slytherin> good knight
[18:55] <luisbg> hello all
[18:55] <luisbg> I have a problem with how packages get installed in a group
[18:55] <luisbg> I have a package that needs to be installed after an other one (some dpkg-divert involved with a file)
[18:55] <luisbg> but if both packages are installed at the same time (apt-get install A B) which happens at install time of ubuntu studio
[18:56] <luisbg> it won't work properly
[18:56] <luisbg> :(
[18:56] <luisbg> it is about the menu, first the package gnome-menus needs to  be installed
[18:56] <luisbg> and then the package ubuntustudio-menu that moves the original menu to .orig and replaces it with the derivative done menu
[18:56] <luisbg> if both packages are installed at the same time only the studio menu is installed (and no .orig)
[18:57] <luisbg> this means that if a user removes the studio-menu file, the system has no menu
[18:57] <luisbg> which is not good :(
[18:58] <james_w> hey luisbg
[18:59] <luisbg> hey james_w
[19:04] <james_w> luisbg: it's supposed to work if they are installed at the same time as the preinst of the diverting package adds the diversion, isn't it?
[19:05] <james_w> or does the diverted file have to be on disk?
[19:07] <luisbg> james_w: the diverted file has to be on the disk
[19:07] <james_w> and if it arrives after it is not installed, rather than just being, you know, diverted?
[19:07] <luisbg> yes
[19:08] <james_w> well, that sounds like a design flaw to me, as it would seem this situation would then be unavoidable, without using pre-depends, or just assuming that either the diverted package is always installed, or that the diverting package is not removed
[19:23] <j-b> Milyardo: Where can I find the official FFmpeg configure used for Intrepid ?
[19:26] <persia> j-b: The current candidate can be collected with `dget http://archive.ubuntu.com/ubuntu/pool/main/f/ffmpeg-debian/ffmpeg-debian_0.svn20080206-12ubuntu1.dsc`
[19:27] <j-b> persia: where do I find your configure line ?
[19:28] <persia> j-b: Typically in debian/rules
[19:28] <persia> You can unpack the source with dpkg-source -x ffmpeg-debian_0.svn20080206-12ubuntu1.dsc
[19:28] <persia> If you don't have the tools, you can also extract it from the diff.gz, but that's not always pretty.
[19:29] <j-b> I have not done debian packages in 3 or 4 years, so I have forgotten
[19:29] <j-b> libswscale seems to be in it
[19:30] <j-b> so, no need for FFmpeg update to get VLC
[19:55] <fabrice_sp> Hi. I've been working on bug 180384. Anyone using Thunderbird is willing to test the produced package? Thanks
[19:58] <\sh> guys...
[19:58] <\sh> does anyone know more about the source package gail and why it's synced in the first place, and after that removed?
[19:59]  * ScottK reads lwn, "Meanwhile, Rockbox has performed a valuable service for Debian developers who would otherwise have to struggle to find a project with longer release cycles than their own."
[20:00] <laga_> haha :)
[20:00] <DktrKranz> \sh, IIRC gail is in libgtk now
[20:02] <\sh> DktrKranz: hmm..
[20:04] <DktrKranz> \sh: from gtk+2.0 (2.13.3-0ubuntu1)
[20:04] <DktrKranz>     - use conflicts and replaces on the different libgail binaries since the
[20:04] <DktrKranz>       library is in gtk now
[20:17] <norsetto> \sh: bug 268713
[20:18] <sebner> \sh DktrKranz norsetto \o/ \o/ \o/
[20:18] <norsetto> sebner: o_0
[20:18] <sebner> norsetto: yes?
[20:19] <norsetto> sebner: trying to keep both eyes open ...
[20:19] <DktrKranz> sebner, new script, isn't it? ;)
[20:20] <sebner> DktrKranz: multi hello script :P
[20:20]  * DktrKranz hides
[20:20] <sebner> norsetto: because you are tired or because of me? ^^
[20:20] <sebner> DktrKranz: ^^
[20:21] <norsetto> sebner: do you know the meaning of paranoic ?
[20:21] <DktrKranz> sebner, you better run fast now...
[20:22]  * sebner runs away and cries. cesare doesn't want his love :(
[20:23] <DktrKranz> sebner, he can't, he's married and his wife would become angry...
[20:24] <sebner> DktrKranz: bah, his wife has to share him :P
[20:47] <soren> norsetto, ScottK-laptop: You've both been somewhat involved in the python-django 1.0 thing, and I'd like some advice. I have a merged package ready, but I don't want to ruin that Eddy guy's first experience with Ubuntu development by trampling over the bug and uploading it if he's somewhat close to being done. Opinions?
[20:47] <norsetto> soren: wasn't it uploaded already?
[20:48] <norsetto> soren: no, my mistake, that was netbeans
[20:48] <ScottK-laptop> soren: Comment in the bug thanking him for his work and say you've built on it to make an upload ready package.  Give him some time (a day or so) to respond and upload if he doesn't.
[20:48] <ScottK-laptop> soren: You might even put your debdiff in the bug and ask him what he thinks.
[20:49] <ScottK-laptop> He was pretty clearly confused about how to merge based on the fact that there was a previous Ubuntu diff, so I don't think he'll mind.
[20:49] <soren> ScottK-laptop: That sounds like a good idea. I'm not going to say that I built on his work, since... well, I didn't :)
[20:49] <ScottK-laptop> Ah.  OK.
[20:49] <soren> ScottK-laptop: To be honest, it was rather less than straightforward.
[20:50] <norsetto> soren: it could be good for him to see how you did it anyway
[20:50] <ScottK-laptop> Well then I'd suggest being as generous about his contribution as is honest.
[20:50] <soren> ScottK-laptop: Apparantly, Debian had two branches, one that was going on in experimental, and one that was going on in unstable, each with their own changelog history.
[20:50] <ScottK-laptop> Ah.  Yes.  That sort of thing.
[20:50] <soren> ...the current package we have was a branch of the one in unstable. The 1.0-1 package originates from the old experimental branch.
[20:51] <ScottK-laptop> Then once 1.0 came out it jumps to Sid.
[20:51] <soren> Yes. So *none* of the changelog diff applied properly.
[20:52] <ScottK-laptop> Lovely.
[20:52] <soren> I just stuck the Ubuntu specific changelog entries in a big pile at the most reasonable point in time, which is around where the two trees branched.
[20:52] <ScottK-laptop> Sounds about right.
[20:52] <soren> I can see why a first timer would get confused by that.
[20:53] <soren> Heck, it confused the heck out of me for a while.
[20:53] <ScottK-laptop> Then I comment along the lines of "This one was really hard because" should also ease any hurt feelings he might have.
[20:53] <soren> Right.
[21:00] <soren> ScottK-laptop: Thanks. I've commented and attached the debdiff.
[21:00] <ScottK-laptop> Great.  Glad to see we're making progress.  Even though I'm not web 2.0 enough to use it, I think it's important for the distro.
[21:36] <ScottK-laptop> soren: I guess keybuck got tired of waiting for django.
[21:37] <soren> ScottK-laptop: Yeah. At least he credited Eddy in the changelog.
[21:37] <ScottK-laptop> Yep.
[21:40] <punkrockguy318> Is it to late to get FCE Ultra 2 into intrepid?  it's a huge improvement over the current fceu
[21:41] <punkrockguy318> Fceu Ultra is the main NES emulator for linux if you're unaware of the project
[21:50] <calc> punkrockguy318: not sure if stuff in universe is bound by the FF or not
[21:51] <calc> punkrockguy318: beta freeze is next week so its probably still acceptable but someone else would know more about universe stuff than I
[21:53] <geser> calc: FF also applies to universe
[21:57] <calc> geser: oh ok
[21:57] <calc> i didn't realize it did since its not supported
[21:59] <cody-somerville> calc, says who?
[22:00] <geser> calc: universe is not supported by Canonical but the community still tries to get universe into a good shape before release, so e.g. no new upstream version after FF
[22:01]  * calc probably is misremembering old data from several releases ago, sorry i'll shut up now
[22:02] <calc> oh i think i know why i was confused
[22:02] <calc> the text in the sources.list says "ENTIRELY UNSUPPORTED"
[22:03] <ScottK-laptop> calc: Canonical employees write the sources.list.
[22:03] <calc> ScottK-laptop: yes, it seems to be somewhat inaccurate
[22:03] <ScottK-laptop> I agree.
[22:03] <calc> sorry for causing additional confusion
[22:03] <ScottK-laptop> No problem.
[22:04] <calc> i hope they get that meta support stuff done eventually
[22:04] <calc> the stuff that was discussed during last UDS
[22:08]  * cody-somerville nods.