[00:00] <mruiz> I'm working on a sync, and I have a versioning problem (Debian < Ubuntu). I want to know how should I rename Debian version...
[00:00] <mruiz> an example:  dpkg --compare-versions 0.0.4-2 gt 0.0.4ubuntu5 ; echo $? gave me 1 as result (false)
[00:01] <crimsun> hmm, it became non-native?
[00:02] <norsetto> g'nigth all
[00:02] <crimsun> you can alway sort the Debian versioning later, e.g., 0.0.4.1-1, if you control the upstream versioning itself.
[00:02] <crimsun> or, use an epoch
[00:02] <mruiz> crimsun, it was an error version number introduced by a Debian NMU
[00:03] <crimsun> mruiz: ok, in that case, if you don't control upstream versioning as well, then you can force it to sort later.  0.0.4+foo-1.  Ugly, yes.  Epochs are also useful.
[00:09] <coppro> does anyone know a screencasting software that doesn't segfault?
[00:12] <greg-g> heh
[00:12] <coppro> vlc and xvidcap both go kaput when they try and record
[00:17] <greg-g> I haven't had good luck with istanbul either
[00:17] <greg-g> but you can try that one
[00:35] <mok0> persia: ping
[01:05] <ryanakca> crap, is there any way to remove an attachment to a bug / supersede it? *foolishly forgot the (LP: #xxxxxx) in his merge debdiff*
[01:12] <LaserJock> ryanakca: yeah, you can
[01:14] <LaserJock> ryanakca: in the "Bug Attachments" portlet on the left you hit the "edit" link for your attachment
[01:29] <ryanakca> LaserJock: thanks :D
[01:45] <ryanakca> if a MOTU wanted to look at bug #229744
[01:53] <ryanakca> Another thing... The checkpolicy version currently in Ubuntu is checkpolicy_2.0.9-0ubuntu1. The Debian version that I'm trying to merge into Ubuntu is checkpolicy_2.0.12-1 . How can I tell that there aren't any inline patches that I'll loose when merging?
[01:53] <ryanakca> (the source is rather different)
[01:53] <ajmitch> by talking with the original uploader to ubuntu (who is part of upstream, iirc)
[01:54] <ryanakca> ajmitch: ok, thanks :)
[01:56] <ajmitch> I doubt that he's added any, but I don't know what's planned - I'm hoping it can just end up as a sync from debian
[02:01] <LaserJock> ajmitch: hi
[02:01] <ajmitch> LaserJock: good day
[02:03] <LaserJock> ajmitch: how's the weather your way? getting cold?
[02:04] <ajmitch> moderately
[02:04] <ajmitch> we don't have the extremes of many places
[02:04] <LaserJock> ah
[02:05] <LaserJock> too much ocean?
[02:05] <ajmitch> yep
[02:05] <emgent> LaserJock: heya :)
[02:05] <ajmitch> so it's not often that we'd get snow in the city in winter
[02:06] <LaserJock> ajmitch: weird
[02:06] <LaserJock> you're so far south
[02:07] <LaserJock> emgent: hi, everything go ok?
[02:07] <nixternal> hola
[02:07] <nixternal> que paso
[02:07] <emgent> LaserJock: yes :)
[02:07] <LaserJock> oh nos, it's  Richard!
[02:07] <RoAkSoAx> nixternal, no paso nada :P
[02:08] <ajmitch> LaserJock: les me show you a map...
[02:08] <nixternal> hola le vato
[02:08] <ajmitch> http://en.wikipedia.org/wiki/Image:Antipodes_LAEA.png
[02:08] <ajmitch> so southern NZ is at about a similar (opposite) latitude as france
[02:09] <RoAkSoAx> nixternal, you from chicago right?
[02:09] <nixternal> ya
[02:09] <nixternal> hehe
[02:09] <RoAkSoAx> nixternal, how is IIT ? good place to be?
[02:10] <nxvl> 2 more days and i'm going to Prague!!
[02:10] <nxvl> wohoo
[02:10] <nixternal> oh ya...if you are interested in finding out more, on OFTC is #chiglug, 90% of the people in there go to IIT, and so does eddieftw/posingaspopular
[02:10] <nxvl> i really can wait to meet you all out there
[02:10] <nixternal> #chiglug on OFTC is hardcore anti-CoC if you catch my drift :)  a bunch of drunk hackers
[02:11]  * ajmitch has even managed to meet 1 or 2 MOTUs before at previous UDS events
[02:11] <RoAkSoAx> haha lol... i might choose IIT to study a MS in CS
[02:11] <nxvl> nixternal: heh, like #linuxperu, the only OT is linux :P
[02:12] <nixternal> hahah
[02:12] <nixternal> ya, exactly
[02:12] <nixternal> RoAkSoAx: put it this way, the geeks in chiglug from IIT, created their own file system in a day
[02:12] <nixternal> I go to their LUG meetings, and 90% of the time I am lost with their talks
[02:12] <ryanakca> heh, interesting
[02:13] <RoAkSoAx> haha lol... i'm between FIU and IIT, but i might be go for IIT cuz it requires less score in the GRE.. and might be easier to obtain an schoolarship.. since i'll be international student
[02:14]  * ryanakca wonders how long it takes for a mailed bug to appear on LP
[02:14] <ryanakca> not that long ;)
[02:15] <nxvl> RoAkSoAx: for a PhD you mena?
[02:15] <nxvl> mean*
[02:16]  * LaserJock runs
[02:16] <RoAkSoAx> nxvl, my University has some kind of relationship with IIT and FIU and i could get an schoolarship for Masters and PhD
[02:16] <RoAkSoAx> i just need to pass the GRE and i would be likely to obtain it :D
[02:17] <nxvl> oh ok
[02:17] <nxvl> well i need to run in some minutes i think
[02:17] <nxvl> if don't answer is that i'm not here
[02:19] <RoAkSoAx> TheMuso, thanks for reviewing alsa-tools :)
[02:27] <LaserJock> nxvl: what are you suggesting in your email?
[02:29] <bddebian> Heya gang
[02:35] <ScottK> nxvl: In your mail: Did the contributor in question discuss the merge with the previous uploader first?
[02:36] <Hobbsee> ScottK: i thought that got (wrongly) abolished?
[02:36] <ScottK> Hobbsee: There is no rule, but I'm gonna suggest rule or not it's a sensible practice.
[02:37] <ScottK> Any MOTU ought to check open bugs before uploading, but they don't always.
[02:37] <StevenK> I tend to, if I have time.
[02:37]  * Hobbsee does check bugs, but also thinks people should check with her if they want to take a merge.
[02:38] <ScottK> StevenK: Do you know if there is someone planning on rebuilding everything that depends on perl 5.8 API?
[02:38] <ScottK> Hobbsee: I agree.
[02:39] <Hobbsee> but that got outvoted previously
[02:39] <ScottK> I can also understand nxvl's frustration.  These things happen too.
[02:39] <StevenK> ScottK: For Perl 5.10?
[02:39] <ScottK> StevenK: Yes.
[02:40] <ScottK> I had to do two perl lib rebuild uploads today before I could upload spamassassin due to them being uninstallable.
[02:40] <LaserJock> well, if we sponsored merges/syncs quickly it really shouldn't be a problem
[02:40] <LaserJock> and I dislike the ping-the-previous-uploader personally, I think we can do better
[02:41] <StevenK> Mmmmmmm. The problem is, Debian is in the middle of the transistion, so we either have to duplicate work or wait. Since we like to beat down the merges queue, we duplicate.
[02:41] <ScottK> StevenK: If it's just a rebuild, they'll binnmu and we'll still have to do it.  I don't see the duplication.
[02:42]  * ScottK wasn't merging.  Was bug fixing.
[02:42] <StevenK> ScottK: Okay, so libxxx-perl is uninstallable. We upload a rebuild, giving us 1.10-1build1. They release 1.10-2 and we need to merge, thereby doing the work the Debian Maintainer did before they did.
[02:43] <ScottK> StevenK: Why would there be a -2?  They'd do -1+b1 or somesuch on the binary with no source change.  Wouldn't they?
[02:44] <StevenK> ScottK: I didn't say it'd be a binNMU, you did.
[02:44] <ScottK> I guess if a package just needs a rebuild, I'm trying to figure out why they'd do anything else.
[02:45] <ScottK> As I understand it source uploads for such things are discouraged in Debian.
[02:45] <StevenK> Source-only uploads to Debian are rejected, I thought.
[02:46] <ScottK> Yes.  OK.  Source + Binary instead of binNMU.
[02:47] <ScottK> Nevermind then.  No point in arguing over it.
[02:47] <ScottK> It'll be needed or not.  One or the other eventually.
[02:47] <StevenK> ScottK: I suspect I'm not being clear enough, sorry.
[02:47]  * StevenK is somewhat distracted by $WORK
[02:48] <ScottK> Understand.  No problem.
[02:51] <DaneM> Hello.  I'm having a strange pbuilder problem.  I have used dh_make and debuild in the source directory, but when I go to build it using pbuilder, I get the following after it installs the dependencies: http://paste.ubuntu.com/11768/  Any help would be great!
[02:51] <DaneM> (and if you read the error, yes, debian/control exists)
[02:51] <StevenK> DaneM: You don't have a debian/changelog file
[02:51] <StevenK> tail: cannot open `debian/changelog' for reading: No such file or directory
[02:52] <DaneM> hold on...I'll paste my directory contents and my changelog...I stripped it down as best I could to make sure it wasn't a formatting thing.
[02:52] <DaneM> (if I put it in the wrong place, though...)
[02:53] <StevenK> It needs to be in ./debian/changelog in the top-level of the unpacked source package
[02:53] <StevenK> Many tools look for it there, and will get confused if they can't find it.
[02:53] <DaneM> nodnod.  pasting now (for better clarity)
[02:55] <DaneM> http://paste.ubuntu.com/11770/
[02:56] <StevenK> DaneM: It shouldn't be stable in the changelog. But the directory listing looks fine to me.
[02:57] <StevenK> DaneM: I'd suggest copying the .dsc, .diff.gz and .orig.tar.gz to a temporary directory and dpkg-source -x the .dsc, and seeing if it looks strange
[02:58] <DaneM> StevenK: hmmmm.  I'm totally a novice on this stuff, so please enlighten me :-)  I'll take your word for it on the stable thing.  What should I change it to?  I'll give the copy a shot too.
[02:59] <StevenK> DaneM: Well, which release are you targetting?
[03:00] <DaneM> Hardy
[03:00] <DaneM> ok...I'll change it to that then.
[03:00] <StevenK> Lowercase :-)
[03:00] <DaneM> k
[03:01] <DaneM> StevenK: I unpacked the .dsc, and sure enough, the changelog is in ./debian/changelog.
[03:01] <StevenK> That's ... odd
[03:02] <DaneM> yeah, that's what I say!  :-p
[03:02] <TheMuso> RoAkSoAx: No problem./
[03:03] <DaneM> should I paste any other files?  I'm not sure if the rules file is right...I edited it the best I could to get it to build the asterisk-addons samples as well as the regular stuff.
[03:03] <RoAkSoAx> =)
[03:04] <StevenK> DaneM: Put the source package up on the Intraweb, and I'll poke at it when I have a moment?
[03:04] <StevenK> That could be June, though :-/
[03:05] <DaneM> hehe thanks.  I'm a newbie; what's the Intraweb?
[03:05] <StevenK> The Internet, I'm being silly
[03:06] <DaneM> hehe ok.  I'll see if I can find a place.  I don't really have a web presence :-(
[03:06] <DaneM> thanks for looking at my problem.
[03:42] <bbyever> how can i enable intrepid repos?
[03:42] <ScottK> bbyever: What release are you running and what are you trying to do?
[03:43] <bbyever> ﻿ScottK: im running hardy and i am trying to build the package bygfoot, which depends on default-jdk-builddep and its only available on intrepid
[03:44] <bbyever> oops, sorry, im trying ot build jabref
[03:46] <ScottK> You don't want to take the binary packages from Intrepid.  You want to take the source and build those.
[03:47] <ScottK> You can edit the deb-src lines in /etc/apt/sources.list to say intrepid instean of hardy and then apt-get update, apt-get source $PACKAGE.
[03:49] <bbyever> ScottK: but why would i want the source? shouldnt i get the binaries to install the dependencies?
[03:49] <StevenK> ScottK: He wants Build dependancies
[03:49] <ScottK> bbyever: They binaries are built on the Intrepid tool chain.  They main or may not be installable/work as expected.
[03:50] <ScottK> bbyever: Get the source to the stuff you want and then build it on Hardy.  Install that and use it to build your package for Hardy.
[03:50] <bbyever> ScottK: ok, thanks
[03:50] <ScottK> bbyever: Installing packages built on a different tool chain will eventually lead to tears.
[03:52] <bbyever> ok
[03:57] <bbyever> Im getting a source package not found error
[03:58] <ScottK> Did you change Universe/Main as needed?
[04:00] <bbyever> i updated universe
[04:00] <bbyever> but i cant change main
[04:00] <bbyever> i get Failed to fetch http://tazcatl.fciencias.unam.mx/ubuntu/dists/intrepid/main/source/Sources.gz  302 Found
[04:00] <ScottK> I'd pick a different mirror then.
[04:01] <StevenK> Then it's redirecting you, and apt doesn't like redirects
[04:01] <bbyever> ok
[04:01] <StevenK> Run wget for that URL, and see what it redirects you to, and edit your sources.list entry
[04:03] <bbyever> it redirects to guide.opendns.com
[04:04] <bbyever> it worked with archive.ubuntu.com
[04:04] <StevenK> http://guide.opendns.com/ubuntu/dists/intrepid/main/source/Sources.gz gives 404 for me, at least
[04:04] <StevenK> Yes, it would.
[04:05] <bbyever> it found the source now. thanks
[04:24] <bbyever> ok so i downloaded the source default-jdk-builddep and i made the debs but when i try to install them, i get dependency not satisfied errors, even though i've installed the dependencies that it said it was missiog
[04:24] <bbyever> missing*
[04:27] <ScottK> With appropriate versions?
[04:28] <bbyever> the package installer didnt say which version of the dependency to install
[04:33] <bbyever> is it because the dependencies have to be from intrepid as well=
[04:33] <bbyever> ?*
[04:33] <ScottK> Install with -V (e.g. sudo apt-get install -V $PACKAGE)
[04:33] <ScottK> It should tell you then.
[04:34] <ScottK> How are you making the .debs?
[04:34] <bbyever> debuild
[04:39] <bbyever> i have to go, i'll try to get this figured out tomorrow. thanks ScottK and StevenK
[05:10] <LucidFox> What happened to edge.launchpad.net? It lost CSS styling
[05:10] <LucidFox> regular launchpad.net works fine
[05:10] <LucidFox> oh, wait
[05:11] <LucidFox> never mind
[06:14] <slomo> siretart: from my side... yes ;)
[06:35]  * TheMuso would kick his local area power grid for being so flaky at this point, but doesn't wish to lose power again.
[06:35] <tbielawa> lol
[06:35] <TheMuso> Well we do have electrical storm activity here atm, but its normally nothing that would cause power outages in other areas.
[06:40] <nxvl> ScottK: nop, last uploader and new uploader aren't the same person
[06:40] <nxvl> ScottK: so if the contributor talk with the developer or not, is tha same
[06:40] <siretart> slomo: well, then go for it. you have commit access :)
[06:40] <nxvl> ScottK: also, the previus uploader commented on the bug report of the merge
[06:41] <nxvl> ScottK: but didn't upload it
[06:41] <slomo> siretart: what's the plan for lenny now btw? or will ffmpeg stay in experimental forever?
[06:41] <siretart> slomo: -!- Topic for #debian-release: this is not #debian-devel | requests for Etch 4.0r4, transitions, binNMUs: mail debian-release | ongoing: perl5.10, speex, heimdal, clamav, libmilter(sendmail) | pending: xulrunner, ocaml, ffmpeg, poppler
[06:42] <slomo> siretart: great :)
[06:43] <siretart> slomo: iow: waiting for a free slot. the upload is build and signed waiting at http://people.debiaan.org/ffmpeg
[06:43] <dholbach> good morning
[06:43] <nxvl> dholbach: gutten tag
[06:44] <nxvl> dholbach: i send an e-mail to -motu for you :D
[06:49] <dholbach> nxvl: I'd recommend to send it to ubuntu-devel@
[06:50] <nxvl> dholbach: i will tomorrow
[06:50] <nxvl> dholbach: i finish some stuff and go to sleep
[06:50] <dholbach> nxvl: alright - thanks
[06:55] <nxvl> btw
[06:55] <nxvl> did someone know where can i find DaD's source?
[06:56] <RoAkSoAx> nxvl, maybe next to MoM's source?? lol :P
[06:56] <LucidFox> What's DaD?
[06:56] <LucidFox> Or what's MoM, for that matter?
[06:56] <nxvl> Merges-o-Matic
[06:56] <tbielawa> LucidFox: http://merges.ubuntu.com/universe.html is the URL. it tries to merge automatically from debian
[06:56] <nxvl> RoAkSoAx: still out with MoM?
[06:56] <nxvl> heh
[06:57] <tbielawa> LucidFox: and shows us what needs done, current versions, etc
[06:57] <tbielawa> I think that's right?
[06:57] <nxvl> nevermind, found the source
[06:57] <RoAkSoAx> well i'm out
[06:57] <RoAkSoAx> bye all
[06:57] <RoAkSoAx> chau nxvl  :P
[06:57] <tbielawa> bye
[06:57] <RoAkSoAx> byt tbielawa
[07:03] <nxvl> k
[07:04] <nxvl> night all!
[07:04] <nxvl> see you in 3 days!
[07:04] <tbielawa> byee
[07:10] <siretart> nxvl: I generally agree with your observation. However I miss a concrete proposal how to fix this.
[07:11] <siretart> nxvl: in order to make it fair the archive would have to check if the package references/closes a bug with a debdiff attached. Or oven better, don't accept uploads but signed debdiffs only.
[07:12] <siretart> following your mail, at least
[07:17] <dholbach> siretart: I think we should discuss this on ubuntu-devel - maybe merging mom and dad would help with that, it's a process we all should follow
[07:19] <siretart> dholbach: I agree that this is not the right place for discussing this. How about in a bof Prague?
[07:19] <siretart> in Prague, that is
[07:20] <dholbach> siretart: sounds good, but I think it wouldn't hurt to discuss on -devel too (so the people who don't participate in UDS are aware of the discussion and can weigh in too)
[07:24] <tbielawa> hmmmmm.... the dpatch manpage
[07:24] <tbielawa> I think I get it :)
[07:24] <tbielawa> took a little while though.
[07:24] <tbielawa> I like this dpatch-edit-patch command, it's lifty
[07:25] <RAOF> There's a similar one for cdbs
[07:33] <tbielawa> RAOF: I did alot of policy review today @ work on the rules file
[07:33] <tbielawa> setting the patching build targets makes alot more sense now than when I looked at it a few days ago
[07:34] <tbielawa> I don't know what this does yet though: dpatch cat-all >patch-stamp
[07:36] <RAOF> tbielawa: I believe that lists all the patches that have been applied, and writes them to the patch-stamp file.
[07:36] <tbielawa> lol
[07:36] <RAOF> tbielawa: /usr/share/dpatch/dpatch.make will remove the neccesity of calling that manually, though.
[07:36] <tbielawa> a short search told me that is meta information about the patches, author, etc
[07:36] <tbielawa> o'rly
[07:36] <RAOF> Ya, rly.
[07:37] <tbielawa> wow
[07:37] <tbielawa> I like that command.
[07:37] <RAOF> Not so much a command as a bunch of rules that you include.
[07:37] <tbielawa> Yes, that's correct
[07:38] <RAOF> So the full line is 'include /usr/share/dpatch/dpatch.make'.  You can now depend on a patch: target and an unpatch: target, both of which do what you think they do :)
[07:38] <tbielawa> :)
[07:38] <tbielawa> this looks like simpler than aplying dpatch by hand
[07:38] <tbielawa> it's like they make this linux thing easier and easier every day
[07:39] <RAOF> Sadly it doesn't (yet) have debhelper 7 mojo.
[07:39] <tbielawa> RAOF: what would happen if it did?
[07:40] <RAOF> Unicorns.
[07:41]  * tbielawa gasps
[07:41] <RAOF> Well, no.  What would happen is that a sample rules file would be %: dh $@
[07:41] <tbielawa> 0_0
[07:41] <tbielawa> I don't even understand what that means. but there's one line, so it must be magic
[07:42] <RAOF> Well, 2 lines.  And you need the make shebang at the top, and the include directive.
[07:42] <tbielawa> sounds fantastic!
[07:50] <tbielawa> with dpatch.make and dpatch-edit-patch -- this feels too easy... like it's not going to work *anticipating the results*
[10:31] <proppy> hi
[10:52] <mathiaz> Which package version is considered higher by dpkg: 2.0.6-1.1ubuntu1 or 2.0.6-1ubuntu1 ?
[10:53] <joaopinto> mathiaz, dpkg --compare-versions
[10:55] <mathiaz> hm.. right - however apt thinks differently
[10:56] <mathiaz> I've got 2.0.6-1.1ubuntu1 in my local apt repository and 2.0.6-1ubuntu1 installed in my vms. apt-get dist-upgrade thinks nothing should be upgraded
[10:57] <\sh> mathiaz: apt-get update ; apt-get dist-upgrade ? I wonder if apt catched the change
[10:57] <mathiaz> \sh: yeah - I've apt-get updated a couple of time. It picks up another package from my local repository.
[10:58] <\sh> mathiaz: and the packages.* files are knowing about the new version, too? ... could be that the package is not properly in the packages file of your local repos
[10:58] <geser> mathiaz: does "apt-cache policy <pkgname>" list both versions?
[10:58] <\sh> or the package is set on hold
[10:58] <mathiaz> \sh: yes - the new vsftpd package is in Packages.gz
[11:00] <mathiaz> geser: apt-cache policy only shows the package from the archive
[11:00] <dholbach> mathiaz: you could ping mvo about it, he'd know
[11:01] <mathiaz> however the new vsftpd package is listed in /var/lib/apt/lists/localrepo.Packages
[11:01] <mathiaz> dholbach: I guess that's the next step ;)
[11:01] <dholbach> :)
[11:01] <sebner> dholbach: have you uploaded my linkchecker merge about an hour ago?
[11:01] <dholbach> sebner: yes
[11:02] <sebner> dholbach: grmpf. haven't you seen that I'm waiting until we can sync it. also FTBFS now :\
[11:03] <dholbach> sebner: I wasn't sure if "we can sync it" meant some time in the future
[11:04] <sebner> damn intrepid upgrade ^^
[11:04] <sebner> dholbach: grmpf. haven't you seen that I'm waiting until we can sync it. also FTBFS now :\
[11:04] <dholbach> sebner: I wasn't sure if "we can sync it" meant some time in the future
[11:05] <sebner> dholbach: yes in future. therefore I assigned the bug to me ;)
[11:06] <dholbach> sebner: it looks like some problem with python / python-central - at the time I test-built it, it built nicely
[11:06] <sebner> dholbach: /here too. nvm. Haven't got time for it now. Final exams are starting tomorrow ^^
[11:08] <dholbach> doko: do you have an idea what happens here:  http://launchpadlibrarian.net/14486647/buildlog_ubuntu-intrepid-amd64.linkchecker_4.9-1ubuntu1_FAILEDTOBUILD.txt.gz  ?
[11:21] <Riddell> jdong, TheMuso: motu-sru approval needed on bug 175536
[11:24] <Riddell> also bug 228534
[11:30] <willwill> does universe accept package from non-motu? I will make a font package for my loco team and wants to see it in universe.
[11:31] <geser> sure, see REVU
[11:31] <geser> !REVU
[11:32] <willwill> thank you
[11:32] <geser> if it passes REVU it will be upload to the Ubuntu archive
[11:33] <mok0> willwill: but be prepared for several rounds of required changes
[11:34] <willwill> mok0, already, ppa make me tired
[11:34] <sebner> !packaging willwill
[11:34] <sebner> -.-
[11:34] <mok0> !packaging
[11:35] <willwill> Maybe next month, I need to create a poll what fonts should be included first.
[11:35] <mok0> sebner, get back to studying for your exam
[11:36] <sebner> mok0: Ubuntu is just too adictive ^^
[11:36] <mok0> sebner: you can get high after the exam :-)
[11:37] <sebner> mok0: Yeah I know. I will shutdown my laptop soon :) And I upgraded to intrepid. If it's not starting it's also good ^^
[11:38] <mok0> sebner: that's brave :)
[11:38] <sebner> mok0: hmm. did the same with hardy ^^. but I don't installed the b0rken libxfonts package
[11:40] <mok0> sebner: I will wait with the upgrade until I know it works ;-)
[11:40] <sebner> mok0: well, if you ignore the broken packages it is already working ^^
[11:45] <Riddell> siretart: what was non free about ffmpeg?
[11:47] <Riddell> siretart: libavdevice52 main or universe?
[11:53] <siretart> Riddell: ffmpeg is 100% GPL and therefore free
[11:54] <siretart> Riddell: and since we nowadays have packages from universe on the live cds, I'm curious to learn what effect this has on the policy what is acceptable for main and what for universe
[11:54] <Riddell> siretart: if it's all free why the need to rename to ffmpeg-free?
[11:54] <siretart> from the code side: libavdevice is a library where code previously in other parts of ffmpeg have been moved to.
[11:55] <siretart> time will show what applications will link against libavdevice in future
[11:55] <siretart> Riddell: the naming is a bit unfortunate. I plan to upload a ffmpeg-risky package to multiverse soon, which does not have patented encoders stripped
[11:56] <Riddell> universe on live CDs?  you mean xubuntu?
[11:56] <siretart> yes, or like medibuntu, or whatnot
[11:56] <Riddell> there's no change to what can go on CDs.  main only for supported distros and nothing with problematic patents
[11:57] <siretart> well, libmad0 is in main, and is also affected by patents.
[11:57] <Riddell> yes, always has been
[11:57] <Riddell> and has always been banned from being on CDs
[11:58] <Riddell> no change there
[11:58] <siretart> the same applies for ffmpeg
[11:59] <emgent> heya
[12:04] <geser> soren: Hi, do you see a reason to not sync libreadonly-xs-perl from Debian?
[12:05] <siretart> Riddell: regarding ffmpeg, what's the plan with kubuntu? will intrepid ship kde3 in main?
[12:07] <Riddell> siretart: as little as possible
[12:08] <siretart> Riddell: because that would mean that we can demote xine-lib, and with that ffmpeg
[12:08] <Riddell> that would be dependant on the phonon gstreamer plugin being packaged and working as well as xine
[12:08] <Riddell> but it's certainly something to look into
[12:08] <siretart> yupp
[12:12] <Riddell> siretart: how does gstreamer match these days for e.g. dvd menus, w32codecs?
[12:15] <siretart> Riddell: I didn't notice improvements for dvd menus. for w32codecs, well, there is a plugin package, and I had the impression that it worked on i386 only
[12:16] <siretart> the nice thing about gstreamer is that we can have and build a functional core on the CD, and offer users to download dvd support as add-on later. This is IMO the best we can offer anyway
[12:16] <soren> geser: No, I don't think so. I'm not sure why it doesn't show up on MoM. :/
[12:16] <siretart> since it seems that canonical is not willing to ship mpeg2 decoders and libdvdcss on the livecd anyways
[12:23] <geser> soren: it's listed on http://merges.ubuntu.com/universe-manual.html
[12:24] <soren> geser: Oh, ok.
[12:24] <soren> geser: Without actually looking at the packages, I can't think of any reason why we shouldn't be able to sync them
[12:25] <soren> geser: them == libreadonly-{xs-,}-perl
[12:26] <geser> soren: ok, I'll check the other too and file sync requests for both. Thanks.
[12:27] <soren> geser: Oh, thank *you*
[12:33] <\sh> ./VolumeButton.cs(55,17): warning CS0612: `Gtk.Tooltips' is obsolete gnarf
[12:34] <sebner> bye folks.
[12:37] <\sh> do we have a mono gtk pro here? ;)
[12:40] <mok0> yuccc, mono
[13:00] <ScottK> Hello askand.
[13:00] <askand> ﻿ScottK: ah hello again!
[13:01] <ScottK> Anyone who's able: askand has produced a fix for bug 89936 and would like to learn how to integrate his change into an updated package.  Would someone have time to help him with that?
[13:20] <ScottK> askand: I'm busy with $WORK right now, so all I can do is counsel patience.
[13:22] <askand> ﻿ScottK:  Sure, Ill wait
[13:23] <persia> askand: I'm also occupied, but there's some docs on generating a debdiff and requesting sponsorship in the section on Preparing New Revisions in https://wiki.ubuntu.com/MOTU/Contributing.  If something is confusing, asking specific questions here often elicits a faster response.
[13:24] <askand> ﻿ persia: thanks
[13:35] <mok0> askand: I can help
[13:36] <mok0> askand: do you know how to make a source package?
[13:36] <askand> ﻿mok0:  please do :) nah..not reallyy experimented a bit with it
[13:37] <mok0> askand: ... but you got the source package of gmail-notify... ?
[13:37] <ScottK> mok0: AFAIK this is his first attempt.  He was in #ubuntu-bugs looking for how to get his fix uploaded.
[13:37] <askand> ﻿ mok0: yes I have
[13:38] <mok0> askand: ok, so it goes like this: 1) get source package. 2) fix fix fix 3) update changelog (important!!)
[13:39] <mok0> askand: 4) cd to dir that contains debian/ (5) debuild -S -sa
[13:39] <askand> ﻿mok0: ok..the fix fix fix part? Should I just replace the file with a bug in with a file witout the bug?
[13:40] <mok0> askand: yes, the "fix fix fix" means: edit
[13:41] <mok0> askand: when you run "debuild -S -sa" you will get new .diff.gz and .dsc  files
[13:42] <mok0> askand: in the directory above topdir ( topdir== the one that contains debian/)
[13:42] <askand> The last changelog entry was: gmail-notify (1.6.1-3ubuntu2) gutsy; urgency=low should mine be gmail-notify (1.6.1-3ubuntu3) hardy; urgency=medium?
[13:42] <mok0> askand: the you simply "debdiff old.dsc new.dsc"
[13:43] <mok0> askand: if it's a fix to hardy, it should be hardy-proposed
[13:43] <mok0> askand: but, yes, you increment the last number (after ubuntu)
[13:43] <slytherin> mok0: you are talking too fast
[13:44] <askand> yea thanks god for scrollbuttons ;-)
[13:44] <mok0> slytherin: ah. That's the first time anyone has accused me of that :-)
[13:45] <askand> Should I somewhere in the changelog put wat bug is solved with this update?
[13:45] <mok0> askand: yes, in the form (LP:  #nnnn)
[13:46] <mok0> askand: (LP: #89936) actually
[13:46] <mok0> askand: make a good description of what you have done in changelog/
[13:46] <geser> mok0, askand: if it's a SRU the version should be 1.6.1-3ubuntu2.1 and the bug should be fixed in intrepid first (1.6.1-3ubuntu3)
[13:47] <slytherin> is anyone able to do grab-merge.sh blueproximity? The script simply exits for me.
[13:48] <mok0> askand: yeah geser is right, forgot about that...
[13:48] <geser> slytherin: MoM or DaD?
[13:48] <\sh> slytherin: use mom and not dad ;)
[13:48] <mok0> slytherin: works for me
[13:48] <askand> ﻿mok0: hmm..that makes it gmail-notify (1.6.1-3ubuntu3) intrepid ?
[13:49] <mok0> askand: if it's a bug in hardy that you want to fix, it should be ﻿gmail-notify (1.6.1-3ubuntu2.1) hardy-proposed
[13:49] <slytherin> geser: the script was taken from MoM
[13:50] <askand> ﻿mok0:  http://pastebin.com/m4ba2b5bb
[13:51] <slytherin> Oh. DaD says there is a merge for blueproximity, where as MoM doesn't. And I was trying to use MoM script
[13:51] <mok0> askand: also state what files you changed.
[13:51] <\sh> slytherin: manual merge eventually?
[13:52] <askand> oh right
[13:52] <mok0> askand: and wrap the line in the entry so no line is longer than the "--" lines
[13:52] <\sh> slytherin: http://merges.ubuntu.com/universe-manual.html <- there it hides
[13:52] <\sh> slytherin: problem here is: no base debian version to check against
[13:53] <askand> ﻿mok0: http://pastebin.com/m45ccd3fe
[13:53] <\sh> slytherin: therefore mom just don't give any result...and thinking about the old DaD problems, dad will break the merge completly...
[13:53] <mok0> slytherin: take care, afair there is some evil rm statements at the start of that script
[13:54] <slytherin> \sh: yes, you are right, the package in hardy was Ubuntu-only package. SO there is no base debian version
[13:54] <mok0> askand: good, but put the path (relative to topdir) in front of langs.xml
[13:54] <\sh> slytherin: actually it's good to just dget the debian version and the old version in hardy...and do a manual merge...and hopefully sync it ;)
[13:55] <mok0> askand: ... and you didn't change the word "meddelande" you removed it ;-)
[13:56] <askand> ﻿mok0: hm..im not sure what you mean with relative to topdir? It is currently in the topdir? Or do you mean when it is installed?
[13:56] <mok0> askand: you also removed "%(n)" ...
[13:56] <slytherin> \sh: hmm, I will try. But as per my experience I haven't found very friendly changelog entries in Debian changelogs. So it usually hard (for me) to know what exact changes were made.
[13:56] <mok0> askand: "topdir" is the one that contains debian/
[13:56] <askand> ﻿mok0: yea langs.xml is in there
[13:57] <mok0> askand: ah, then you put debian/langs.xml
[13:57] <\sh> slytherin: read the ubuntu changelog...as it is a 0ubuntu version, mostly it was just pushed into ubuntu as new version...so normally debian was too late with a new version, or we have someting specific inside..which can be merged easily
[13:57] <askand> ﻿mok0: nono its in the topdir I mean :)
[13:57] <mok0> askand:  okok :.-)
[13:57] <mok0> hehe
[13:57] <slytherin> \sh: will try
[13:58] <mok0> askand: you are ready to run "debuild -S -sa"
[13:58] <askand> ﻿mok0:  in the topdir?
[13:58] <mok0> yes
[13:59] <mok0> askand: it will ask you to sign with your gpg signature. If you don't have one (get one :-) ) ... you can add "-uc -us" to debuild
[14:02]  * mok0 wonders why gmail-notify crashes on the word "meddelande"...
[14:02] <askand> ﻿***mok0  python does not like the (n) thing
[14:02] <mok0> askand: ok
[14:04] <mok0> askand: if you're interested in localization work, check out the "Translations" tab on Launchpad. There's a nifty system there called "Rosetta" where you can help with translations in a convenient web interface
[14:06] <askand> ﻿ mok0: will check that later, im trying to get a gpgsignature..I had onw before a formatted my computer..
[14:06] <mok0> askand: you don't need the signature to generate the debdiff, so you can wait
[14:06] <mok0> askand: just use "debuild -S -sa -uc -us"
[14:07] <mok0> (-uc and -us means: do not sign .changes and .dsc files)
[14:08] <mok0> askand: (make sure you save a backup of your next signature. It is a big pain + a security risc to loose your private key)
[14:08] <askand> ﻿mok0:  hm it gives me errors.. http://pastebin.com/m388776f3
[14:10] <mok0> askand: hmm, it doesn't like your swedish characters. You can safely delete those lines, though, because you actually need to document not WHAT you did but WHY you did it
[14:10] <askand> ﻿mok0:  ok I see
[14:10] <mok0> askand: the person looking over your debdiff can easily see WHAT has changed, but not WHY (unless you put it in the changelog)
[14:12] <mok0> askand: there is a fairly sophisticated parser for the changelog file, I guess it doesn't like non-ascii characters...
[14:13] <mok0> askand: you also need to "apt-get install cdbs"
[14:15] <james_w> hi askand
[14:15] <askand> ﻿mok0: now it worked!
[14:15] <askand> ﻿james_w:  hi
[14:15] <mok0> askand: cool!
[14:15] <james_w> askand: Swedish characters should be fine, are you using a UTF-8 locale?
[14:15] <mok0> now you should have your new .dsc file
[14:16] <askand> ﻿mok0:  ive got .build, .changes, .dsc and .diff.gz
[14:16] <askand> ﻿ james_w: yes I am
[14:16] <james_w> askand: strange then
[14:16] <mok0> askand: so, you do "debdiff old.dsc new.dsc"
[14:17] <mok0> where "old" and "new" are gmail- .... etc
[14:17] <mok0> james_w: perhaps it is the xml tags it doesn't like??
[14:18] <james_w> mok0: perhaps, askand, what does "okänd rad" mean?
[14:18] <mok0> unknow line
[14:18] <mok0> unknown
[14:19] <james_w> ah, thanks
[14:22] <askand> ﻿mok0: Ok now I have run debdiff
[14:22] <mok0> askand: cool! Attach it to the bug
[14:23] <askand> ﻿ mok0:  attach what? :P
[14:23] <mok0> askand: the output of debdiff
[14:23] <askand> ﻿ james_w: it accepts my swedish letters now by the way, must have been something else that was wrong
[14:23] <mok0> askand: hang on
[14:23] <james_w> askand: cool, glad it works.
[14:24] <mok0> debdiff ﻿﻿﻿﻿﻿gmail-notify_1.6.1-3ubuntu2.dsc gmail-notify_1.6.1-3ubuntu2.1.dsc > ﻿﻿gmail-notify_1.6.1-3ubuntu2.1.debdiff
[14:25] <mok0> askand: the convention is to name your debdiff with the same root name as the new .dsc file
[14:26] <mok0> askand: you can also check with "lsdiff ﻿gmail-notify_1.6.1-3ubuntu2.1.debdiff"
[14:26] <mok0> askand: ... which will give you a list of the files that have changes
[14:27] <askand> ﻿ mok0: you have ﻿gmail-notify_1.6.1-3ubuntu2.1.dsc but I have ﻿gmail-notify_1.6.1-3ubuntu3.dsc
[14:27] <askand> as the new version?
[14:28] <mok0> askand: ah, the ubuntu3 comes from the changelog file
[14:28] <mok0> askand: change it to -3ubuntu2.1
[14:28] <askand> ﻿mok0:  ok then I start over?
[14:29] <mok0> askand: then you run debuild -S -sa -uc -us again
[14:31] <mok0> askand: the 2.1 means that it is bug-fix #1 to -3ubuntu2
[14:31] <mok0> askand: ... and that it is a post-release fix to hardy
[14:32] <mok0> askand: also known as SRU (stable release update)
[14:34] <askand> should I mark it as a patch when I attach it?
[14:34] <mok0> askand: yes
[14:35] <askand> ﻿mok0: ok done! :)
[14:35] <mok0> askand: then, finally, you subscribe ubuntu-universe-sponsors
[14:37] <mok0> askand: ... from the pink menu in LP
[14:38] <askand>  mok0: okok done
[14:38] <mok0> askand: cool. Thanks for your work!
[14:38] <askand> ﻿mok0: thanks for helping out! :)
[14:39] <mok0> askand: np! Now you're a bug fixing expert :-)
[14:39] <mok0> askand: now go fix more bugs :-)
[15:02] <mok0> askand: uploaded. I had to make changes in the changelog file; the changelog parser did not like the <tab> characters at the beginning of each line.
[15:25] <bddebian> Heya gang
[15:27] <geser> Hi bddebian!1!
[15:27] <bddebian> Heya geser
[15:36] <tbielawa> allo all
[15:40] <Iulian> Hello bddebian.
[15:41] <bddebian> Hello tbielawa, Iulian
[18:09] <slomo_> siretart: ffmpeg seems to be a bit unhappy on powerpc... see the gstreamer0.10-ffmpeg/experimental build log. i can't check what goes wrong exactly now but it's probably a segfault somewhere in ffmpeg code that happens only on ppc ;)
[18:10] <siretart> slomo_: I trust that you manage to create a patch based on a nice backtrace. Hint: ffmpeg-dbg might be useful for that
[18:11] <slomo_> siretart: busy atm :)
[18:11] <siretart> slomo_: same here. plus: no ppc hardware
[18:20] <nicolasvw> While looking for the best practice for upgrading a package with a new upstream version (once the package is ready for sponsorship) and I find two possibilities: linking revu upload to LP or attaching an interdiff. What's the recommended way to go?
[18:22] <jdong> nicolasvw: interdiff or full .diff.gz
[18:25] <nicolasvw> thankx jdong
[18:31] <dx9s_work> where can I see all changes to suphp between hardy and gutsy
[18:31] <dx9s_work> I think I found a  major bug
[18:32] <geser> in the changelog
[18:32] <geser> or you compare both source packages
[18:33] <dx9s_work> what WHATEVER reason.. in 7.10 .. suphp only require the parent directory to be own by the same person that the script is running as.. not in hardy .. all parent directories have to be owned by the same person (unless it hits a directory owned by root)
[18:33] <dx9s_work> some really irratating bug
[18:33] <dx9s_work> really pissing me off
[18:34] <dx9s_work> and it is impossible to have "all parent directories" own by the same person in a multi-user website using suphp... makes it completley useless!!!!!!!!!!!
[18:35] <dx9s_work> dann
[18:35] <dx9s_work> have to reverse "debian/patches/10_CVE-2008-1614.dpatch"
[18:36] <dx9s_work> they didn't completely regession test it
[18:36] <dx9s_work> POS!
[18:37] <dx9s_work> who maintains suphp?
[18:37] <YokoZar> Hi, I've had an SRU pending for like 2 weeks now, and it seems to work fine but no one's pushed it out yet...
[18:39] <YokoZar> https://bugs.edge.launchpad.net/ubuntu/+source/wine/+bug/224042
[18:53] <jdong> YokoZar: you need one more tester to say it's working
[18:53] <jdong> YokoZar: afterwards, mark verification-done and remove verification-needed
[18:56] <mok0> siretart: ping
[18:59] <dx9s_work> how can I downgrade to older version of suphp! ?
[19:01] <dx9s_work> from 0.6.2-2ubuntu1 to 0.6.2-2
[19:01] <geser> fetch the deb and install it with e.g. gdebi
[19:03] <dx9s_work> perhaps it would be easier to go deb-src?
[19:03] <dx9s_work> that way I can complete access to the src code
[19:06] <dx9s_work> not as verse on building deb's from src (recent ubuntu/deb convert) .. know how to make .tgz from src for slackware no problem.. seeing apt-get source and apt-get build-deb
[19:06] <siretart> mok0: please don't ping contentlessly
[19:06] <mok0> siretart: sorry. I'd like to ask to get motu powers on revu
[19:08] <dx9s_work> geser, perhaps you can point me at a howto on the process to download the actual source code used by the maintainers to produce the .deb files so I can manually install my own .deb file (and hopefully fix the serious bug in suphp)
[19:08] <siretart> mok0: sure. what's your revu login?
[19:09] <mok0> siretart: mok@bioxray.au.dk
[19:09] <siretart> and your lp id?
[19:09] <mok0> siretart: mok0
[19:09] <geser> dx9s_work: if you have the deb-src lines in /etc/apt/sources.list, simply apt-get source <pkgname>
[19:13] <siretart> Altering mok@bioxray.au.dk to level reviewer
[19:13] <dx9s_work> geser, had to install dpkg-dev
[19:13] <mok0> siretart: thanks!
[19:18] <dx9s_work> geser, so where is the build scripts (aka options passed to configure and so forth and the process for building the .deb .. I know some makefiles have a make option for .deb files)
[19:19] <geser> dx9s_work: debian/rules inside the unpacked source dir
[19:20] <dx9s_work> ah
[19:23] <dx9s_work> okay removed the latest (recent as of last month) patch ... reading up on the process to build and install into the REAL root (or fake root) .. remember I am NEW to .deb's from the maintainer/builder side
[19:27] <dx9s_work> okay have a deb.. now I need to install using dpkg I think it is
[19:28] <dx9s_work> done
[19:28] <dx9s_work> gonna see if removing the patch fixed my problem
[19:29] <mok0> I uploaded torque_2.1.8+dfsg-0ubuntu2 for intrepid earlier today, but it's vanished into blue air. I've not gotten any reject mails, nor can I find it in the build queue. What gives?
[19:30] <geser> mok0: I'm also missing some uploads from today
[19:30] <mok0> geser: I don't know if I should say that's comforting :-)
[19:31] <dx9s_work> CRAP!
[19:31] <dx9s_work> no change.. need to compare a working gutsy machine and this hardy machine closer
[19:32] <geser> mok0: I'm trying to get an answer in #launchpad
[19:33] <mok0> geser: great, perhaps I should join you there...
[19:36] <dx9s_work> it was something that broke (usable but for ONE person... which completely blows the reason for have suphp in the first place) between "suphp (0.6.2-1ubuntu1) "  and later currently 0.6.2-2ubuntu1 (the maintainer has 0.6.3 out.. I might just install manually and screw the the .debs)
[19:38] <mok0> dx9s_work: it may give you some clues on how to fix the debs later
[19:39] <dx9s_work> mok0, just a pain-in-the-arse.. I don't need to be fixed THIS problem.. I have another work-stoppage thing that I am trying to fix and this is a show stopper (hardy's suphp multi-user support.. or lack of it)
[19:40] <mok0> dx9s_work: I know the frustration of cascading problems
[19:42] <mok0> dx9s_work: ... but please, don't take it out on us ;-)
[19:43] <dx9s_work> is there a way to "apt-get source xxxxxx-some-older-version" ... even trying to get "apt-get source libapache2-mod-suphp_0.6.2-2ubuntu1" (which is the correct name /version) doesn't work
[19:43] <dx9s_work> oh it's not anyONES fault.. just a pain when you (me in this case) don't know the source process very well w/ deb's
[19:43] <dx9s_work> if it was slackware.. I'd have it done by now
[19:44] <RainCT> dx9s_work: you can get older version from http://packages.ubuntu.com, if they are still on some repo
[19:45] <RainCT> (there's a link the the .dsc file at the left of the info pages. to download the source do:  dget <url to the dsc file>; dpkg-source -x *dsc)
[19:45] <geser> LP has also older versions
[19:46] <dx9s_work> I want to get really good at this .deb stuff so you'll have to bare w/ me
[19:46] <mok0> dx9s_work: work out what the problem is first, then come here and get help updating  the package
[19:46] <mok0> dx9s_work: ... and open a bug on LP
[19:47] <mok0> dx9s_work: that will help the devs keep track of the progress
[19:47] <geser> dx9s_work: go to https://launchpad.net/ubuntu/+source/suphp, select the version you want, and dget the .dsc file (dget is in devscripts)
[19:48] <mok0> geser: not much action on #launchpad :-/
[19:49] <geser> mok0: I know :(
[19:53] <mok0> geser, I see some discussion on -devel about shh keys. Could that have to do with the upload problem+
[19:53] <mok0> s/+/?/
[19:55] <geser> mok0: I doubt it, I can't imagine how the ssh-key issue might affect the gpg signatures from uploads
[19:55] <cbx33> hey guys
[19:55] <cbx33> anyone here use NX?
[19:55] <dx9s_work> okay hopefully installed 0.6.2-1ubuntu1 (from gutsy days into hardy)
[19:55] <jdong> cbx33: used to, haven't bothered to set it up recently.
[19:55] <jdong> (100mbit internet --> not much care for NX efficiency)
[19:56] <cbx33> jdong: was wondering how to regen the key it comes with
[19:56] <jdong> cbx33: I doubt it's vulnerable.
[19:56] <dx9s_work> yippie
[19:56] <dx9s_work> that fixed it!
[19:56] <dx9s_work> some bug between what gutsy has in 0.6.2-1ubuntu1 and later
[19:56] <cbx33> jdong:
[19:56] <dx9s_work> (what hardy has)
[19:57] <cbx33> well i just ran ssh-vulnkey
[19:57] <cbx33> and it came back wit hthis
[19:57] <cbx33> COMPROMISED: 1024 xx:XX:XX:XX:XX:XX:XX
[19:57] <cbx33> no-port-forwarding,no-agent-forwarding,command="/usr/NX/bin/nxnode"
[19:57] <cbx33> where xx is the fingerprint
[19:57] <dx9s_work> mok0 and geser ... I'll have to spend time and research what/where the problem is later.. but rolling back to older source from gutsy days fixed it
[19:59] <cbx33> jdong: what ya think?
[20:01] <mok0> dx9s_work: fine, but please take a minute or two to open the bug on LP
[20:09] <dx9s_work> mok0, it says ( https://launchpad.net/ubuntu/hardy/+source/suphp/0.6.2-1ubuntu1 ) ... removal requested on 2007-11-11 ... is there a way to determine WHO requested it / approved it?
[20:09] <dx9s_work> as the superseded version must have been tested (possibly poorly) by somebody and I need to inform that person how to test it and future releases for this bug
[20:10]  * mok0 looks
[20:11] <jdong> cbx33: I frankly woulnd't care
[20:11] <jdong> cbx33: the nx key is public anyway
[20:11] <jdong> cbx33: it allows all users with an nx pubkey to log in to nx@your_host
[20:11] <jdong> cbx33: but user nx only spawns NX shells that allow a further login.
[20:11] <james_w> dx9s_work: in this case it means automatically, as a new version was uploaded
[20:12] <ScottK> dx9s_work: https://launchpad.net/ubuntu/+source/suphp/ - The only change appears to have been security related.
[20:12] <jdong> cbx33: i am not a crypto expert but I don't think a compromise of the nx user login is any worse than what nx does by default...
[20:14] <mok0> dx9s_work: It looks like 0.6.2-1ubuntu1 was superseded by a debian sync
[20:14] <dx9s_work> james_w, ScottK, problem is it causes it to be highly un-usable... and all files / directories must be own by one person... might as well just use suexec instead for the entire site over suphp .. older 0.6.2-1ubuntu1 days allw for multiple users (assuming the immediate parent directory is owned by the same person) ...  big feature difference.. I assume it was a bug due to how it was tested before publishing
[20:15] <ScottK> dx9s_work: I think your assuming I care more than I do.  You asked a question.  I answered it.  Sorry I can't help you more.
[20:15] <dx9s_work> np thanks ScottK
[20:15] <james_w> dx9s_work: https://edge.launchpad.net/ubuntu/+source/suphp/0.6.2-2 looks like the upload that probably added the change
[20:16] <james_w> https://edge.launchpad.net/ubuntu/hardy/+source/suphp/0.6.2-2 shows it better
[20:16] <mok0> ... but the current hardy version is  0.6.2-2ubuntu1
[20:17] <dx9s_work> I think the 10_CVE-2008-1614 in the hardy version might solve one minor (really minor) security problem in place of a huge feature drop
[20:17] <mok0> dx9s_work: hasn't that been addressed by https://edge.launchpad.net/ubuntu/hardy/+source/suphp/0.6.2-2ubuntu1
[20:18] <dx9s_work> I dunno.. I DL'ed the source for 0.6.2-2ubuntu1 and remove the patching for 10_CVE-2008-1614 .. and that didn't solve it ... it could also be the AddType change from x-http-php to application/x-http-php
[20:18]  * dx9s_work looks now at the url
[20:19] <james_w> dx9s_work: that patch fixes a race condition, it shouldn't normall change anything that isn't racy.
[20:19] <dx9s_work> I really don't know what/where .. the issue is..
[20:20] <dx9s_work> but if the fact that php code one run under hardy's version unless the parent directory and the parent's parent directory and the parents parents parents directory are ALL owned by the same person ... (until it hits a directory that root owns)
[20:20] <dx9s_work> one run=won't run
[20:20] <james_w> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416424 is the bug fixed there.
[20:21]  * dx9s_work reads
[20:24] <dx9s_work> hmmm..
[20:25]  * dx9s_work quotes "
[20:25] <dx9s_work> Indeed, it's not a bug in suPHP, but it's a bug in the libapache2-mod-suphp
[20:25] <dx9s_work> package because it contains the Apache configuration file and ships with an
[20:25] <dx9s_work> insecure configuration.
[20:25]  * dx9s_work "
[20:25] <dx9s_work> will look at that closer
[20:31] <dx9s_work> set it up using the alternate method (addtype versus addhandler) .. and moved back to 0.6.2-2ubuntu1 .. and same problem with parent and grandparent directory ownership
[20:31] <dx9s_work> so no
[20:32] <dx9s_work> the answer is that issue fixed something but created another problem
[20:34] <cbx33> ko jdong
[20:34] <dx9s_work> gonna hafta roll back to 0.6.2-1ubuntu1 .. suphp in hardy is broken
[20:55] <dx9s_work> well rolled back to 0.6.2-1ubuntu1 and used sethandler+filesmatch (workaround) method. that should be paranoid enough and still work for many people on the same site (until I get time to look at 0.6.3 reference code and test it out)
[21:07] <geser> mok0: I just got the accepted mails for my uploads. So whatever was broken got fixed.
[21:11] <mok0> geser: me too
[21:38] <mok0> What software do they use at BTS to generate those little box & arrow diagrams?
[21:40] <norsetto> mok0: you mean the useless version graph?
[21:41] <mok0> norsetto: yes :-)
[21:44] <norsetto> mok0: knowing debian its some perl script ....
[21:44] <mok0> norsetto: yeechh
[21:45] <mok0> norsetto: of course I could probably find the source code somewhere and find out...
[21:46] <norsetto> mok0: try searching for perl and graph
[21:51] <andrew___> mok0: that sort of thing is normally done with Graphviz (I don't about this particular case though)
[21:59] <mok0> andrew___: thx I will check that out!
[22:17] <norsetto> ScottK: you may want to check bug 229776
[22:17] <ScottK> norsetto: I have it on my list to look at.
[22:18] <norsetto> ScottK: ok
[22:18] <ScottK> I'm subscribed to the package bugs via pythonistas.
[22:18]  * norsetto wonders what is the diff between a pythonero and a phytonista
[22:19] <ScottK> For the teams, one is for Main packages and the other for Universe.
[22:19] <ScottK> I've no idea of the exact reference from which the team names came from though.
[22:21] <ScottK> mok0: Why did you add a Linda over-ride to Torque?  It's been removed from the archive.
[22:33] <LaserJock> ScottK: ping?
[22:33] <ScottK> Pong
[22:34] <ScottK> LaserJock: ^^^
[22:34] <LaserJock> ScottK: you know anything about the qt4 backports?
[22:35] <ScottK> I know how they are being done.  I haven't been invovled directly in the doing.
[22:35] <LaserJock> hmm, k. Does Riddell do them?
[22:35] <ScottK> Yes.
[22:36] <ScottK> He figured a way to build them on a PPA and then copy them to backports so they don't have to get in line behind Intrepid builds.
[22:36] <LaserJock> interesting
[22:37] <LaserJock> it seems the QT4 4.4 packages kill at least lyx
[22:37] <LaserJock> looking into stellarium as well, not sure about it
[22:37] <ScottK> Everyone knows backports are crack ;-)
[22:37] <ScottK> K.
[22:37] <LaserJock> sure
[22:38] <LaserJock> it's just a bit odd since it's a library backport
[22:38] <ScottK> It's tied to and needed for the whole KDE4 4.0.4 backport.
[22:38] <LaserJock> i.e. you install one thing from -backports and it kills other things from the stable repo
[22:38] <LaserJock> sure
[22:39] <LaserJock> I'm just trying to figure out the best course of actions
[22:39]  * ScottK tends to enable backports, install the one thing he wants, and turn them back off again.
[22:39] <ScottK> Sure.
[22:39] <ScottK> I'd say file bugs and whine at Riddell for now.
[22:39] <LaserJock> apparently there is a new version of Lyx that will work with QT4 4.4
[22:39] <LaserJock> I wonder if I should try to push that into Intrepid and backport it
[22:40] <ScottK> I think that'd be excellent.
[22:45] <Jazzva> norsetto: I'm almost done with gecko-mediaplayer. I noticed that there is src/nsIScriptableGeckoMediaPlayer.h which is generated in build process, but not removed in clean process. Should I remove it in clean rule?
[22:46] <LaserJock> ScottK: sweet, apparently this QT4 4.4 issue has been fixed by Debian
[22:46] <norsetto> jazzva: strange, let me check
[22:46] <Jazzva> Ok
[22:48] <ScottK> Kewl.
[22:48] <ScottK> Sounds like some core-dev should do a merge ....
[22:48] <ScottK> See you all later.
[22:48] <norsetto> l8r
[22:52] <norsetto> Jazzva: yes, add it to the clean target
[22:53] <Jazzva> Ok...
[22:54] <LaserJock> jdstrand: ping
[23:00] <Jazzva> norsetto: Uploaded diff.gz. Bug 229335
[23:01] <norsetto> jazzva: thx
[23:01] <Jazzva> np :)
[23:02] <norsetto> jazzva: and pls. subscribe me :-)
[23:03] <Jazzva> Ok
[23:04] <Jazzva> done
[23:04] <Jazzva> :)
[23:16] <norsetto> g'night all
[23:28] <ScottK> LaserJock: The whole point of merging MoM/DaD to get comments there is so that the place you go look to see if a merge needs doing also has some informal status information.  Everyone file a bug is way overkill.
[23:30] <LaserJock> ScottK: well, considering that contributors need to do it anyway I don't think it's all that much of a stretch
[23:30] <LaserJock> but perhaps MoM+comments is the way to go when that's done
[23:30] <ScottK> But we've already got a plan for one stop shopping.
[23:30] <ScottK> That should be be very soon I think.
[23:30] <LaserJock> anyway, that wasn't really the point
[23:31] <LaserJock> my point is that we need everybody to check the canonical  location
[23:31] <LaserJock> in this case, if the developer had checked  for a merge bug it the problem would have been avoided
[23:31] <ScottK> If you insist on a centralized model that's true.
[23:31] <ScottK> Agreed.  And we don't need a new rule for that.
[23:32] <LaserJock> I was trying to encourage MOTUs and contributors to check before doing the work
[23:33] <ScottK> Which is good.  Just don't make me file work tracking bugs.
[23:33] <LaserJock> well
[23:33] <LaserJock> you need to grab your merges in some way that everybody's going to see
[23:33] <LaserJock> we used to do that via bugs
[23:33] <LaserJock> but MoM is probably better
[23:33] <ScottK> I think we used to do it via ask the person that touched it last if that wasn't you, but whatever.
[23:34] <LaserJock> I just think thats stupid, sorry :-)
[23:34]  * ScottK goes outside to enjoy sunshine with his daughter ....
[23:34] <LaserJock> I'm sitting here right now waiting for a pong on a merge
[23:35] <ScottK> Well so work on something else.  I think filing pointless bugs is stupid.
[23:35] <LaserJock> I could have done it a while ago and moved on to the real work I wanted to do, but instead I'm gonna have to wait a day just to get an OK to do a merge
[23:35] <crimsun> LaserJock: for a Universe source package?
[23:35] <LaserJock> I think people should rather "grab" the ones they do want to do and let everybody else get on with it
[23:35] <LaserJock> crimsun: main
[23:36] <crimsun> LaserJock: I don't see why you would wait unless it's a fairly critical source package.
[23:36] <crimsun> and even then, you're in main - people can just deal.
[23:36] <LaserJock> crimsun: because that's what ScottK says people should do :-)
[23:36] <mok0> Hmm, no openssh update for Lenny?
[23:36] <LaserJock> and I don't want to get yelled at :-)
[23:37] <ajmitch> LaserJock: we could always just list all the merges on a wiki page & lock them that way...
[23:37] <crimsun> hey, that sounds like a brilliant idea1
[23:37] <crimsun> oh wait...
[23:37] <ajmitch> crimsun: but wasn't it fun to edit?
[23:37] <crimsun> hehe
[23:39] <LaserJock> ajmitch: we already have tools, I'm sure we can do better than a wiki page
[23:40] <LaserJock> although wiki pages are better than nothing, IMO
[23:40] <ajmitch> LaserJock: crimsun knows that pain that I'm talking about :)
[23:42] <LaserJock> ajmitch: I remember
[23:43] <ajmitch> we moved on to having bugs filed, which were scraped for sistpoty's merge tool
[23:43] <LaserJock> ajmitch: I thought that was a decent idea, though it seemed a bit fragile
[23:44] <LaserJock> I think a python-launchpad-bugs run version would work better
[23:44] <LaserJock> but MoM comments would be much better methinks
[23:45] <ajmitch> it was fragile in a sense, but it worked
[23:46] <LaserJock> did we get down to a 0 merge list?
[23:46] <ajmitch> we got close
[23:46] <ajmitch> some packages would just fail due to other changes to the system
[23:47] <ajmitch> old, crufty stuff usually
[23:47] <ajmitch> though that would happen far more often with the rcbugs list (which won't be updated anytime soon due to recent debian security changes)
[23:48] <LaserJock> bah