[12:58] <LaserJock> imbrandon: you send that keyboard?
[12:59] <tonyyarusso> LaserJock: for?
[01:00] <LaserJock> a sun machine
[01:00] <tonyyarusso> ?
[01:00] <tonyyarusso> oh
[01:01] <tonyyarusso> LaserJock: Sorry - I'm behind in the scrollback.  gmail filter for?
[01:02] <LaserJock> everything
[01:02] <imbrandon> LaserJock: yea about 2 days ago
[01:02] <LaserJock> imbrandon: k
[01:02] <LaserJock> thanks
[01:02] <LaserJock> I'm not sure if this is the most efficient way or not, but I've got this as one filter:
[01:03] <LaserJock> ((replyto:*@bugs.launchpad.net OR archive@ubuntu.com) OR (to:(@lists.ubuntu.com OR @lists.canonical.com) -(edubuntu)) -("Launchpad Bugs") -("Edubuntu Bugs"))
[01:04] <tonyyarusso> nice
[01:04] <LaserJock> that's my "everything *buntu except Edubuntu stuff and Launchpad bug" filter
[01:04] <tonyyarusso> You do all of your ubuntu stuff in one filter?
[01:05] <LaserJock> I cutting down on how many labels/folders I'm using
[01:05] <LaserJock> 1 per project
[01:06] <LaserJock> so I have 10 labels
[01:10] <LaserJock> alrighty folks, time for me to go back "underground". cya
[01:54] <crimsun> apologies for the absence; I'm digging through ~15k emails in reverse-chrono.  Congrats to everyone who made -motu and -core-dev!
[01:54] <ajmitch> hi crimsun, good to see you alive still :)
[01:54] <ajmitch> I know how the mail pile feels
[01:55] <AstralJava> Just survived from about a 10k hurdle... :)
[01:55] <AstralJava> Pretty much ready to crash now.
[02:09] <crimsun> nice to see the audio bugs keep rolling in
[02:10] <TheMuso> crimsun: Yeah, mostly related to that damn hda-intel module.
[02:17] <leonel> looking  at   http://www.ubuntu.com/usn   I see advisories for  security vilnerabilities     how the  non security bugfixes  handled ?
[02:17] <TheMuso> leonel: Stable release updates process.
[02:17] <TheMuso> !SRU
[02:17] <ubotu> Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates for main and restricted, while https://wiki.ubuntu.com/MOTU/SRU is for universe and multiverse.
[02:18] <leonel> TheMuso:  thank  you  ..  reading ...
[02:58] <Amaranth> dang, i thought getting 20 mails an hour was bad
[03:03] <RAOF> Amaranth: Thinking of which, someone wants to get kvm sync'd from debian to the tune of US$250.
[03:03] <Amaranth> what?
[03:04] <Amaranth> don't we have the latest kvm? i thought it was required for the 2.6.22 kernel
[03:04] <RAOF> Amaranth: Not at all.  We've got 28, which is enough.
[03:06] <RAOF> But 36, or whatever debian has, has (1) guest SMP support, and probably fixes some minor bugs.
[03:06] <Amaranth> their website is useless
[03:07] <Amaranth> doesn't tell me anything
[03:07] <Amaranth> if it fixes gfxboot i'll be pushing for it anyway :P
[03:07] <RAOF> Amaranth: File some bugs, and I'll see if I can make a UVFe case.
[03:07] <Amaranth> RAOF: but i have no idea what it fixes
[03:08] <Amaranth> so i don't know if i care
[03:08] <Amaranth> their website still says "Installation requires -no-kvm on Intel"
[03:11] <RAOF> AHA!  That's why my xgl upgrade testing seems non-deterministic!
[03:11] <RAOF> It's a good idea to test upgrades from the version in the archives, rather than the locally built one I have lying around :)
[03:27] <ajmitch> keescook: you're brave (pam)
[03:29] <ajmitch> afaik it's only been in unstable for a short time
[03:30] <ajmitch> ok, 10 days
[03:31] <pwnguin> thats long enough to make testing ;)
[03:34] <ajmitch> not when there's been 2 subsequent uploads
[03:36] <pwnguin> well doh
[03:51] <ajmitch> nealmcb: they probably won't mind too much in the server channel, at least it's about ubuntu still :)
[03:53] <nealmcb> oops - I meant to delete the maintainer's name from the gdebi package so he doesn't get spammed.....
[03:53] <ajmitch> mvo?
[03:53] <nealmcb> so is there a way to delete ppa packages that don't build?
[03:54] <nealmcb> ajmitch: Michael Vogt?
[03:54] <pwnguin> nealmcb: ive read not yet
[03:55] <Hobbsee> nealmcb: why are you *uploading* packages which odnt build?
[03:55] <ajmitch> nealmcb: yes, I think that he's probably listed as maintainer
[03:55] <ajmitch> and I think deleting is still a few weeks away :)
[03:57] <pwnguin> Hobbsee: id say half the ppa value is building the package for you. -mobile comes to mind
[03:57] <nealmcb> Hobbsee: I got encouraged by sabdlf's mail asking folks to test ppa, so I just jumped in, knowing very little about packaging, but more than some others that are gonna jump in soon if it takes off :-)
[03:57] <Hobbsee> pwnguin: oh, true.  i was thinking failed to build on *every* arch.
[03:57] <Hobbsee> pwnguin: you know, dos'ing the builds with stuff that fails, and all...
[03:58] <pwnguin> Hobbsee: well, it's against the policy to do that, and they're supposed to have some detection, though i'd wager some amount of fair scheduling should be present
[03:59] <Hobbsee> as long as they bump the motu's priority... :_)
[03:59] <bddebian> Heya gang
[03:59] <tonyyarusso> eh?  PPA won't build for lpia, only the two main ones.
[04:00] <ajmitch> Hobbsee: and I suppose you'll request a special priority for yourself? :)
[04:00] <RAOF> I should really file a bug on that.  If you upload a package, and then packages that are dependennt on that package, the dependent packages get queued first, then go into DEPWAIT... forever.
[04:00] <pwnguin> lol
[04:00] <Hobbsee> ajmitch: nah.  just motu.  which i happen to be in
[04:00] <Hobbsee> ajmitch: besides, i have other places to build, if i wish
[04:01] <RAOF> Oh, that and the crazy timer skew, which is killing all my amd64 builds.
[04:01] <ajmitch> I wouldn't mind other places to build stuff
[04:02] <pwnguin> i wouldnt be surprised to see people use ppas to build custom kernels
[04:02] <bddebian> I am wondering.  Should I really be "fixing" these FTBFSs if we already have the binaries?  Maybe I'm causing more greif than solving?
[04:02] <Hobbsee> bddebian: if we already have the binaries?
[04:02] <RAOF> bddebian: What if we later want to fix bugs in them?  It's nice to start with something that builds :)
[04:03] <nealmcb> ajmitch: I wonder what it would take to put up an ec2 image that could do builds....
[04:03] <ajmitch> nealmcb: ec2?
[04:04] <ajmitch> bddebian: security or stable release updates will be much easier
[04:04] <nealmcb> amazon's ec2 - rent a xen server by the hour - $0.10/hr
[04:04] <ajmitch> interesting
[04:04] <nealmcb> "elastic compute cloud"
[04:04] <ajmitch> that reminds me, i need to ask about some hosting
[04:04] <ajmitch> the old days of buying CPU time
[04:04] <bddebian> OK, OK
[04:04] <nealmcb> It is expensive if you want to run it around the clock, but cheap for extra bursts of capacity
[04:05] <bddebian> Hobbsee: Yes in many cases we already have binaries in the archive but the source packages FTBFss
[04:05] <nealmcb> I figure ec2 is good for server testing too - don't have to worry about finding or trashing a spare server
[04:05] <Hobbsee> bddebian: different versions, presumably
[04:05] <pwnguin> nealmcb: that's what vmware / xen is for ;)
[04:05] <bddebian> Hobbsee: Nope :_(
[04:06] <bddebian> When they sync from Debian do they just grab the existing binaries or do they build the source?
[04:06] <nealmcb> pwnguin: yeah, for folks that have the unused memory and cpu
[04:06] <bddebian> Or maybe these are so old we have just had the binaries forever? :-)
[04:06] <RAOF> bddebian: I know.  Xgl was an example.  We only sync source packages from debian.
[04:06] <RAOF> bddebian: Probably some libraries changed, that's what happened to xgl.
[04:06] <bddebian> uclibc hasn't seen an update since 2005 :-)
[04:07] <bddebian> RAOF: Aye.  Lots of gtk related stuff
[04:09] <bddebian> I wish I could fix uclibc it's breaking lots of stuff but it needs lots of help
[04:09] <nealmcb> so when headers and such change, do ppa packages get rebuilt automatically?
[04:10] <ajmitch> nope
[04:10] <ajmitch> there are no automagic rebuilds
[04:10] <ajmitch> I doubt that will be implemented any time soon
[04:11] <StevenK> It hasn't even been implemented for the main archive.
[04:12] <ajmitch> the likelihood of that is still small, i think
[04:12] <pwnguin> you'd have to identify some sort of "rebuild depenency"
[04:21] <TheMuso> Hobbsee: heh love your post on lp-users. :)
[04:21] <Hobbsee> TheMuso: :D
[04:21] <nealmcb> is there a set of packages that can do remote builds, e.g. as a web service or via bzr/ssh/scp?
[04:22] <ajmitch> nealmcb: yes, but they're not easy to setup
[04:22] <ajmitch> I think falcon might trigger pbuilder now, so you could look for that
[04:23] <RAOF> nealmcb: You can actually use dput to do that, if you want.  It can trigger a remote program, I think.
[04:24] <ajmitch> mini-dinstall can do a post-upload hook
[04:25] <ajmitch> http://blogs.ubuntu-nl.org/dennis/2007/08/03/package-build-coordination/
[04:28] <nealmcb> falcon looks right-on - http://www.kaarsemaker.net/software/falcon/
[04:30] <RAOF> nealmcb: Oh, yes.  Once beta 3 is out.  Poke seveas, and/or hack on the code :)
[04:31] <nealmcb> RAOF: great - so combining falcon on a temporary ec2 machine with a mirror to a normal web site for a repository somewhere, and dput  on the client side, and you too can run a build infrastructure on the cheap :-)
[04:32] <nealmcb> but only worthwhile if you need some big builds that would tax your local hardware
[04:32] <RAOF> Or you just want to offload a whole bunch.
[04:33] <jmg> nealmcb: an ec2 box is not guaranteed to be an faster than an athlon 2400
[04:33] <RAOF> Also, you end up with a proper repository.
[04:33] <nealmcb> it takes several minutes to just get an ec2 machine up and running
[04:34] <nealmcb> jmg: right - individual ec2 machines aren't the fastest.  but if falcon can manage multiple build machines, they'd be great in parallel
[04:35] <ajmitch> like a full archive rebuild?
[04:35] <jmg> i imagine one could combine it with distcc
[04:35] <nealmcb> but they're faster than the machines some folks have, like me at the moment...
[04:35] <ajmitch> jmg: no, packages need to be modified to use that
[04:35] <ajmitch> make isn't run with -j
[04:35] <jmg> ajmitch: i thought it was just a matter of an environment flag
[04:36] <jmg> ok
[04:36] <ajmitch> and many packages can just fail with -j
[04:36] <jmg> well
[04:36] <ajmitch> due to undeclared file dependencies in the makefile
[04:36] <jmg> you could build multiple packages at once across multiple machines
[04:36] <jmg> for sure
[04:36] <jmg> and with ec2
[04:36] <ajmitch> yes
[04:36] <jmg> you could just bring up n machines
[04:36] <jmg> to compile n packages
[04:36] <jmg> at once
[04:36] <ajmitch> and lucas runs a full rebuild over many fast machines
[04:37] <jmg> if you tried to run a full rebuild of main/universe/multiverse using n machines
[04:38] <jmg> it'd probably crash ec2
[04:38] <nealmcb> so under what circumstances and how often do folks tend to want to build a bunch of packages?
[04:38] <nealmcb> jmg: they limit you to 20 at once unless you talk to them....
[04:39] <ajmitch> I wonder how many xen domains they pack on a physical box
[04:40] <nealmcb> "equivalent of a system with 1.7Ghz x86 processor, 1.75GB of RAM, 160GB of local disk, and 250Mb/s of network bandwidth."
[04:40] <bddebian> StevenK: Nice! (popplerkit)
[04:41] <ajmitch> nealmcb: i/o contention with many domains compiling stuff will hurt
[04:43] <nealmcb> ajmitch: yeah - they've talked about ways to hint to ec2 about which virtual machines you want near or far from each other, but last I heard they hadn't exposed a way to do that
[04:47] <nealmcb> oh cool - falcon uses django, my favorite
[05:05] <bddebian> Will archive admins give back packages for rebuilds or are we supposed to still do build1 versions?
[05:06] <tonyyarusso> Why is it that the source packages for universe are processed more slowly on the new queue than other things?
[05:07] <TheMuso> bddebian: Admins can give back.
[05:07] <bddebian> TheMuso: Thanks
[05:07] <TheMuso> build1 is only used to rebuild a package against newer libs, etc.
[05:07] <Hobbsee> tonyyarusso: because it's on an importance basis, basically
[05:08] <tonyyarusso> Hobbsee: ah.
[05:08] <tonyyarusso> Still makes a little part of me cry inside when I see "No Currently building builds for The Gutsy Gibbon." when there are 24 waiting in line :(
[05:09] <bddebian> TheMuso: What would the difference be?
[05:10] <TheMuso> bddebian: No need to re-upload a package to be rebuilt if none of its deps have changed is it.
[05:11] <TheMuso> There are a lot of build1 packages in universe. Take a look and you will see what I mean. Rebuilds only to build against a newer library, etc.
[05:11] <bddebian> I know because that was how we used to do it but I never understood it
[05:12] <Hobbsee> tonyyarusso: then that suggests there's something wrong with teh buildds
[05:12] <bddebian> If they will give-back, why would we ever do build1 revisions?
[05:12] <TheMuso> bddebian: A library that a package depends on has a new ABI.
[05:13] <TheMuso> for example.
[05:13] <TheMuso> ABI bump even.
[05:13] <tonyyarusso> Hobbsee: oh really?  Not just that they didn't get around to marking things as approved today before going home?
[05:13] <ajmitch> bddebian: because you can't replace a binary package with a new one of the same version
[05:13] <ajmitch> givebacks are only used when the source hasn't built for that version on the arch specified
[05:13] <bddebian> Ah ha, gotcha
[05:13] <Hobbsee> tonyyarusso: it shouldnt need a manual approval.
[05:14] <tonyyarusso> Hobbsee: erm, then what's the difference between NEW and APPROVED ?
[05:14] <tonyyarusso> Hobbsee: ACCEPTED, rather.
[05:15] <Hobbsee> new == new packages to ubuntu, ie, new sources, or new binaries
[05:15] <Hobbsee> that the source package isnt already in ubuntu for
[05:15] <tonyyarusso> right, those are the ones that are just sitting
[05:20] <tonyyarusso> Hobbsee: Sorry, I'm still confused about how this process works.
[05:20] <ajmitch> binaries aren't built until the source is accepted
[05:20] <bddebian> Then the binaries have to be accepted once they build
[05:20] <Hobbsee> tonyyarusso: right, things only go to the NEW queue, if a) the source package is not currently already in ubuntu
[05:21] <Hobbsee> or b) if there are new binaries built from the source package, compared to the last source package.
[05:21] <Hobbsee> everything else goes to accepted, assuming it's with a good key
[05:21] <Hobbsee> TheMuso: rmadison -u ubuntu foo
[05:22] <guest22> Could someone please explain the implications of the current new package freeze? Does this mean there will be no new Universe packages in gutsy, or just until release? Will all new REVU uploads have to be for the next release?
[05:22] <StevenK> TheMuso: rmadison -u ubuntu -a <arch> -s <rel> <package>
[05:22] <ajmitch> no new packages in gutsy, and yes, for the next release
[05:22] <bddebian> guest22: Yes, pretty much anything new to Ubuntu will not be in Gutsy
[05:22] <tonyyarusso> ajmitch, bddebian, Hobbsee: So for the ones that are legitimately new, are they looked over and okayd for building by hand or not?
[05:22] <Hobbsee> guest22: no new packages in gutsy at all, without a freeze exception, at all.  new revu uploads will probably get archived.
[05:23] <TheMuso> ok will check it out.
[05:23] <TheMuso> bbl
[05:23] <Hobbsee> tonyyarusso: yeah.  although not built by hand - they get thrown to the buildds and such
[05:23] <tonyyarusso> Hobbsee: Ok.
[05:23] <bddebian> heh
[05:23] <bddebian> More like hamsters on wheels
[05:24] <guest22> bddebian and Hobbsee: Thanks
[05:24] <guest22> Hobbsee: If new REVU uploads are to be archived, when will the next review cycle start? As soon as gutsy has been released?
[05:25] <Hobbsee> guest22: after the toolchain for hardy is built, i expect.
[05:26] <StevenK> Maybe the toolchain will be ready-ish when the archive opens, like Gutsy
[05:26] <Hobbsee> guest22: basically, it's so that people have time to fix bugs, without having emphasis on reviewing everything.
[05:26] <Hobbsee> StevenK: that would be nice.
[05:27] <guest22> Hobbsee: OK. Another question: do packages submitted for gutsy have to be re-uploaded to REVU for inclusion in hardy, or is that automatic?
[05:27] <StevenK> They have to be re-uploaded, since they require changes.
[05:28] <StevenK> (gutsy -> hardy, in the debian/changelog as a smallest case)
[05:28] <guest22> StevenK: Understood, thanks.
[05:28] <StevenK> bddebian: What about popplerkit?
[05:29] <ajmitch> we haven't made any rules yet about what will go into hardy or when freeze dates will be, given that it's an LTS release
[05:29] <StevenK> Can we boot out php5? Please?
[05:30] <ajmitch> tempting...
[05:30] <StevenK> Indeed ... :-)
[05:30] <ajmitch> how about dropping python2.4?
[05:30] <StevenK> I wasn't aware that we'd dropped 2.3
[05:30] <ajmitch> just chuck in python 3000, noone will notice
[05:31] <StevenK> ajmitch: from __future__ import braces
[05:31] <ajmitch> hah
[05:32] <ajmitch> well python 3k just had an alpha release
[05:32] <ajmitch> as did samba4
[05:32] <StevenK> ajmitch: Have you tried it? It's funny. :-)
[05:32] <bddebian> StevenK: Didn't you just upload it?
[05:32] <ajmitch> yes, I've seen it in the past
[05:32] <StevenK> bddebian: Yup
[05:32] <bddebian> Yeah, thanks.  I tried to fix that damn thing back in Edgy I think
[05:33] <StevenK> I only had to fix a Poppler 0.6 API change ...
[05:33] <ajmitch> I think that the main thing holding it in there is zope3
[05:34] <StevenK> Ahhh, zope.
[05:34] <bddebian> StevenK: Well you are still a stud :-)
[05:34] <ajmitch> he's married, remember
[05:36] <bddebian> So far as you know :)
[05:36] <bddebian> Damn you try to compiment someone and what do you get.. Sheesh..
[05:37] <ajmitch> bddebian: I've actually met StevenK
[05:38] <ajmitch> and survived
[05:38] <Hobbsee> and me
[05:38] <ajmitch> quite true
[05:40] <bddebian> Wow, not THATs a feat :-)
[05:40] <bddebian> ajmitch: Of course you don't take compliments for shite either :-)
[05:40] <ajmitch> of course I don't
[05:40] <bddebian> OK, spiftacity is borked
[05:41] <ajmitch> no kidding
[05:41] <ajmitch> it should be removed
[05:43] <StevenK> What's a compliment? :-P
[05:44] <ajmitch> I think it's something that employees do when around their boss
[05:44] <chillywilly> hi
[05:44] <chillywilly> no, that would be ass kissing ;)
[05:44] <ajmitch> same thing
[05:45] <chillywilly> how's it going dude?
[05:45] <ajmitch> alright
[05:45] <bddebian> Heya chillywilly
[05:46] <chillywilly> hi buddy
[05:46] <bddebian> So I think I'll file a removal request for spiftacity.  Anyone opposed?
[05:46] <ajmitch> not at all
[05:46] <chillywilly> so when's the next release? :)
[05:46] <ajmitch> it's only metacity with modified makefiles to generate a new binary with compositing enabled
[05:46] <bddebian> "When it's ready" ;-P
[05:46] <ajmitch> chillywilly: exactly when it's been scheduled for the last few months
[05:47] <chillywilly> our "linux guy" tried to tell me the other day tht edgy was newer than feisty and I was like "I don't think so"
[05:47] <chillywilly> ajmitch: when is the date?
[05:47] <ajmitch> !gutsy
[05:47] <ubotu> Gutsy Gibbon is the code name for the next release of Ubuntu (7.10) | (due October 2007) | It is development software, as such unstable, support _only_ in #ubuntu+1
[05:47] <ajmitch> hm, no release schedule link there
[05:47] <chillywilly> thanks
[05:47] <ajmitch> wiki.ubuntu.com/GutsyReleaseSchedule
[05:48] <chillywilly> good enough for me
[05:48] <ajmitch> if he tried to tell you that, he's an idiot
[05:48] <bddebian> @#$%^ LP
[05:49] <chillywilly> well he's normally a pretty bright guy, but I knew he was dead wrong
[05:49] <chillywilly> oh well I didn't feel like arguing the point so I just let it go
[05:49] <nealmcb> Is there a way to get email when a package successfully builds after a dput?  Or do I have to sit and watch the web status page?
[05:49] <ajmitch> nealmcb: unlikely
[05:50] <chillywilly> go do something fun and check back later?
[05:50] <chillywilly> ;P
[05:50] <ajmitch> I don't know the rules for emailing build results from PPAs
[05:50] <Hobbsee> you do get emails
[05:50] <Hobbsee> or used to
[05:50] <ajmitch> whether it takes the name from the changelog
[05:50] <pwnguin> i get emails for failures
[05:50] <nealmcb> I didn't get anything for the ppa I just built.  I think this is gonna be confusing for newbies.
[05:51] <pwnguin> and for accepting uploads
[05:51] <chillywilly> hmm, ok so mid October
[05:51] <chillywilly> fun
[05:51] <pwnguin> but nothing for "it's done"
[05:51] <ajmitch> pwnguin: right
[05:51] <ajmitch> because most developers of ubuntu upload so much that they'd get flooded for every successful build on each arch
[05:51] <chillywilly> nice nick
[05:51] <pwnguin> and the web interface doesn't seem to have anything for "in build queue"
[05:52] <pwnguin> chillywilly: be warned, it's a laborious process during which you'll walk over the dead bodies of your friends in combat
[05:52] <nealmcb> ajmitch: I was surprised it would take the email from the changelog.  I don't _want_ to publish my email for yet more spammers out there, and prefer to put web urls in to take credit for things.  ppa should send mail to the person associated with the gpg key, I would think.
[05:52] <bddebian> Are we supposed subscribe UUS or anyone for removal requests or go ahead and subscribe Archive?
[05:53] <chillywilly> penGNUin is much more fun than that...
[05:53] <ajmitch> bddebian: you're a motu, why subscribe sponsors?
[05:53] <bddebian> Just don't want to get in any more trouble :-)
[05:54] <ajmitch> you'll probably get into trouble anyway
[05:54] <bddebian> Probably
[05:56] <Hobbsee> nealmcb: which is....you anyway, i'd expect.
[05:57] <bddebian> Hah, nice bug title on BTS: please update/request removal of your package
[06:02] <nealmcb> Hobbsee: Sure, the system should send email to me.  I'm just thinking that I shouldn't have to publish my email in yet another easy place for spammers to mine in order to get a notification.  And I wonder if it is time to move to URLs in pgp keys also.  I'm thinking that moving to identity systems like openid make a lot more sense than emails.
[06:04] <pwnguin> what good is a url?
[06:06] <nealmcb> I also filed bug 136593 and wonder if a different submission front-end would work better.  But I expect that changing a well established system like distro package maintenance is, uh, not an easy task :-)
[06:06] <ubotu> Launchpad bug 136593 in soyuz "no status update after dput for ppa package" [Undecided,New]  https://launchpad.net/bugs/136593
[06:07] <nealmcb> Perhaps falcon is a better model than ppa for what I'm after
[06:07] <RAOF> ajmitch: Does metacity+compositing actually work in any way?
[06:07] <ajmitch> RAOF: not that I'm aware of
[06:07] <RAOF> ajmitch: :)
[06:08] <nealmcb> and I'm sorry if this isn't the right place to talk about ppas.  I'm just getting much better answers here than I did in #launchpad....
[06:09] <pwnguin> the motu is in part to help train new packagers ;)
[06:09] <nealmcb> pwnguin: I think of urls as much easier to maintain over time than email addresses, and much more in control of the owner
[06:09] <nealmcb> and spam is a huge problem
[06:09] <pwnguin> openID?
[06:10] <pwnguin> who's the biggest openID provider?
[06:10] <nealmcb> http://openid.net/
[06:10] <nealmcb> aol?
[06:10] <pwnguin> very likely
[06:10] <nealmcb> but you can redirect thru your own domain to the current provider of your choice
[06:11] <pwnguin> i wonder...
[06:11] <nealmcb> so you can own the url but outsource the web app machinery
[06:11] <pwnguin> ah, so you're saying own a uri, but redirect to aol, or lj or whoever
[06:11] <nealmcb> yeah
[06:12] <pwnguin> the same can be done with email ;)
[06:13] <pwnguin> i partly think it's a matter of having a way to contact the maintainer
[06:13] <nealmcb> do you want to answer all the queries by hand, or let people get answers in the middle of the night via your web page?
[06:14] <pwnguin> i dont have a webpage, but i highly doubt that it would be able to answer questions i get
[06:14] <nealmcb> having an email is hardly a guarantee that you can contact the maintainer
[06:14] <pwnguin> the best case scenario someone posts on a blog and THAT sends an email
[06:14] <pwnguin> and we're back to spam
[06:14] <pwnguin> nealmcb: i havent read all of debian-policy, but id wager it's in there
[06:15] <nealmcb> I publish my email on my web page in a way that is easy for humans to read but hard for spammers to harvest
[06:15] <nealmcb> it == must provide email?
[06:15] <pwnguin> well, debian provides email
[06:16] <pwnguin> i meant more along the lines of please respond to bug reports sent to username@debian.org or we put your package on the orphans list
[06:16] <nealmcb> I mean, do you mean that debian-policy requires that people sign changelogs with actual email addresses?
[06:17] <nealmcb> pwnguin: I would certainly expect responsiveness to be required.  but what if people prefer irc to email?  or blog queries?
[06:18] <imbrandon> its all relitive, email is the standard debian/ubuntu way
[06:18] <imbrandon> want other contact options read a README
[06:18] <nealmcb> I'm not saying I'm right - just trying to figure out the current expectations and possibilities for change
[06:19] <imbrandon> the conatc is an email, the uri is started in the debian/copyright file where the software was taken
[06:19] <imbrandon> so its all a matter of where you are looking
[06:19] <imbrandon> relitive as i said
[06:20] <nealmcb> and my starting point here was ppa uploads, in which I'd expect more flexibility
[06:20] <pwnguin> relative
[06:20] <imbrandon> actualy new uploads like mentors and revu and ppa should be held to even higher standards imho
[06:21] <RAOF> No distribution unless lintian clean?
[06:21] <imbrandon> ;)
[06:21] <nealmcb> if they are targeted at a distro, I agree.  But _personal_ repositories are at the opposite end, I'd think
[06:21] <pwnguin> pbuilder complains to me that gutsy is an unknown distribution
[06:21] <pwnguin> locally
[06:22] <bddebian> Is this a bash issue or just broken?:
[06:22] <bddebian> SyntaxError: Non-ASCII character '\xac' in file ./make-doc.py on line 204
[06:22] <imbrandon> needs to be updated then probably, and is it pbuilder complaining or linda/lintian inside the pbuilder chroot
[06:23] <imbrandon> nealmcb: personal package archive to work on packages targeted for future release
[06:23] <pwnguin> lintian inside chroot
[06:23] <imbrandon> thus works in progress
[06:23] <imbrandon> pwnguin: ahh then yes update your lintian version ;)
[06:24] <pwnguin> ?
[06:24] <imbrandon> or ignore it as most do, its harmless
[06:24] <imbrandon> how are you calling pbuilder
[06:24] <pwnguin> sudo pbuilder build foo.dsc
[06:24] <imbrandon> sudo pbuilder update
[06:24] <imbrandon> ^^ run that
[06:24] <imbrandon> then rebuild
[06:25] <imbrandon> it should update your lintian amon other things
[06:25] <nealmcb> imbrandon: that is not how ppa was pitched to me....
[06:26] <pwnguin> i dont quite understand. was lintian broke until last week?
[06:26] <imbrandon> pwnguin: lintian is one of the last things to be updated
[06:26] <imbrandon> and broke isnt quite it, it just dosent know about gutsy yet, as its yet unreleased software
[06:26] <imbrandon> is more like it
[06:27] <imbrandon> its just a warning in case you typo
[06:27] <imbrandon> safely ignored
[06:27] <pwnguin> i also get warnings about unstable
[06:27] <pwnguin> in change logs
[06:27] <imbrandon> using a sid pbuilder ?
[06:28] <pwnguin> no, just gutsy
[06:28] <pwnguin> brought over a package that hasnt even hit NEW in debian yet
[06:28] <imbrandon> errm why are you using a gutsy pbuilder for a sid package ?
[06:28] <pwnguin> the changelog
[06:28] <imbrandon> correct but the changelog needs to be updated
[06:28] <pwnguin> disagree
[06:28] <imbrandon> if you are building for gutsy
[06:29] <imbrandon> sure its built against a whole new toolchain. definately
[06:29] <imbrandon> just as you wouldent install a bin package directly from sid
[06:29] <pwnguin> my entry is labelled correctly
[06:29] <pwnguin> the older entries are left alone
[06:29] <imbrandon> if it says unstable still its not
[06:31] <imbrandon> if you use dch -i and tweak it from there it should set you up correctly
[06:31] <imbrandon> when making the changelog entry
[06:31] <pwnguin> im gonna rebuild locally to double check
[06:31] <pwnguin> but im 99 percent certain i get an error for doing things the way ive always seen it done
[06:32] <imbrandon> the warning looks at the last changelog entrys dist
[06:32] <imbrandon> so if it says unstable then you dident change it when making a new entry
[06:33] <pwnguin> E: titanion_0.3~ppa2_source.changes: bad-distribution-in-changes-file gutsy
[06:34] <pwnguin> titanion (0.3~ppa2) gutsy; urgency=low
[06:34] <imbrandon> yes gutsy is because lintian dosent know about gutsy yet
[06:34] <imbrandon> thats not unstable
[06:34] <pwnguin> whoops
[06:34] <pwnguin> wrong line
[06:34] <pwnguin> i must have remembered incorrectly
[06:34] <StevenK> Sigh. gambas2 just built on amd64, but it doesn't appear in the arch list
[06:35] <pwnguin> i probably fixed that one. but i do get a changelog should mention nmu
[06:35] <imbrandon> yea we dont do mnu's in ubuntu , its a debian thing so can also be ignored
[06:35] <ajmitch> pwnguin: that's usual
[06:35] <ajmitch> StevenK: special!
[06:35] <imbrandon> nmu's*
[06:36] <imbrandon> heh
[06:36] <StevenK> ajmitch: Which train wreck?
[06:36] <imbrandon> i stoped reading *-devel at the begning of the summer
[06:36] <StevenK> I unsubscribed from -devel a while back
[06:38] <pwnguin> other than that stuff, i think i got titanion building and working.
[06:39] <imbrandon> ;)
[06:39] <ajmitch> StevenK: virtualbox maintenance
[06:40] <StevenK> Ahh
[06:40] <StevenK> Don't wanna know.
[06:41] <StevenK> I saw people arguing about it on #debian-devel last night, and I didn't want to know then either
[06:41] <ajmitch> except it seemed to have a happy ending
[06:41] <ajmitch> how un-debian
[06:41] <imbrandon> heh
[06:41] <StevenK> Indeed
[06:41] <ajmitch> it's not as amusing as the oversized icelinux threads
[06:42] <imbrandon> icelinux?
[06:42] <ajmitch> you don't want to know
[06:42] <imbrandon> heh
[06:43] <imbrandon> ugh i think the server overheated
[06:44] <imbrandon> damn it
[06:47] <imbrandon> wow looks like AMD took ATI's head out of its ass and released the specs for the R500 onwords
[06:47] <imbrandon> so FLOSS drivers acn be made
[06:47] <imbrandon> http://lwn.net/Articles/248227/
[06:48] <bddebian> Yeah, I saw that today
[06:48] <ajmitch> released, or will release?
[06:48] <imbrandon> looks like "are" releasing now at the kernel summit is more like it
[06:48] <RAOF> Future perfect tense
[06:49] <imbrandon> so half
[06:49] <ajmitch> now hopefully nvidia will open up a bit in response :)
[06:50] <jmg> imbrandon: wow
[06:51] <imbrandon> yea i was suprised too, i read on /. earlier about them "going to" but there is numerous blog posts now from people at the kernel summit saying they have a basic framework for 2d already
[06:53] <imbrandon> wonder why the r500 on and not the r200
[06:53] <imbrandon> anyhow back to figuring out wtf on this box
[06:53] <jmg> yeah
[06:55] <bddebian> Ah well, gnight folks
[07:33] <asisak> Hey everyone!
[07:33] <asisak> RAOF: congratulations
[07:33] <RAOF> asisak: Thanks
[07:33] <asisak> It is very nice to see that we have a lot of "junior" MOTUs
[07:33] <asisak> Thinking not only to myself :)
[07:56] <StevenK> d
[07:57] <RAOF> New and diffeerent?
[07:58] <StevenK> TypoTyTy
[07:58] <StevenK> Wah
[07:58] <RAOF> :)
[08:15] <Fujitsu> Hm, 1100ms to my first hop... this isn't good.
[08:23] <ubotu> Launchpad bug 104297 in kvm "KVM kernel interface is not loaded" [Undecided,Triaged]  https://launchpad.net/bugs/104297
[08:27] <Hobbsee> RAOF: i think siretart has done that.  as to why, when it's a package outside ubuntu...i'm not sure
[08:28] <ajmitch> because the bug isn't in the 3rd party package
[08:28] <RAOF> Why didn't it get set a priority, then?
[08:28] <ajmitch> but that the kernel module should load on boot when the kvm package is installed
[08:28] <ajmitch> RAOF: he didn't set one?
[08:28] <Hobbsee> oh, so the kvm is supposed to load anyway
[08:29] <RAOF> Yeah.  Or that kvm should auto-load the appropriate module, or whatever.
[08:29] <\sh> moins
[08:29] <ajmitch> hi \sh
[08:51] <dholbach> good morning
[08:55] <RAOF> Hm.  It seems merging kvm-36 from Debian should fix a couple of bugs we have.
[09:00] <StevenK> Does our kernel support kvm-36?
[09:01] <RAOF> StevenK: Apparently.
[09:02] <RAOF> StevenK: The guy who has offered $250 for a kvm merge ran it on our kernel :)
[09:02] <RAOF> He gets it for free, of course, if he gets it.
[09:04] <StevenK> What do you mean, no kickback for motu-uvf? :-)
[09:05] <RAOF> motu-uvf is welcome to accept a kickback.  I'll forward his email, if you like :)
[09:06] <StevenK> Heh, I so couldn't accept it.
[10:32] <zorg_the_false> q. is update-rc.d supported by debian too ? or is it ubuntu specific ?
[10:40] <huats> does anybody canhelp me a bit with building on ppa ?
[10:40] <\sh> zorg_the_false, update-rc.d is debian specific
[10:40] <zorg_the_false> \sh: ok thanks
[10:52] <Lutin> dholbach: got my mail about human-icon-theme ?
[10:52] <dholbach> Lutin: yes, thanks a lot
[10:53] <dholbach> Lutin: I will make the change soonish
[10:53] <Lutin> dholbach: ok
[10:53] <dholbach> Lutin: I used ./autogen.sh because the process of rolling a tarball, updating the package and so on was too complicated for the artwork people who just want to get things done
[10:54] <Lutin> dholbach: oooh ok
[10:55] <dholbach> but thanks again for letting me know
[10:55] <Lutin> lol :)
[11:05] <dholbach> Lutin: uploaded
[11:06] <Amaranth> RAOF: email?
[11:07] <Amaranth> RAOF: nevermind, launchpad to the rescue
[11:09] <Amaranth> should i poke someone after emailing motu-council or just hope they notice my application in the queue?
[11:09] <Lutin> dholbach: cool, thanks
[11:55] <huats> norsetto: Hi
[11:55] <dholbach> hey norsetto
[11:55] <dholbach> hey huats
[11:55] <norsetto> hi huats; how's going!?
[11:55] <huats> dholbach: Hey how are you ?
[11:55] <norsetto> dholbach: morning Master :-)
[11:55] <huats> dholbach: been a long time
[11:56] <huats> norsetto: I am alright,
[11:56] <huats> norsetto: what about you ?
[11:56] <norsetto> huats: outstanding :-)
[11:56] <dholbach> good good - how are you doing?
[11:56] <huats> norsetto:  I've been working a bit on the bug... And I manage with precious help from #launchpad to get my ppa running
[11:59] <huats> norsetto: so I just get notified by launchpad that a fix has been released
[12:00] <huats> norsetto: it does not contain the manpage yet
[12:00] <huats> norsetto: but beside that, is it ok for you ?
[12:00] <norsetto> huats: you mean your patch?
[12:00] <zorg_the_false> q. in the /etc/init.d script, which programm parse the ### BEGIN INIT INFO stuff ? nothing appears about that in the man update-rc.d
[12:02] <zorg_the_false> how come that when i do 'update-rc.d myservice defaults' i always get the error "System startup links for /etc/init.d/myservice already exist". according to example on the web and my reading of the man page, this should work. what i am missing ?
[12:04] <zorg_the_false> and btw, this is not specific to myservice, all /etc/init.d script i tried produces the same error
[12:06] <zorg_the_false> oh my bad. i misinterpreted the error message
[12:09] <norsetto> dholbach: thx for your comment on bug 137476. Can you check my answer?
[12:09] <ubotu> Launchpad bug 137476 in conky "conky (1.4.7-0ubuntu1) do not support rss and wireless variables" [Undecided,Incomplete]  https://launchpad.net/bugs/137476
[12:11] <norsetto> huats: I see what you mean, I didn't know about that
[12:11] <norsetto> huats: was your patch actually working?
[12:12] <huats> norsetto: what you mean by working ?
[12:13] <dholbach> norsetto: stuff like dh_gconf makes use of it
[12:13] <dholbach> norsetto: I find it useful to have it in the package
[12:13] <norsetto> huats: I mean, can the package be built and is it working correctly with your patch?
[12:13] <dholbach> norsetto: dpkg-gencontrols complains about a lot of things, X*Python* included
[12:13] <norsetto> dhobach: yes, I know they can, but in this case is not used
[12:14] <huats> norsetto: the package is building right now... with my pacth... on ppa. I'll tell you more as soon as I have the answer
[12:14] <dholbach> also it's a diff we have to carry vs debian
[12:14] <norsetto> dholbach: debian is at 1.4.5, we are at 1.4.7
[12:14] <dholbach> still we'll merge at the beginning of next cycle
[12:15] <dholbach> regardless of the upstream version that is in Debian
[12:15] <norsetto> dholbach: you mean, they merge?
[12:15] <dholbach> we merge
[12:15] <norsetto> dholbach: we downgrade!?
[12:15] <dholbach> so if there's a new debian revision regardless of the ubuntu upstream version we use, we'll merge
[12:16] <dholbach> no
[12:16] <dholbach> but we merge their changes in
[12:16] <norsetto> dholbach: what changes? they are laggin behind by one year.....
[12:16] <dholbach> merging does not depend on version numbers, but on code diff
[12:19] <norsetto> dholbach: so the philosophy is only fix what is blatantly wrong, and forget the rest I gather
[12:22] <dholbach> no, not really, but in this case I think it makes sense to have misc:Depends in it
[12:24] <huats> norsetto: the build has been successful
[12:25] <norsetto> huats: ok, can you install and is the desktop working, and the icon is there?
[12:25] <huats> that was my next move :-)
[12:26] <Lutin> dholbach: why would it be needed ?
[12:26] <norsetto> dholbach: I can have it back, np, I'm making the debdiff right now. One day perhaps I will even understand it
[12:29] <soren> norsetto: We will merge Debian's changes. They may have made changes to the packaging or fixed bugs or something. We cherry pick those changes and put them into our package. That's merging.
[12:30] <soren> norsetto: We're not going to adopt their package (thus downgrading). We'll *merge* their changes into our packages.
[12:32] <dholbach> norsetto: if there's something you don't understand, just ask
[12:32] <norsetto> soren: I'm being practical here, I see a package which is apparently forgotten in Debian, and I'm trying to clean it up. If Debian is back, we can always revert, no problem. Actually, to me it would make sense to ask the DD to do this work.
[12:33] <soren> norsetto: Yes, and your work is appreciated, and it's not going to get thrown away. Noone is suggesting that.
[12:35] <norsetto> soren: I wouldn't mind actually if this is orphaned in Debian so that at least we can clean it up properly
[12:35] <soren> norsetto: The point dholbach was trying to make (AFAICS) is that we now have a diff between Debian and Ubuntu. Each time Debian touches a package, we merge their changes into our package. We generally want to keep this diff as small as possible as this makes our job easier when we're merging at the start of the release cycle.
[12:36] <norsetto> soren: I know I'm a maniac :-D
[12:36] <norsetto> soren: yes, I understand this, this is what you will see in the bug report with the new patch
[12:36] <soren> norsetto: ...and since the ${misc:Depends} does no harm, he prefers to keep it. So do I, in fact.
[12:37] <soren> norsetto: Right. I just thought I detected some misunderstanding and wanted to help clear it up :)
[12:39] <norsetto> I like happy families :-)
[12:42] <dholbach> no no, cleaning is fine :)
[12:42] <norsetto> dholbach: thats what my wife keeps saying too!
[12:43] <soren> norsetto: *G*
[12:44] <elmargol> I have to burn a gutsy cd today. Is there an estimated time for tribe 6?
[12:49] <soren> elmargol: There's not going to be a Tribe-6 CD.
[12:49] <elmargol> why?
[12:49] <soren> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2007-September/000337.html
[12:49] <elmargol> oh
[12:49] <soren> elmargol: You can just grab one of the daily CD's.
[12:50] <elmargol> ok thank you
[12:50] <soren> elmargol: np
[12:51] <elmargol> there is a OVERSIZED file ist this a problem?
[12:59] <\sh> hmmm...
[12:59] <dholbach> norsetto: uploaded
[12:59] <\sh> can someone try to compiles scotts wine package from revu?
[01:00] <norsetto> dholbach: Danke
[01:00] <dholbach> :)
[01:01] <norsetto> huarts: any news?
[01:02] <norsetto> huats: any news?
[01:02] <huats> norsetto: sorry I did have the time : I've a serious bug @work...
[01:03] <huats> norsetto: I let you know as soon as I have installed it
[01:03] <norsetto> huats: I didn't know they worked in Toulouse :-)
[01:03] <huats> norsetto: but if you want to install it before go ahead...
[01:03] <huats> norsetto: LOL
[01:06] <dholbach> soren: can you please add a copyright for submittodebian, also add yourself to debian/copyright, AUTHORS and the script to setup.py in ubuntu-dev-tools/trunk?
[01:06] <dholbach> soren: that way we could do another upload and bring it to the masses
[01:08] <norsetto> huats: btw, you should consider sending this patch to Debian
[01:08] <soren> dholbach: Sure. Not right now, though. Gimme an hour.
[01:08] <dholbach> soren: take your time
[01:09] <dholbach> soren: just wanted to make sure we can get it out at some point
[01:09] <huats> norsetto: ok I will... but you'll have to considerto help me in that :-)
[01:09] <norsetto> huats: of course, pdp
[01:11] <huats> norsetto: pdp ???
[01:11] <norsetto> huats: pas des problemes ....
[01:12] <huats> norsetto: why I was searching english, while you speak a fluent french ?
[01:12] <huats> :-)
[01:14] <norsetto> huats: btw, you can also check if the files are installed in the right place, by using dpkg: dpkg -c .deb
[01:15] <norsetto> hey, I wrote "<package name>" and it disappeared :-(
[01:15] <norsetto> huats: dpkg -c package_name.deb
[01:16] <huats> norsetto: yep
[01:16] <huats> I will
[01:24] <\sh> strange problem
[01:24] <\sh> checking whether make sets $(MAKE)... yes
[01:24] <\sh> checking for x86_64-linux-gnu-gcc... gcc -m32
[01:24] <\sh> checking for C compiler default output file name...
[01:26] <\sh> na
[01:26] <\sh> scott forgot the lib32gcc1
[01:26] <\sh> ha
[01:30] <\sh> hmm
[01:45] <norsetto> Anyone want to give a look at: http://revu.tauware.de/details.py?upid=206 ?
[02:28] <deadwill> mornin' all
[02:28] <deadwill> o/
[02:45] <ScottK> superm1: The good news is that the xserver-xorg-video-openchrome backport you wanted for Feisty got accepted.  The bad news is that it FTBFS on 3 arch with the same error.  I'd appreciate it if you could have a look at it and see what can be done towards fixing it. https://launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/0.2.6+svn357-0ubuntu1~feisty1
[02:46] <ScottK> Same deal in Gutsy BTW, so it's not Feisty specific.
[02:53] <\sh> hmm..
[03:03] <nixternal> err, wrong channel :)
[03:18] <nealmcb> ajmitch: Thanks for the gdebi suggestion.  Built fine on gutsy and feisty, but for edgy: "Missing Dependencies:    debhelper (>= 5.0.38)"
[03:43] <\sh> any objections to update the drupal package to 5.2 (just reading -motu ml)
[03:43] <Fujitsu> \sh: Is there any reason to do so?
[03:43] <\sh> Fujitsu, serious security bugs in 5.1
[03:44] <Fujitsu> (other than a user saying it's a Good Thing?)
[03:44] <\sh> see drupal.org
[03:44] <Fujitsu> Gr, why don't they just fix them?
[03:46] <\sh> Fujitsu, what I could do is a quick diff from 5.1 to 5.2 and apply it to our package ,-)
[03:46] <\sh> which could give us more trouble regarding database upgrades
[03:48] <\sh> ah he talks about feisty I guess
[03:55] <geser> !info drupal5 gutsy
[03:55] <ubotu> drupal5: a fully-featured content management framework. In component universe, is extra. Version 5.2-2ubuntu1 (gutsy), package size 747 kB, installed size 3332 kB
[03:56] <geser> \sh: drupal5 is already at 5.2 in gutsy
[04:06] <superm1> ScottK, I didn't request it myself did I? I'll be glad to look it over though.
[04:07] <\sh> geser, yepp..I think he talks about feisty
[04:07] <Whoopie> ScottK: the fix for bug 137712 is quite trivial. Who could update xchat?
[04:07] <ubotu> Launchpad bug 137712 in xchat "[PATCH]  XCHATSHAREDIR variable not correct" [Undecided,New]  https://launchpad.net/bugs/137712
[04:11] <bddebian> Heya gang
[04:11] <geser> Hi bddebian
[04:11] <bddebian> Heya geser
[04:13] <geser> Whoopie: have you asked the last uploader if he plans to fix it in the next upload?
[04:14] <geser> Whoopie: I see he is a bug contact for xchat so he probably knows about your patch
[04:18] <Whoopie> geser: ah, ok. Then, I'll wait for some days. Thanks!
[04:21] <\sh> geser, any clue who is doing security updates when pitti is not available?
[04:21] <soren> \sh: keescook
[04:21] <geser> \sh: keescook
[04:21] <soren> geser: snap
[04:21] <\sh> soren, geser thx
[04:21] <soren> :p
[04:38] <deadwill> hey bddebian
[04:42] <bddebian> Hi deadwill
[04:44] <\sh> should I file security bug reports as private ?
[04:46] <geser> only if they are new. imho there is no need to mark them private if the issue is already public
[05:01] <superm1> ScottK, on gutsy i dropped the arch any, and replaced it with i386 amd64 lpia.  The hardware isn't even available on other architectures, so there isn't much of a point to building for them.
[05:04] <alex-weej> anyone know what i need to do to get a package rebuilt for the archives? libapache2-mod-cband needs rebuilding in feisty (it hasn't worked since April)
[05:04] <alex-weej> the so is dated november 2006
[05:05] <bddebian> alex-weej: Does it build?
[05:05] <alex-weej> yes
[05:05] <bddebian> Without modification?
[05:06] <alex-weej> yes
[05:06] <alex-weej> https://bugs.launchpad.net/ubuntu/+source/mod-cband/+bug/96063
[05:06] <ubotu> Launchpad bug 96063 in mod-cband "libapache2-mod-cband needs rebuilding" [Undecided,Confirmed] 
[05:06] <bddebian> Give me a sec and I'll build it.  If it works I'll ask for a give-back
[05:06] <alex-weej> what's a give-back?
[05:08] <bddebian> Hobbsee: Mithrandar gave back player for me :-)
[05:08] <bddebian> alex-weej: We have the binaries, why does it need a rebuild?  Newer apache2 libs or something?
[05:10] <alex-weej> bddebian: i guess it's an ABI break
[05:10] <alex-weej> Edgy bundled Apache 2.0?
[05:12] <bddebian> Are we supposed to update the maintainer field for build1 revisions?
[05:13] <Hobbsee> bddebian: right, then it does, cool
[05:14] <bddebian> What is the exact format for the changelog entry to close an LP bug?
[05:14] <superm1> (LP: #XXXXX)
[05:14] <bddebian> superm1: Thx
[05:15] <alex-weej> bddebian: nice one
[05:15] <bddebian> alex-weej: ??
[05:15] <alex-weej> bddebian: "thanks" -- i assume you're closing this bug
[05:15] <bddebian> alex-weej: Ah, :-)
[05:19] <bddebian> alex-weej: You know what happens when you assume don't you? ;-)
[05:19] <alex-weej> ;p
[05:20] <\sh> I wonder how we make drupal from dapper security enabled ,->
[05:20] <\sh> backporting patches from 4.7 to 4.5 is a pain
[05:24] <keescook> \sh: (just waking up now), hi!
[05:25] <keescook> \sh: were CVEs assigned for these problems?
[05:26] <\sh> keescook, not that I can see..but the drupal own security announcements
[05:26] <\sh> keescook, I attached them in the changelog and in the bug report
[05:28] <keescook> \sh: hm, these will be tricky to find.  Here's the current list...  http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=drupal
[05:29] <\sh> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4363 and http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4063
[05:30] <\sh> I can add them to the changelog and resend a new debdiff if you want
[05:30] <keescook> \sh: yeah, that'd be great; thanks!
[05:30] <\sh> keescook, give me a sec :)
[05:33] <\sh> keescook, I'm going to prepare some drupal sec updates for dapper and edgy too...I just need to cherry pick those from drupals SVN
[05:34] <keescook> \sh: okay, excellent
[05:35] <\sh> gnarf
[05:37] <\sh> kees uploaded..hopefully it isn't doubled, just because we had a small network outage *grmpf*
[05:37] <keescook> \sh: okay, I'll get it building and uploaded.
[05:37] <\sh> keescook, thx a lot :)
[05:41] <\sh> ok...going home and playing with drupal svn ... cu later
[06:06] <\sh> keescook, see my comment to the drupal bug...dapper and edgy are clean
[06:08] <keescook> \sh: okay, good
[06:10] <keescook> \sh_away: hm, debdiff seems to include some .orig files.
[06:14] <ScottK> superm1: Sounds like a reasonable solution.  Thanks.
[06:15] <superm1> np, i'm glad someone requested the backport for it, its quite useful to people with those via chips
[06:17] <ogra> superm1, ++
[06:18] <ogra> will make a lot ltsp users happy to have openchrome ... even in feisty
[06:18] <superm1> reminds me, still need to file the MIR for it.  I'll try to put some time aside tomorrow for that
[06:18] <StevenK> ScottK: Are you happy with my requestsync changes?
[06:18] <ScottK> StevenK: Yes
[06:22] <bddebian> Great sdcc doesn't build with just lyx.. Grr
[06:30] <alex-weej_> bddebian: hey
[06:30] <alex-weej_> crap i left xchat on at work
[06:30] <bddebian> Yo?
[06:30] <alex-weej_> bddebian: can you roll an update for cband for feisty please?
[06:30] <StevenK> alex-weej_: ssh in and kill it? :-)
[06:31] <alex-weej_> good plan
[06:31] <alex-weej_> rar
[06:32] <bddebian> I don't normally do SRUs but I suppose I could try
[06:33] <alex-weej_> what's an SRU?
[06:33] <bddebian> Stable Release Update
[06:33] <alex-weej_> oh right
[06:34] <alex-weej_> well somebody should, feisty has another year of support right?:
[06:34] <ScottK> To the extent Universe is supported, yes.
[06:34] <bddebian> Yes but I'm still not real clear on what criterea is used
[06:35] <ScottK> What bug is it that might be fixed?
[06:35] <bddebian> ScottK: mod-cband just neeeds a rebuild against the apache2.2 libs
[06:35] <ScottK> Ah.
[06:35] <ScottK> Otherwise it "doesn't work", right?
[06:35] <ScottK> I think that would qualify.
[06:36] <bddebian> Yep
[06:36] <bddebian> Do I just prepare a package and throw it on feisty-proposed or something?
[06:38] <ScottK> Yes and then once it's accepted you send a mail to the motu list asking people to test it.
[06:38] <ScottK> No need to use the ~proposed version numbers anymore.  Just use the version number you actually want it to have.
[06:38] <bddebian> But feisty-proposed in the changelog?
[06:39] <geser> yes
[06:39] <bddebian> Do I need to file a bug or anything?
[06:39] <bddebian> Better yet is there a wiki page I should be reading? :-)
[06:39] <geser> the package gets copied from -proposed to -updates if it got tested and accepted
[06:40] <geser> a bug would be useful to collect the test result
[06:40] <geser> as a record for the archive admins
[06:41] <alex-weej_> to be honest, the original debian import got less testing than that
[06:41] <alex-weej_> :P
[06:41] <bddebian> See, here is my issue.  From the SRU wiki page:
[06:41] <bddebian>     *
[06:41] <bddebian>       Bugs which may, under realistic circumstances, directly cause a security vulnerability
[06:41] <bddebian>     *
[06:41] <bddebian>       Bugs which represent severe regressions from the previous release of Ubuntu
[06:41] <bddebian>     *
[06:41] <bddebian>       Bugs which may, under realistic circumstances, directly cause a loss of user data
[06:41] <ScottK> wiki.ubuntu.com/MOTU/SRU
[06:41] <bddebian> I don't see it meeting any of those three
[06:42] <ScottK> Well it worked before Apache got updated, right?
[06:42] <keescook> is this rebuild needed due to the apache security update?
[06:43] <bddebian> keescook: No 2.0 -> 2.2 transition
[06:43] <keescook> aah
[06:53] <ScottK> bddebian: Did the package work at any point?
[06:53] <bddebian> ScottK: In Edgy I believe
[06:54] <ScottK> Then I think it would represent a severe regression (for that package) from a previous release and qualify.
[06:54] <ScottK> I'd say go for it.
[06:54] <proppy> norsetto: ping
[06:57] <RainCT> if a binary package has not depends, can I just remove the Depends line?
[07:00] <geser> RainCT: what did you package that it has no depends? (just curious)
[07:01] <RainCT> geser: the -data
[07:01] <geser> ah, sure removing the Depends line should be no problem (check with linda/lintian)
[07:02] <RainCT> ok, thanks
[07:04] <proppy> about bug #137573
[07:04] <ubotu> Launchpad bug 137573 in poker-network "poker2d crash (SIGSEGV) at startup" [Undecided,Incomplete]  https://launchpad.net/bugs/137573
[07:05] <proppy> I've trouble getting a clean stack trace and being able to step into gtk sources
[07:06] <proppy> I've installed the following packages apt-get install python-gobject-dbg libgtk2.0-0-dbg
[07:07] <proppy> And the gdb stacktrace is still the same
[07:07] <proppy> that before I've installed the dbg package
[07:08] <proppy> It just get rid of (no debugging symbols found) warnings
[07:11] <bddebian> So I just dput my package right to Ubuntu as normal?
[07:11] <Hobbsee> bddebian: as opposed to what?
[07:11] <geser> bddebian: for the SRU? yes
[07:38] <bddebian> Go geser, go geser :)
[07:43] <asisak> Hey MOTUs!
[07:44] <geser> Hi asisak
[07:44] <asisak> Hey geser
[07:45] <geser> asisak: Whoopie looks for someone to upload the patch from bug #137712
[07:45] <ubotu> Launchpad bug 137712 in xchat "[PATCH]  XCHATSHAREDIR variable not correct" [Undecided,New]  https://launchpad.net/bugs/137712
[07:45] <deadwill> hey asisak
[07:46] <bddebian> Heya asisak
[07:52] <asisak> hey bddebian, deadwill
[07:52] <deadwill> o/
[07:54] <proppy> can I generate an apport report from command line ?
[07:55] <proppy> Given a segfaulting program in a gutsy chroot, how can I generate an apport crash ?
[07:58] <asisak> Whoopie: you want me to create a debdiff from your patch?
[07:58] <asisak> Whoopie: (or not me, just someone)
[07:59] <geser> proppy: have you tried running apport-cli inside the chroot?
[08:01] <proppy> geser: root@nekun:/# apport-cli
[08:01] <proppy> Could not import module, is a package upgrade in progress? Error: No module named xdg.DesktopEntry
[08:01] <proppy> I guess i should apt-get install python-xdg
[08:03] <proppy> geser: but what should I use to generate the .crash file ?>
[08:03] <proppy> geser: from a segfaulting program
[08:03] <geser> hmm
[08:04] <geser> doesn't the kernel do it and you should have one in /var/crash outside the chroot?
[08:05] <proppy> not inside and not outside
[08:06] <proppy> Is it able to generate .crash for python program too ?
[08:07] <geser> I've seen apport reports with python tracebacks so it works for them too
[08:08] <proppy> I'm segfault in a gtk native librairie but imported from python
[08:08] <proppy> I'will ask on lp if someone is able to generate .crash file for it
[08:10] <proppy> norsetto: #137573 updated
[08:31] <pkern> Is there documentation about the buildds and how to request give-backs etc.?
[08:33] <bddebian> pkern: Just poke a buildd admin in -devel
[08:54] <Whoopie> asisak: that would be great!
[08:54] <proppy> norsetto: ScottK: new patch for #137573
[08:54] <proppy> #137573
[08:55] <proppy> bug #137573
[08:55] <ubotu> Launchpad bug 137573 in poker-network "poker2d crash (SIGSEGV) at startup" [Undecided,Incomplete]  https://launchpad.net/bugs/137573
[08:55] <asisak> Whoopie: what do you think? Should I use both patches or only the one that patches configure?
[08:56] <Whoopie> asisak: only the debian/rules patch
[08:56] <ScottK> proppy: I'm having hardware trouble on the box that I've got set up to test, so it'll be a little while (probably not today) before I could get to it.
[08:57] <ScottK> proppy: I'll take a look at it, but I can't test/upload it now.
[08:57] <proppy> Ok np
[08:57] <proppy> I'll be busy forwarding it upstream btw
[08:59] <ScottK> Great.  I'd prepare another debdiff, attach it, and make sure UUS is subscribed.
[09:00] <sistpoty> hi folks
[09:00] <bddebian> Heya sistpoty
[09:01] <sistpoty> hi bddebian
[09:01] <bddebian> alex-weej: mod-cband has been accepted in feisty-proposed so if you could test when it hits the archive, I would appreciate it!
[09:03] <norsetto> hi proppy, sorry, was having dinner
[09:03] <proppy> np norsetto :)
[09:03] <alex-weej> bddebian: tbh if it's just a rebuild i've already been testing it all day at work
[09:03] <proppy> norsetto: I attached a new patch to bug #137573
[09:03] <alex-weej> we use dapper on our servers you see, but my workstation is feisty
[09:03] <ubotu> Launchpad bug 137573 in poker-network "poker2d crash (SIGSEGV) at startup" [Undecided,Incomplete]  https://launchpad.net/bugs/137573
[09:04] <bddebian> alex-weej: OK, then could you please comment on Bug #137795 ?
[09:04] <ubotu> Launchpad bug 137795 in mod-cband "[SRU Universe]  mod-cband 0.9.7.4-2build1" [Undecided,In progress]  https://launchpad.net/bugs/137795
[09:05] <geser> Hi sistpoty
[09:05] <sistpoty> hi geser
[09:06] <alex-weej> bddebian: actually... now that I think about it, i'm not 100% convinced our deployment was working, but at least it let apache load. hm. :S
[09:06] <asisak> hey sistpoty
[09:06] <asisak> Hmm.. I see norsetto around :)
[09:06] <norsetto> proppy: ok, just had a cursory look, I still have 9 security patches to prepare, so it maybe a while before I can look into that, but thanks :-)
[09:06] <alex-weej> bddebian: i'll try figure it out tomorrow
[09:06] <sistpoty> hi asisak
[09:07] <DktrKranz> could a sponsor look at a potential SRU in bug 73722 ? a rebuild is required to use the new version of libpt. thanks
[09:07] <ubotu> Launchpad bug 73722 in openmcu "[SRU]  Linked against libpt-1.9, which is not in dapper" [Undecided,Confirmed]  https://launchpad.net/bugs/73722
[09:07] <proppy> norsetto: np, let me know if I can help :)
[09:08] <asisak> integrally or differentially?
[09:10] <norsetto> asisak: with a null pointer ;-)
[09:11] <proppy> ** Error: error in error handling **
[09:11] <bddebian> alex-weej: NP, thanks
[09:11] <alex-weej> Error: error in retrieving line number on which real error occurred
[09:12] <bddebian> heh
[09:18] <deadwill> bye all
[09:18] <deadwill> a nice weekend
[09:18] <deadwill> o/
[09:18] <asisak> bye deadwill
[09:19] <sistpoty> cya deadwill
[09:19] <bddebian> Later deadwill
[09:29] <norsetto> Got an interesting one, how do you patch the source when the source is a .tar.gz?
[09:30] <asisak> you create a debian .diff anyway
[09:31] <asisak> So you can include actual changes in that. However, using a patch-o-matic is suggested IIRC
[09:31] <norsetto> asisak: what I mean is an upstream source, not a source package
[09:31] <ScottK> Why are you trying to do that?
[09:32] <asisak> I guess he wants to fix bugs upstream.
[09:32] <norsetto> well, thats what I find instead of the source tree
[09:32] <ScottK> norsetto: Are you the upstream or is this just for your own use?
[09:33] <norsetto> neither: I have foo.dsc; foo.diff.gz; foo.orig.tar.gz and after a dpkg-source -x foo.dsc in the directory foo, I have foo.tar.gz and debian ......
[09:33] <sistpoty> norsetto: you mean a .tar.gz inside a debian source package?
[09:33] <norsetto> sistpoty: yes :)
[09:34] <sistpoty> norsetto: hm... there is one tool which is not unlike dpatch-edit-patch for this. However I don't recall it right now. what are the build-depends of the source-package?
[09:34] <sistpoty> (as this tool must be in one of the build-depends
[09:34] <sistpoty> +)
[09:36] <norsetto> standard stuff, the package is using cdbs and there are some patches already in debian/patches
[09:36] <asisak> I guess it is dbs
[09:36] <sistpoty> norsetto: it is using cdbs? iirc I just found it and it should be dbs-edit-patch (or s.th. from the dbs package)
[09:36] <norsetto> perhaps a flag of cdbs-edit-patch then
[09:36] <norsetto> ah, ok, let me check that
[09:37] <asisak> norsetto: which package is that?
[09:37] <norsetto> sylpheed
[09:42] <sistpoty> norsetto: actually cdbs-edit-patch should do the trick then. Unfortunately it doesn't for me :( (I preemptively blame cdbs for this *g*)
[09:42] <norsetto> well, dbs seems to be doing it :-)
[09:42] <norsetto> even though fails to apply one patch .....
[09:44] <sistpoty> hm... cdbs-edit-patch did apply all, but bailed out later (and dbs bailed out for me as well)
[09:46] <rockets> What's the application that tells me to go install stuff when I type in a command for something I don't have installed
[09:48] <norsetto> sistpoty: btw, I'm working on the dapper version
[09:48] <sistpoty> norsetto: ah, /me looked at gutsy
[09:49] <sistpoty> rockets: I guess it's somewhere in the package command-not-found
[09:49] <rockets> sistpoty, hehe
[09:49] <sistpoty> (was no joke actually, as there is such a package ;)
[09:50] <rockets> sistpoty, yeah i just looked it up, thanks
[09:50] <rockets> ive always wondered how that worked
[09:50] <sistpoty> np
[09:50] <rockets> btw the description of command-not-found-data still says
[09:50] <rockets> "Data for edgy"
[09:57] <norsetto> this sucks the big one
[09:58] <norsetto> keescook: hey kees, we stumbled against a little problem here
[09:59] <davromaniak> is Sebastien Bacher here ???
[10:02] <keescook> norsetto: what's up?
[10:03] <norsetto> keescook: I'm trying to patch sylpheed too (the others are corrected), but this one is something a bit obtuse
[10:03] <keescook> ?
[10:04] <norsetto> keescook: the debian source package contains a .tar.gz and nether cdbs not dbs seems to be able to create a patch
[10:04] <bddebian> Ack I hate those
[10:04] <norsetto> bddebian: how do I understand you .....
[10:04] <keescook> norsetto: ew
[10:05] <sistpoty> norsetto: cdbs-edit-patch 06mynewsecurityfix doesn't work?
[10:05] <norsetto> sistpoty: no :-(
[10:05] <keescook> norsetto: if it really isn't in orig.tar.gz form, then just patch it inline.  no other option, really.
[10:05] <sistpoty> ;(
[10:05] <norsetto> keescook: but they have already cdbs patches in there, there must be a way to have this working .....
[10:06] <pwnguin> what's the best way to represent ubuntu specific changes to a package?
[10:06] <keescook> norsetto: hm, I don't think you're right -- I see orig.tar.gz for dapper, edgy, feisty of "sylpheed"
[10:07] <norsetto> keescook: thats right
[10:07] <norsetto> keescook: try to dpkg-source one of them .dsc
[10:07] <pwnguin> for example, debian has a package called gdc, while ubuntu has gdc-4.1. do i just change the control file, or do i keep a patch for it?
[10:07] <sistpoty> keescook: it uses the tarball rule
[10:08] <keescook> I must be misunderstanding something
[10:08] <norsetto> sistpoty: it does, but fails with this: cd: 73: can't cd to /tmp/cdbs-new-patch.J18021/sylpheed-2.2.4.new/build-tree/sylpheed-$(VERSION)
[10:08] <sistpoty> norsetto: yes, that's exactly what it does for me from the beginning on :(
[10:09] <geser> pwnguin: I can't find gdc in Debian unstable only gdc-4.1
[10:09] <norsetto> keescook: in the sylpheed .orig.tar.gz there is no tree, there is another tar.gz
[10:09] <sistpoty> norsetto: maybe you could fiddle (or temporarily remove) DEB_TAR_SRCDIR from rules?
[10:10] <norsetto> keescook: so when you dpkg-source the *.dsc you get a .tar.gz instead of the tree source (rules is made to work with this through tarball.mk1)
[10:10] <keescook> norsetto: oooh, evil.  yeah, you'll likely have to unpack it and play with it by hand
[10:11] <keescook> norsetto: http://people.ubuntu.com/~kees/scripts/u-patch
[10:11] <keescook> I use that to "unpack and patch" packages
[10:11] <norsetto> keescook: ok, let me check that
[10:17] <sistpoty> norsetto: found it, run /bin/sh debian/get-version.sh and replace $(VERSION) from debian/rules, DEB_TAR_SRCDIR line with it, that works for me
[10:17] <norsetto> sistpoty: yes, but why idt doesn't work with it!? its 2.2.4
[10:18] <sistpoty> norsetto: not too sure, maybe some evil script looks for DEB_TAR_SRCDIR with grep instead of including the makefile?
[10:19] <norsetto> hmmm, this obviously was working at least in dapper/edgy/feisty though
[10:20] <norsetto> keescook: would that be acceptable for a security fix?
[10:20] <sistpoty> norsetto: cdbs-edit-patch, line 66 is the evildoer
[10:23] <norsetto> sistpoty: you know I wonder, if it will work with a simple assigment
[10:25] <sistpoty> norsetto: you mean the sylpheed package?
[10:25] <norsetto> sistpoty: do you think this changed for gutsy?
[10:26] <sistpoty> norsetto: no idea actually
[10:26] <sistpoty> (cdbs-edit-patch just explains why it doesn't work)
[10:26] <norsetto> sistpoty: you been a great help :-)
[10:26] <sistpoty> you're welcome ;)
[10:32] <asisak> Whoopie: uploaded xchat
[10:32] <asisak> Whoopie: thanks for your patch
[10:33] <zxz> Hi, I worked to create locales packages for sunbird for universe and I'll be ready soon to upload. I followed the instructions to be added in REVU but it's been several days and I still don't have access, can somebody help me around that?
[10:34] <geser> !info sunbird gutsy
[10:34] <ubotu> sunbird: Sunbird stand-alone Calendar. In component universe, is optional. Version 0.5-0ubuntu4 (gutsy), package size 7506 kB, installed size 22304 kB
[10:35] <zxz> on launchpad, I'm Savann Carignan
[10:35] <sistpoty> norsetto: bug #137827 reported :)
[10:35] <ubotu> Launchpad bug 137827 in cdbs "cdbs-edit-patch fails with tarball.mk and a nonstatic DEB_TAR_SRCDIR" [Undecided,New]  https://launchpad.net/bugs/137827
[10:36] <norsetto> bugger it :-)
[10:36] <sistpoty> (needed to write this over a few times, since I only flamed cdbs the first few tries *g*)
[10:36] <norsetto> sistpoty: :-D
[10:37] <norsetto> sistpoty: I think I will confirm the bug :-)
[10:37] <bddebian> mertiki: Is this just a patch to the existing package?
[10:38] <sistpoty> hehe
[10:38] <sistpoty> mertiki: I'll look over it in a few minutes, but first I'm out for a cigarette
[10:38] <mertiki> no, it's the locales, to gives langage support to sunbird
[10:38] <bddebian> mmm, cigarette
[10:38] <mertiki> no problem
[10:39] <pwnguin> geser: maybe it's a virtual package?
[10:39] <pwnguin> geser: gdc-4.1 provides gdc
[10:40] <bddebian> Damn I hate little packages with HUGE build-depends
[10:40] <pwnguin> geser: it seems i dont need to change it after all
[10:47] <sistpoty> mertiki: what was the package name that you uploaded to revu?
[10:48] <bddebian> heh
[10:48] <mertiki> I didn't because I can't have access to revu, it's the first time that I try this and my packages are quite simple
[10:49] <ScottK> tonyy: Maybe a script that compares something between Ubuntu and Kubuntu so it needs to depend on kubuntu-desktop too.
[10:49] <mertiki> I followed the instructions to gain access for upload to revu, but I'm not able to use it yet
[10:49] <ScottK> mertiki: When did you upload your GPG key to launchpad and join the 'contributors' team?
[10:49] <sistpoty> mertiki: oh. you'll only get an account for revu, once you actually upload a package (since your account can then only be used to comment to packages you've uploaded to revu)
[10:49] <tonyy> ScottK: haha
[10:50] <mertiki> the packages that I'll upload are sunbird-locale-fr_0.5-0ubuntu1_all, etc. for each language
[10:50] <bddebian> ScottK, tonyy: You two are evil :-)
[10:50] <mertiki> ah.... goutsh
[10:50] <mertiki> sorry all :P
[10:51] <sistpoty> mertiki: just go ahead and upload these. if they don't show up (which they should, because your key is in revu's keyring), please ask again ;)
[10:51] <ScottK> mertiki: You do know we are past new package freeze for Gutsy, right?
[10:51] <mertiki> my GPG key is uploaded since several months and I joined the team since 1 or 2 weaks
[10:51] <sistpoty> mertiki: yes, it's already in revu's keyring, I just checked
[10:52] <mertiki> ScottK : Gutsy won't receive new packages?
[10:52] <bddebian> Nope
[10:52] <ScottK> Not without an exception approved.
[10:52] <mertiki> If I upload today, it will only be in the next release right?
[10:53] <sistpoty> ScottK: but we're not yet past translation freeze? (so this might be worth an exception, though I now absulotely nothing about how translations are or should be handled)
[10:53] <ScottK> The biggest issue is that the archive admins who have to manually review all new packages have other stuff to do late in the cycle so we don't want to burden them unless it's important.
[10:53] <ScottK> Not saying they won't get in, just that it needs to be looked at.
[10:54] <mertiki> It's not critically pressing, I'm new to this so I'm learning too :)
[10:54] <sistpoty> I guess we could need someone with knowledge about translations in the motu team *g*
[10:54] <ScottK> That would be good.
[10:54] <bddebian> pfft, what else do you need but English? ;-P
[10:54] <ScottK> Won't be me.  All I could do are English to English translations.
[10:55] <asisak> Do you need one who can translate or one who can make applications translation-aware?
[10:55] <mertiki> haha, I don't know if it looks like I'm french, but I am. Each english phrase is hard to write
[10:56] <ScottK> One who at least understands how the process works.
[10:56] <asisak> The general process or the one with Rosetta?
[10:56] <sistpoty> asisak: rather someone who knows how rosetta integrates with all that (which is a superset of both, I guess)
[10:56] <ScottK> mertiki: All kidding aside, we do appreciate the extra effort it takes to communicate in a non-native language.
[10:56] <ScottK> asisak: Yes.
[10:56] <mertiki> ScottK :  thanks your welcome :)
[10:58] <asisak> ScottK: bug 137712, can we have a feisty backport now? :)
[10:58] <ubotu> Launchpad bug 137712 in xchat "[PATCH]  XCHATSHAREDIR variable not correct" [Undecided,Fix released]  https://launchpad.net/bugs/137712
[10:58] <mertiki> I think that for Mozilla-products like Sunbird, Rosetta isn't the solution because xpi extensions already exists. the language support for thunderbird is xpi files installed through apt
[10:58] <sistpoty> bddebian: Kha'Plah!
[10:58] <bddebian> hehe
[10:59] <ScottK> asisak: File a feisty-backports bug and test it and yes.
[10:59] <sistpoty> ok, I'll have to go to bed now... gn8 everyone
[10:59] <bddebian> Gnight sistpoty
[11:05] <bddebian> w000
[11:05] <imbrandon> t
[11:07] <bddebian> Nice package name: quiteinsanegimpplugin
[11:08] <mertiki> @++ everyone and thanks for the answers
[11:11] <bddebian> We are supposed to be removing the packages from Lucas's list if we "fix" them?
[11:12] <bddebian> geser: ^ ?
[11:14] <bddebian> w00t, rekall finally built
[11:16] <bddebian> la la la
[11:17] <geser> I've asked lucas if I should remove fixed packages or comment them and he left it to me how to handle it
[11:17] <bddebian> Aye I saw your comment, hence why I am confirming with you? :)
[11:17] <geser> I tried commenting them but I found that is easier to remove fixed package as this way it easier to see which still need fixing
[11:19] <ajmitch> good morning
[11:20] <geser> Hi ajmitch
[11:20] <geser> bddebian: is removing fixed packages from the list ok for you or do you prefer commenting?
[11:23] <bddebian> Heya ajmitch
[11:23] <bddebian> geser: No I think it's good.  I was going to do that before but since it wasn't my page...
[11:28] <asisak> ScottK: how many testing do we need?
[11:28] <asisak> Should I announce the package and let some people test it?
[11:29] <ScottK> asisak: For backports the standard is pretty low.  As long as it builds, installs, and runs, it's good.
[11:30] <asisak> ScottK: I see.
[11:30] <asisak> I guess I should only change the package to have a proper version then
[11:30] <asisak> Or is it automatic?
[11:31] <ScottK> All you have to do is take your Gutsy source package and build it for Feisty and test it.
[11:31] <ScottK> Say in the bug you've done that.
[11:31] <ScottK> The creation of the backported package is done via an archive admin script.
[11:33] <bddebian> geser: OK, I've removed all mine
[11:33] <geser> yeah, the list gets shorter
[11:34] <asisak> ScottK: what should I do now?
[11:36] <ScottK> File the bug in Feisty backports
[11:36] <asisak> there is a bug in feisty backports
[11:38] <ScottK> asisak: Please say in the bug that you tested it on Feisty and it works and then edit the title to be a backports request for the new version.
[11:38] <ScottK> Set it to confirmed when you are done.  In Progress in backports means it's been acked to the archive.
[11:39] <ScottK> Gotta run.  I'll look at it later if jdong doesn't get it first.
[11:39] <jdong> asisak: thanks,  I was looking athtat bug report earlier today too
[11:39] <asisak> thanks ScottK
[11:39] <jdong> asisak: it looks good for approval; let me eat dinner then push that through
[11:40] <asisak> thanks jdong as well
[11:40] <asisak> Enjoy your dinner, jdong
[11:43] <asisak> Good night, everyone.
[11:47] <norsetto> I have ever say again that I want to do 9 security patches in a row, please, just please, shoot me in the heart
[11:48] <geser> that bad?
[11:48] <bddebian> Later gang
[11:48] <norsetto> geser: worse :-)
[11:48] <norsetto> bddebian: nigthie
[11:50] <norsetto> bets are open on the one that I screwed !
[11:50] <keescook> they all look fine to me.  :)
[11:50] <norsetto> wait, bets are open on the one I didn't screw :-)
[11:50] <geser> norsetto: I hope you don't get nightmares from the patches
[11:51] <norsetto> keescook: sorry it took so long, bloody cdbs-edit-patch bug and all, if it wasn for sistpoty (god bless him)
[11:51] <keescook> and now i get to go do 8 updates (krb5 & librpcsecgss again -- upstream got their patch wrong)
[11:51] <norsetto> geser: heck!
[11:51] <keescook> norsetto: no problemo!  thank you for doing all the heavy lifting!  I'll get them all published shortly here.
[11:52] <norsetto> keescook: what is amazing is the amount of time it takes to add 6 bloody bytes .....
[11:52] <keescook> yeah, it's crazy.
[11:53] <keescook> ajmitch: want to do claws-mail for gutsy?  I think norsetto is tapped.  :)
[11:53] <ajmitch> for CVE-2007-4048
[11:54] <norsetto> keescook: is it available already from Debian?
[11:54] <ajmitch> keescook: if I do, it'll be sometime this weekend :)
[11:54] <keescook> norsetto: well, 3.0.0 was packaged for Debian, so you'd have to file a UVF exception to merge it to gutsy.
[11:55] <keescook> or you can just down (yet another) tiny patch.  :)
[11:55] <norsetto> keescook: you know, I just patched claws-mail 3 days ago .....
[11:56] <keescook> heh
[11:56] <norsetto> the story of my life, I'm always a tad bit too late :-)
[12:02] <norsetto> keescook: I don't think the patch for gutsy will be a security patch, right, just a normal patch would do?
[12:04] <keescook> norsetto: correct; regular versioning.  but please still mention the CVE in the changelog.
[12:04] <norsetto> keescook: sure
[12:10] <ScottK> ajmitch: Anything with php in the name is by definition crack, so I don't think it matters much which version.
[12:10] <ajmitch> thanks for the useful input
[12:11] <ScottK> Hey, I'm easy.
[12:11] <ScottK> Back later.
[12:29] <norsetto> keescook: done, I guess I don't need to subscribe u-u-s since you will sponsor that?
[12:29] <keescook> norsetto: sure thing.
[12:30] <norsetto> keescook: ok, I screwed it up ..... I just nominated it for gutsy :-)
[12:30] <keescook> norsetto: s'okay.  :)
[12:32] <keescook> norsetto: does sylpheed-claws in gutsy need an update too?  I see that sylpheed is already fixed, and claws-mail replaced sylpheed-claws-gtks (which you just fixed)
[12:33] <keescook> I'll build it as soon as my builds of krb5 and librpc (for a 3 releases) finished.  I think I need a 6-CPU machine.  ;)
[12:33] <norsetto> I thought sylpheed-claws was replaced by claws-mail, let me check
[12:33] <keescook> norsetto: oh, perhaps they were both replaced by claws-mail ?
[12:33] <keescook> if that's the case, we should file a "remove" request for sylpheed-claws
[12:34] <keescook> (which is still in the archive for gutsy)
[12:34] <geser> isn't sylpheed-claws the gtk1 version?
[12:34] <geser> and claws-mail the renamed gtk2 version?
[12:35] <ScottK> Yes
[12:35] <ScottK> IMO sylpheed-claws should just be removed.
[12:36] <ScottK> keescook: Yes please.  IIRC that's the last rdepend for gpgme.
[12:36] <ScottK> Then we can kill that too.
[12:36] <keescook> ScottK: can you file a removal bug?  I'm juggling a bunch atm
[12:36] <ScottK> keescook: Will do, but maybe not until tomorrow.
[12:37] <ScottK> Maybe tonight.
[12:37] <keescook> ScottK: no rush.  :)