[12:37] <TheMuso> Hey folks.
[12:38] <ajmitch> hey TheMuso
[12:42] <imbrandon> ello TheMuso ajmitch
[12:44] <ajmitch> hey imbrandon
[12:44] <ajmitch> what's up?
[12:45] <nixternal> alrighty, what is on the blocks for getting fixed today?
[12:50] <ajmitch> bugs?
[01:10] <K0brik> I am writing a finetuning script for Ubuntu Feisty on my system. Should I add it somewhere when I'm done
[01:13] <K0brik> it is basically some gconf commands
[01:13] <K0brik> and some kernel tweaking
[01:27] <K0brik> btw C is not 0
[01:59] <_MMA_> Can someone tell me why Bug 140620 was assigned to Ubuntu Studio? Can a user do that to try to get it further attention?
[01:59] <ubotu> Launchpad bug 140620 in linux-source-2.6.22 "[gutsy]  sound card stopped working with 2.6.22-11 for ICH7 pci id 8086:27d8" [Medium,Triaged]  https://launchpad.net/bugs/140620
[02:01] <TheMuso> _MMA_: Have you looked at the activity log?
[02:01] <_MMA_> no
[02:02] <TheMuso> That will tell you who assigned it to ubuntustudio.
[02:02] <TheMuso> c
[02:02] <TheMuso> ugh
[02:07] <_MMA_> TheMuso: k. I got it.
[02:39] <ajmitch> _MMA_: users commonly assign bugs when they shouldn't
[02:42] <_MMA_> ajmitch: I did track it down. bdmurry at BenC's request assigned it to us as the user had this issue using the new -rt kernel we've been working on. Thing is I cant find if things work fine for him on -generic. In any case I'll chat with Ben about it tomorrow.
[02:42] <ajmitch> fun :)
[02:42] <_MMA_> :D
[02:51] <bddebian> Heya gang
[02:51] <robyarrrr> arr matey!
[02:52] <bddebian> :-)
[02:54] <bddebian> Hobbsee: !!!!!!!!!!!!
[02:54] <zul> hye Hobbsee
[02:57] <Hobbsee> hey bddebian, zul!
[02:59] <bddebian> I'm beginning to realize that I really probably should have something specific I work on :-(
[03:04] <Hobbsee> bddebian: like the sponsorship queue?
[03:05] <bddebian> Are "package includes py[co]  files really worth the delta with debian?
[03:05] <Hobbsee> no idea
[03:05] <Hobbsee> LP: #83860
[03:08] <bddebian> What's that?
[03:08] <ajmitch> hello Hobbsee
[03:09] <bddebian> Oh sure, hi ajmitch
[03:09] <Hobbsee> bddebian: just a bug from a changleog
[03:09] <Hobbsee> Seveas: would you mind fixing ubotu to parse bugs with that syntax?
[03:09] <Hobbsee> hiya ajmitch
[03:09] <ajmitch> hello bddebian
[03:10] <RAOF> Heya Hobbsee, ajmitch bddebian :)
[03:11] <Hobbsee> hi RAOF.  have you fixed the world yet?
[03:11] <bddebian> Heya RAOF
[03:11] <RAOF> Hobbsee: Nah, I've been busy.
[03:11] <RAOF> I haven't even fixed Xgl yet :(
[03:11] <ajmitch> that's ok, we can file a removal request for xgl
[03:11] <bddebian> Don't feel bad, I don't fix anything :-)
[03:11] <bddebian> haha
[03:12] <Hobbsee> RAOF: darn you.
[03:13] <RAOF> Hobbsee: And to cap it off, I'll have a whole bunch of marking to do after tomorrow.
[03:13] <RAOF> Also, I'm tired.
[03:14] <TheMuso> bddebian: Ensure you are getting the latest dpkg...
[03:14] <Hobbsee> awww
[03:14] <bddebian> TheMuso: Aye, thx
[03:14] <pwnguin> so the guide to wminput suggests the following udev rule
[03:15] <pwnguin> KERNEL=="uinput", MODE="0666"
[03:15] <Hobbsee> siretart: you around?  i have a really stupid question.
[03:16] <ajmitch> pwnguin: that seems a bit silly
[03:16] <pwnguin> ajmitch: im not sure how to fix it though. they suggest a group
[03:16] <ajmitch> what is uinput?
[03:16] <pwnguin> im not sure but
[03:16] <pwnguin> i use it in another package =(
[03:16] <pwnguin> im guessing usb input
[03:18] <Hobbsee> ajmitch: can you deal with the latest MOTU mail please?
[03:18] <pwnguin> the debian fingerprint guys are moving forward on their stuff, and i know it uses uinput. it vaguely feels like a bug to have an authentication tool not owned by root
[03:19] <ajmitch> Hobbsee: you have root
[03:19] <Hobbsee> ajmitch: indeed, i do, but i dont actually know what my p/w on revu is - and it's asking me for it.
[03:19] <pwnguin> hah
[03:19] <ajmitch> heh
[03:20] <Hobbsee> ajmitch: hence the asking of the stupid question about
[03:20] <Hobbsee> s/about/above
[03:20] <ajmitch> removed, you can reply
[03:20] <bddebian> Hrm, sure, I'll upload some dutch translation patch.. :-)
[03:21] <Hobbsee> ajmitch: you could just fix the shell script too
[03:24] <pwnguin> uinput.c: /* *  User level driver support for input subsystem
[03:38] <ajmitch> Hobbsee: 'fixed', in a sense
[03:38] <Hobbsee> ajmitch: what'd you do?
[03:39] <ajmitch> well the uploaders.gpg keyring wasn't owned by www-data
[03:40] <ajmitch> it gets owned by whichever user 'revu-key update' was last run as
[03:40] <Hobbsee> oh, classy
[03:40] <ajmitch> so the script was failing on chgrp
[03:40] <Hobbsee> yep
[03:40] <ajmitch> I could remove 'set -e'
[03:49] <bddebian> Heya Burgundavia
[03:49] <Burgundavia> hey bddebian
[03:49] <bddebian> and jsgotangco
[03:50] <bddebian> and jdong
[03:50] <bddebian> and and and.. :-)
[03:52] <Hobbsee> bddebian: do the sponsorship queue instead.
[03:52] <Hobbsee> bddebian: if you get bored of that, start fixing bugs, from #2.
[03:53] <ajmitch> bddebian: if even I can fix bugs, you can as well
[03:55] <bddebian> Hobbsee: There isn't much there to do
[03:55] <bddebian> ajmitch: I can't fix shit :-)
[03:55] <bddebian> TheMuso: You still around?
[03:55] <ajmitch> bddebian: don't lie, get to work
[03:56] <bddebian> Name something I've fixed. :-)
[03:56] <Hobbsee> bddebian: yes there is.  there are still 30K of bugs.
[03:56] <bddebian> Hobbsee: In UUS?
[03:56] <ajmitch> bddebian: I'm not going to sit here & argue
[03:56] <Hobbsee> bddebian: in ubuntu
[03:56] <bddebian> ajmitch: Come on, it's fun :-)
[03:57] <ajmitch> no, it's really tiresome
[03:57] <TheMuso> bddebian: Yes.
[03:57] <bddebian> TheMuso: Now I remember what I wanted to ask you.  You are assigned to a libooc-xml bug but I was just about to request removal of that package.  Do you have a need for it?
[03:58] <bddebian> Hmm, bouncy does crash
[03:59] <bddebian> :-)
[03:59] <TheMuso> bddebian: Not that I know of. I can't remember why I assigned myself now.
[04:00] <bddebian> OK I'm going to ask for removal.  It won't build with oo2c and xml support is built in oo2c now
[04:32] <bddebian> So who knows python gtk? :-)
[04:34] <ajmitch> probably quite a few people
[04:52] <bddebian> Gawd I suck at debugging stuff
[04:54] <imbrandon> ajmitch: am i not correct in saying that upstream should not put `debain/` in a release tar if at all possible , so we dont have to repack ( i know repacking is last resort ) etc, i'm trying to explain this to someone but its not comming out right
[04:54] <imbrandon> and i'm not sure where its at in the policy if it is
[04:55] <bddebian> Tell them to go ahead and have one, just remove it on make dist ;-P
[04:55] <imbrandon> bddebian: right but make-dist is before they package the tar ;)
[05:04] <bddebian> Uhm, shouldn't make-dist create the tar?
[05:20] <bddebian> Drink more Mt. Dew!
[05:24] <Hobbsee> he needs a bigger fridge for that.
[05:24] <imbrandon> hehe
[05:24] <imbrandon> its oreo's and milk atm
[05:25] <ajmitch> scary
[05:25] <ajmitch> what happened to you?
[05:26] <bddebian> Milk? WTF? You can dip Oreos in Mt. Dew, can't ya? ;-P
[05:27] <imbrandon> heheh oreo's and OJ is better
[05:27] <imbrandon> my wife hates when i do that
[05:38] <imbrandon> LaserJock: goto sleep ;)
[05:39] <RAOF> Oh, miro.  Why must you mock me?
[05:39] <LaserJock> me??
[05:39] <LaserJock> sleep?!?
[05:39] <ScottK> Sleep is for the weak.
[05:40] <StevenK> No no, sleep is for the week
[05:40] <ajmitch> week after release?
[05:40] <StevenK> Sounds about right
[05:42] <imbrandon> :)
[05:49] <pwnguin> this should be interesting
[05:50] <pwnguin> wacom entries pulled from xorg.conf =/
[05:51] <imbrandon> thats normaly the first thing i delete
[05:51] <imbrandon> from xorg.conf
[05:52] <pwnguin> that would be okay
[05:52] <pwnguin> if i wanted my tablet not to work ;)
[05:53] <pwnguin> i was rather hoping the conf file restructuring would hit gutsy
[06:31] <ajmitch> tonyyarusso: explain why bug 140864 is failed against ubuntu, please? :)
[06:31] <ubotu> Launchpad bug 140864 in ubuntu "Not all Minnesota Team members are on ML" [Undecided,In progress]  https://launchpad.net/bugs/140864
[06:32] <tonyyarusso> ajmitch: b/c LP is stupid and I couldn't think of a better way to send notifications to the team until the other bug mentioned is fixed.  Suggestions for less weird ways _very_ welcome.
[06:33] <ajmitch> less spammish would be having a website product or similar for the team, with the team as bug contact
[06:34] <tonyyarusso> hmm, that might work
[06:34] <tonyyarusso> would it be easy to create such a product and then remove it if it became no longer relevant?
[06:34] <ajmitch> probably, but I don't know the details of removing products
[06:35] <tonyyarusso> ajmitch: are you aware of any other pseudo-projects like that?
[06:35] <ajmitch> no, that's why I suggested a website product, since plenty of teams have something like that
[06:37] <LaserJock> I see my pbuilder script has turned into a monster
[06:37] <ajmitch> mine isn't public
[06:37] <ajmitch> it's under lock & key on my disk
[06:37] <tonyyarusso> ajmitch: do you have a link to an example handy?
[06:38] <ajmitch> no
[06:38] <tonyyarusso> k
[06:48] <ScottK> Good night all.
[06:51] <ajmitch> night ScottK
[06:51] <bddebian> Gnight ScottK
[06:51] <bddebian> I'm heading too, gnight folks
[06:51] <ajmitch> night bddebian
[06:52] <bddebian> Gnight ajmitch
[06:59] <tonyyarusso> ajmitch: okay, I made something more sane - how do I remove it from Ubuntu?
[06:59] <ajmitch> mark it as invalid
[06:59] <tonyyarusso> done
[06:59] <tonyyarusso> that all?
[06:59] <ajmitch> cool, thanks
[06:59] <ajmitch> that's all you can do
[07:00] <tonyyarusso> ok
[07:56] <dholbach> good morning
[08:02] <ajmitch> hey dholbach
[08:03] <dholbach> hey ajmitch
[08:03] <RAOF> Hey dholbach.
[08:04] <dholbach> heya RAOF
[08:09] <superm1_> morning guys
[08:09] <superm1_> dholbach, can you unsubscribe ubuntu-main-sponsors from that lirc bug?  keescook uploaded it, but it still has a task in linux-ubuntu-modules which ubuntu-main-sponsors doesn't need to be subscribed for
[08:11] <dholbach> superm1_: ok, will do
[08:13] <RAOF> Oh, blargh.  Why won't Xgl do the decent thing and clean up it's lockfiles on exit?
[08:48] <elmargol> I try to build a feisty package on my ppa. I get E: Package dialog has no installation candidate
[08:48] <elmargol> I think dialog is in universe
[08:49] <dholbach> elmargol: best to try #launchpad - check https://help.launchpad.net/PPAQuickStart - especially the bit about the 'ogre model'
[08:52] <superm1_> elmargol, it shouldn't need to build depend on dialog, but the resultant binary would make sense to depend on something like that
[08:52] <elmargol> Do i have to set the Section on every Package: section?
[08:53] <elmargol> Or only at the Source:
[08:53] <superm1_> well it won't hurt in any way to put it for every section
[08:54] <StevenK> It depends if the Section is the same.
[09:15] <siretart> morning
[09:16] <dholbach> hey siretart
[09:17] <\sh> siretart, very nice mail :)
[09:17] <siretart> :)
[09:18] <siretart> \sh: I didn't suppose to post it to the mailing lists as well. but well, anyhow..
[09:18] <\sh> siretart, the good thing is, that thomas knows what's going on...
[09:18] <\sh> and I saw michael is already in the team..which is also very good :)
[09:20] <Le-Chuck_ITA> Hello all
[09:22] <\sh> siretart, when you have time and fun, check out apache directory studio...it's an eclipse plugin which contains an ldap browser and scheme editor....REALLY GOOD CRACK :)
[09:23] <ajmitch> hi siretart, \sh
[09:23] <siretart> *headscratch*
[09:23] <siretart> apache directory studio.. hmm. is this openldap or another ldap server?
[09:23] <ajmitch> siretart: I commented out 'set -e' in revu-key, and changed ownership of the uploaders.gpg keyring, it was causing it to fail when run by www-data
[09:24] <siretart> ajmitch: good catch!
[09:24] <siretart> ajmitch: feel free to commit it!
[09:28] <siretart> reminder to self: DO NOT close bugs with uploads to a (team-) ppa
[09:29] <pwnguin> heh
[09:29] <pwnguin> i do wish i could file bugs against my own ppa
[09:29] <siretart> pwnguin: you could create a product, and file bugs against that
[09:30] <siretart> ubuntu-backports is doing that for instance
[09:31] <pwnguin> well, these are basically packages that gutsy+1 will pull in from the same place i did
[09:31] <Le-Chuck_ITA> siretart: also use ntpdate in amd64 builders :)
[09:31] <pwnguin> at which point, all the bugs will have to be refiled against them in ubuntu as well
[09:32] <siretart> Le-Chuck_ITA: sorry?
[09:32] <Le-Chuck_ITA> siretart: you were talking about a fix: (LP# ...) you commited or about fixing this in launchpad?
[09:33] <RAOF> Le-Chuck_ITA: Ooooh, can you use that to make the amd64 builds actually work? :)
[09:33] <Le-Chuck_ITA> I had an amd64 package built and it worked?!
[09:33] <siretart> Le-Chuck_ITA: I'm still confused. I've uploaded test packages to a ppa, which closed bugs against packages in the ubuntu archive
[09:34] <Le-Chuck_ITA> siretart: Ok so never mind
[09:34] <Le-Chuck_ITA> dunno why, I thought you were going to fix the bug in LP :)
[09:35] <RAOF> Le-Chuck_ITA: Oh.  I thought you were talking about bug #137185.
[09:35] <ubotu> Launchpad bug 137185 in soyuz "Builds fail due to timestamp differences" [High,New]  https://launchpad.net/bugs/137185
[09:35] <Le-Chuck_ITA> also
[09:35] <Le-Chuck_ITA> :)
[09:35] <dholbach> siretart: that's a LP bug
[09:36] <dholbach> siretart: I filed it and hope it gets fixed ASAP
[09:36] <siretart> dholbach: I'm subscribed to that bug ;)
[09:36] <dholbach> ok great :)
[09:36] <ubotu> Launchpad bug 137815 in ubuntu "Default firewall rules needed along with program to set up firewall (dup-of: 52449)" [Undecided,New]  https://launchpad.net/bugs/137815
[09:36] <ubotu> Launchpad bug 52449 in ubuntu "Where is the firewall in Kubuntu" [Wishlist,Confirmed]  https://launchpad.net/bugs/52449
[09:36] <Le-Chuck_ITA> ahaha
[09:36] <Le-Chuck_ITA> sorry
[09:37] <Le-Chuck_ITA> typo
[09:38] <RAOF> Heh.
[09:38] <Le-Chuck_ITA> dholbach: To decrypt your password, type the following into your shell:  	> gpg -d <<EOT ; echo  	Now paste the text below, and enter EOT<return>   	another revu-key instance is already running check /tmp/revu-key.pid and PID 3202
[09:39] <Le-Chuck_ITA> this on revu site
[09:39] <dholbach> Le-Chuck_ITA: hm? I have my revu password
[09:39] <pkern> The password recovery is currently buggy.
[09:39] <Le-Chuck_ITA> ok, thanks
[09:39] <Le-Chuck_ITA> and... ehm, should I just retry until success?
[09:40] <pkern> Nope, some admin needs to remove the stale lockfile.
[09:40] <Le-Chuck_ITA> hmm
[09:41] <siretart> again?
[09:41] <\sh> I wonder if it's possible to run compiz on two screens
[09:41] <pkern> siretart: Looks like that. ;)
[09:41] <pkern> siretart: Is the source available somewhere?
[09:42] <siretart> pkern: sure, should be on launchpad
[09:42] <siretart> not sure if that changes have been pushed yet. there are some (site specific) revision in the branch on sparky that should not be pushed, though
[09:43] <RAOF> Amaranth: Hey!
[09:44] <siretart> stale lock file removed, and narrowed the lock
[09:44] <Amaranth> RAOF: hey
[09:44] <Le-Chuck_ITA> siretart: thanks
[09:44] <siretart> this should unbreak diff.py
[09:44] <RAOF> Amaranth: Xgl is broken in annoying ways!  Help me fix it! :)
[09:44] <Amaranth> RAOF: hehehe
[09:44] <Amaranth> RAOF: busy fixing compiz
[09:45] <Amaranth> elmo's gnome-terminals won't fullscreen
[09:45] <pkern> siretart: I did not find any locking stuff on LP, but k. ;)
[09:45] <\sh> Amaranth, hmmm? F11 FullScreen?
[09:45] <RAOF> Amaranth: Heh.  Works For Me(tm)
[09:45] <siretart> pkern: oh. I see. looking at it
[09:46] <Amaranth> \sh: right, in metacity gnome-terminal gets two configure events (because it's reparented) and so redraws itself
[09:46] <Le-Chuck_ITA> siretart: I am in trouble just again
[09:46] <Amaranth> \sh: in compiz it gets one, i need to make it get two
[09:46] <RAOF> Amaranth: Aaah.  I see.  It's empty until you touch it?
[09:47] <Le-Chuck_ITA> I registered on REVU months ago, I then lost the passprase of my old key - I need to register again since key recovery is for old key
[09:47] <Le-Chuck_ITA> I have registered my new key in launchpad and uploaded sources signed with the new key, to make the situation worse
[09:48] <Amaranth> RAOF: NVIDIA FIXED THE BLACK WINDOWS
[09:48] <RAOF> Amaranth: I know.  Also the VT switch bug, apparently.
[09:48] <Amaranth> RAOF: that was fixed in 100.14.11
[09:48] <RAOF> Amaranth: News to me.  It's still broken here (with sync_to_vblank on).
[09:49] <RAOF> Amaranth: Plus, the kernel team are hard-a-work shoving the new biniary blob down the appropriate tubes.
[09:50] <StevenK> What's a biniary blob?
[09:50] <pkern> Le-Chuck_ITA: Why did you keep the old key activated?
[09:50] <RAOF> It's quite a lot like a binary blob, but with more personality.
[09:50] <StevenK> RAOF: Thhbt
[09:51] <RAOF> Also, someone has put some XFont-enabled emacs-snapshot packages into a PPA.  Dear lord that looks better.
[09:51] <Le-Chuck_ITA> I didn't save a revocation certificate at the time, because I didn't know a lot about gpg and keys
[09:51] <RAOF> StevenK: That acronym means nothing to me :)
[09:51] <pkern> Le-Chuck_ITA: But the deactivation on LP might be distinct from that? (Although I did not try it.)
[09:51] <Le-Chuck_ITA> pkern: I think I deactivated that on LP
[09:51] <pkern> Le-Chuck_ITA: It somehow can't force me to revoke my key if I just want to deactivate it.
[09:51] <StevenK> RAOF: Blowing a raspberry
[09:52] <RAOF> StevenK: Ah.  Right.
[09:52] <pkern> Le-Chuck_ITA: Well, there are still two listed on `https://launchpad.net/~vincenzo-ml'.
[09:52] <Le-Chuck_ITA> you're right, deactivating now
[09:53] <pkern> Le-Chuck_ITA: I am pretty sure that two keys with the same email addresses confuse REVU.
[09:53] <Le-Chuck_ITA> I disabled the forgotten one, do you have to resync?
[09:54] <pkern> REVU needs to resync the keyring then, yeah.
[09:54] <pkern> (I can't do that...)
[09:54] <Le-Chuck_ITA> how often does this happen?
[09:55] <pkern> Le-Chuck_ITA: Once a day by cron, and manually by admins, I got told.
[09:55] <pkern> Le-Chuck_ITA: i.e. the problem should autofix itself until tomorrow.
[09:55] <Le-Chuck_ITA> ok, I will wait. A last question: I uploaded sources to revu signed with my new key, will they stay there?
[10:07] <Le-Chuck_ITA> ok I am always here asking everything
[10:07] <Le-Chuck_ITA> but is there a wiki page on non-native uploads?
[10:10] <RAOF> Le-Chuck_ITA: In what way "non-native"?  You mean "debian native", or what?
[10:10] <Le-Chuck_ITA> I mean the ones with the original tarball, since I have to upload a new version to REVU...
[10:14] <RAOF> Le-Chuck_ITA: What particularly about them?  You can include the original tarball in the source package by passing "-sa" to debuild, or dpkg-buildpakage.  Is that what you mean?
[10:15] <Le-Chuck_ITA> This is what I mean but... ehm, I have the original tarball, do I have to put in the directory containing the source tree, and debuild will find it, or what?
[10:17] <RAOF> Le-Chuck_ITA: It needs to be in the directory containing the unpacked source directory (ie: the parent directory of the source)
[10:18] <Le-Chuck_ITA> RAOF: it has also to be named in a particular way, and, also, how does debuild know not to pack the whole source tree?
[10:19] <RAOF> Le-Chuck_ITA: I'm not really following you.
[10:19] <RAOF> Let me start a different way:
[10:20] <RAOF> You have the upstream tarball, which you've downloaded and now want to package.
[10:20] <StevenK> When a daddy bit and a mummy bit love each other very much ...
[10:20] <StevenK> Ouch, that tickles
[10:21] <RAOF> First, you rename the tarball to "foo_version.orig.tar.gz".
[10:21] <RAOF> Then, you unpack that tarball.
[10:22] <RAOF> Then, you do your packaging stuff in the unpacked source.
[10:23] <RAOF> Then, when debuild comes along to build the source package, diffs your unpacked source tree against the .orig.tar.gz, creating the "foo_version-0ubuntu1.diff.gz" and friends.
[10:23] <Le-Chuck_ITA> and, this is what it isn't doing!
[10:23] <Le-Chuck_ITA> surely it's my fault but I don't understand where
[10:23] <RAOF> Can you pastebin the output of your debuilder run?
[10:23] <Le-Chuck_ITA> I have xournal_0.4.1.orig.tar.gz  and xournal-0.4.1 (d)
[10:24] <RAOF> Looks OK at this point...
[10:24] <Le-Chuck_ITA> but maybe I have to append also ubuntu1 to the orig.tar.gz name...
[10:24] <RAOF> No.
[10:25] <RAOF> Can you pastebin the output of your debuilder run?
[10:26] <RAOF> Presumably there's an error message hiding somewhere.
[10:26] <Le-Chuck_ITA> http://paste.ubuntu-nl.org/37885/
[10:27] <RAOF> Le-Chuck_ITA: Your version in debian/changelog is wrong :)
[10:27] <Le-Chuck_ITA> I have: xournal (0.4.1ubuntu1) gutsy; urgency=low
[10:28] <RAOF> You've got 0.4.1ubuntu1 (which is for a native package), rather than 0.4.1-0ubuntu1
[10:28] <RAOF> Is it a native package?  My guess is no :)
[10:28] <RAOF> Eh, it's a simple enough mistake.
[10:28] <pwnguin> so if someone files a bug against a universe package, is marking it invalid appropriate?
[10:29] <RAOF> pwnguin: Depends on whether or not it's an invalid bug, surely.
[10:29] <pwnguin> RAOF: i just did a search in launchad for invalid/wontfix
[10:29] <pwnguin> from what i can tell
[10:29] <pwnguin> at one point, lp was not for tracking universe bugs
[10:29] <Le-Chuck_ITA> RAOF: dpkg-source: building xournal using existing xournal_0.4.1.orig.tar.gz - yeah!
[10:30] <pwnguin> as mdz has several "we dont track unsupported packages in this system" replies
[10:30] <pwnguin> (in 2005)
[10:31] <RAOF> Oh.  That's no longer the case!  There are tons of valid bugs filed against universe :)
[10:31] <pwnguin> thats what i thought
[10:32] <pwnguin> theres a discussion in launchpad on closing bugs
[10:32] <pwnguin> apparently some people want to mark bugs WONTFIX or something to indicate they're ignoring it
[10:32] <RAOF> Yup.  This seems reasonable.
[10:33] <pwnguin> i donno
[10:34] <pwnguin> just because one person ignores a bug doesn't mean everyone should
[10:35] <proppy> regarding recently gutsy publish ubuntu2 version of poker-network package should I request a feisty-backport or a SRU ?
[10:35] <proppy> or is it too late
[10:40] <proppy> do not know if 'fixing crashing bug' is worth requesting a SRU
[10:41] <Le-Chuck_ITA> dholbach: Bug #137934 and http://revu.tauware.de/details.py?upid=267
[10:41] <ubotu> Launchpad bug 137934 in xournal "Please sponsor xournal 0.4.1" [Undecided,Incomplete]  https://launchpad.net/bugs/137934
[10:42] <propp1> is bug #137573 much more a candidate to feisty backport or SRU?
[10:42] <ubotu> Launchpad bug 137573 in poker-network "poker2d crash (SIGSEGV) at startup" [Medium,Fix released]  https://launchpad.net/bugs/137573
[10:43] <Le-Chuck_ITA> propp1: how long lasts feisty support?
[10:44] <propp1> Le-Chuck_ITA: you mean by upstream ? or by ubuntu ?
[10:45] <Le-Chuck_ITA> by ubuntu
[10:45] <dholbach> Le-Chuck_ITA: checking it out
[10:45] <dholbach> Le-Chuck_ITA: normally it's just enough to follow up on the bug report
[10:45] <Le-Chuck_ITA> hmmm, you're subscribed via ubuntu-bugs so
[10:45] <Le-Chuck_ITA> sorry, didn't mean to push you
[10:47] <propp1> dholbach: where should I follow up the bug report ?
[10:48] <dholbach> Le-Chuck_ITA: no problem
[10:48] <dholbach> propp1: I don't know what you are referring to?
[10:48] <propp1> (10:45:24 AM) dholbach: Le-Chuck_ITA: normally it's just enough to follow up on the bug report
[10:48] <propp1> sorry I must have missunderstood
[10:48] <dholbach> propp1: I was talking to Le-Chuck_ITA :)
[10:49] <dholbach> no problem
[10:49] <Le-Chuck_ITA> propp1 it was because I pinged him on IRC
[10:49] <dholbach> Le-Chuck_ITA: this change should not be necessary:
[10:49] <dholbach> --- xournal-0.3.3/debian/control        2007-09-19 10:45:48.000000000 +0200
[10:49] <dholbach> +++ xournal-0.4.1/debian/control        2007-09-19 10:45:41.000000000 +0200
[10:49] <dholbach> @@ -1,5 +1,5 @@
[10:49] <dholbach>  Source: xournal
[10:49] <dholbach> -Section: x11
[10:49] <dholbach> +Section: universe/x11
[10:49] <dholbach>  Priority: optional
[10:49] <dholbach>  Maintainer: Ubuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com>
[10:49] <dholbach>  XSBC-Original-Maintainer: Mathieu Bouchard <mbouchar@bioinfo.ulaval.ca>
[10:49] <dholbach> I can fix it if you like
[10:49] <Le-Chuck_ITA> yes please
[10:49] <dholbach> ok
[10:50] <dholbach> test building it
[10:52] <pkern> dholbach: Daniel, when is the `universe/' bit necessary? I know that packages get promoted w/o source changes to main, but according to lp-users you sometimes have to add it...
[10:53] <dholbach> pkern: that's just for PPA uploads
[10:53] <pkern> dholbach: Ok.
[10:53] <dholbach> cf. https://help.launchpad.net/PPAQuickStart -> 'ogre model'
[10:53] <dholbach> apart from that it should not be necessary at all
[10:53] <pkern> dholbach: Does it hurt if it is uploaded to Ubuntu proper with this change? i.e. PPA packages could not be uploaded verbatim?
[10:54] <dholbach> we override it in LP for archive.ubuntu.com anyway
[10:54] <dholbach> pkern: it would not hurt, no
[10:54] <dholbach> pkern: I just removed it because it's a change vs the debian package and I noticed it before the upload :)
[10:55] <dholbach> pkern: but right, I see your point - it's not nice
[10:55] <Le-Chuck_ITA> in any case a ppa package is likely to have a different changelog
[10:55] <pkern> That would not hurt, would it?
[10:55] <dholbach> no
[10:56] <dholbach> we should ask the LP folks in the next PPA session what their plans are for that
[10:56] <Le-Chuck_ITA> yes but you can't upload a ppa package
[10:56] <dholbach> we should chime in on a specficiation dealing with copying over sources
[10:56] <Le-Chuck_ITA> you have to edit the changelog to reflect ubuntu versions
[10:56] <pkern> Le-Chuck_ITA: So your point is that you have to edit the package anyway.
[10:57] <Le-Chuck_ITA> yes at least for now
[10:59] <propp1> Le-Chuck_ITA: do not know about feisty support
[10:59] <Le-Chuck_ITA> It was just my theory that if feisty is going to be unsupported an SRU does not make much sense now
[10:59] <Le-Chuck_ITA> but I don't know for sure
[10:59] <propp1> how ok
[11:00] <propp1> you mean as feisty is not LTS
[11:00] <Le-Chuck_ITA> yes
[11:00] <propp1> so a backport make more sense ?
[11:00] <Le-Chuck_ITA> In my opinion yes and it's easier too
[11:01] <propp1> ok :)
[11:01] <propp1> Le-Chuck_ITA: thanks
[11:01] <pkern> "Each Ubuntu release is supported for 18 months with security patches, fixes for critical bugs that could cause data loss, and extra translations."
[11:02] <Le-Chuck_ITA> bug in question does not cause data loss but the package is completely broken
[11:02] <Le-Chuck_ITA> would you advice SRU pkern?
[11:03] <pkern> Le-Chuck_ITA: I am not the right person to ask I am afraid. (:
[11:05] <Le-Chuck_ITA> I go back to my boring everyday maths, bye and thanks all for co-operation
[11:05] <propp1> Le-Chuck_ITA: thanks anyway
[11:10] <dholbach> siretart: I will re-start the thread regarding the packaging guide to ubuntu-devel@
[11:10] <dholbach> siretart: I think that more people should have their say on it
[11:10] <dholbach> siretart: I'll try to sum up all the pros and cons we pointed out on ubuntu-motu@ already
[11:11] <propp1> bug #140909 filled
[11:11] <ubotu> Launchpad bug 140909 in feisty-backports "Please backport  poker-network 1.1.1-1ubuntu2 from gutsy to feisty" [Undecided,New]  https://launchpad.net/bugs/140909
[11:12] <propp1> should i suscribe anyone, or is it just fine like this ?
[11:12] <dholbach> https://wiki.ubuntu.com/BackportRequestProcess
[11:13] <proppy> dholbach: thanks
[11:13] <siretart> dholbach: good idea. thanks!
[11:13] <dholbach> siretart: great
[11:21] <pkern> dholbach: There's a packaging guide? That's also one point in the draft response to your mail to me. Heh. :D (I did not yet come around to answer you, mainly because I have some examinations in October.)
[11:21] <dholbach> pkern: I wish you all the best with those then!
[11:22] <dholbach> pkern: https://help.ubuntu.com/6.10/ubuntu/packagingguide/C/index.html
[11:23] <pkern> dholbach: Thanks (:
[11:26] <pkern> dholbach: That's really going into the right direction. Especially points like `where to begin' split into those who are new to packaging and those unfamiliar with Ubuntu.
[11:26] <dholbach> pkern: we have a lot of documents on the wiki about that too
[11:26] <dholbach> that's why I personally propose to move it to the wiki
[11:26] <dholbach> but that's what the thread is about
[11:27] <pkern> dholbach: Right. But one has to dig in the wiki to find those.
[11:27] <dholbach> if you're on ubuntu-devel@ feel free to chime in
[11:27] <dholbach> I personally would rather look in the wiki than on help.u.c
[11:27] <dholbach> :)
[11:27] <dholbach> but right, in any case it should be more discoverable
[11:28] <pkern> dholbach: Point is that when you are new, you really should to read a guide. Obviously that one could also be put on the wiki, as long as it links to all the needed articles.
[11:28] <dholbach> right
[11:28] <pkern> And too few people read the Debian New Maintainers Guide (and at least partially the Policy). \:
[11:29] <dholbach> it'd be nice to have correct links and references all over the place
[11:30] <pkern> Of course it's easier to keep something up-to-date if you put it into the Wiki. (But it could also get outdated there, of course.)
[11:31] <dholbach> sure
[11:31] <dholbach> the main concern for some is that it's open to malicious editing
[11:31] <pkern> But I doubt the usefulness of static lists like `https://help.ubuntu.com/6.10/ubuntu/packagingguide/C/appendix-debhelper.html' -- a list of debhelper scripts.
[11:31] <pkern> Those should be autogenerated from the manpages together with the corresponding description.
[11:31] <dholbach> once it's on the wiki you can edit more easily ;-)
[11:31] <pkern> Such things may be easier on static content than on wiki pages. \:
[11:32] <dholbach> we could autogenerate stuff by using editmoin
[11:32] <dholbach> but first we need to come to an agreement on that discussion
[11:45] <pkern> dholbach: Just as a sidenode: Wouldn't the docbook source be easier to translate? Or is there `no use' in having translated versions of the packaging guide because we want that all devs communicate in English anyway?
[11:46] <dholbach> pkern: that's a question you could follow up on the thread :)
[11:47] <dholbach> people use the wiki for translations too
[11:47] <dholbach> I'm not saying that it's perfect, but translating docbook is probably not what I'd call easy
[11:57] <pkern> dholbach: Disclaimer: I'm not (yet) on ubuntu-devel. I probably should get my slrn in shape to access it via gmane... but well. ;)
[11:58] <dholbach> :)
[01:08] <proppy> I believe there is typo in https://help.ubuntu.com/6.10/ubuntu/packagingguide/C/ubuntu-sync.html how can I edit it ?
[01:15] <bluekuja> proppy, you can't
[01:15] <bluekuja> proppy, report a bug against packaging guide
[01:15] <bluekuja> and someone will fix it
[01:20] <proppy> ok
[01:21] <proppy> in the packaging guide product on launchpad
[01:21] <proppy> ?
[01:23] <ajmitch> soren: if you have time, can you test out samba at https://edge.launchpad.net/%7Eajmitch/+archive once it builds in the PPA?
[01:29] <proppy> bluekuja: launchpad url?
[01:30] <bluekuja> proppy, let me see
[01:31] <bluekuja> proppy, use ubuntu documentation
[01:31] <proppy> bluekuja: thanks
[01:31] <bluekuja> proppy, like this https://bugs.edge.launchpad.net/ubuntu-doc/+bug/69650
[01:31] <ubotu> Launchpad bug 69650 in ubuntu-doc "Packaging Guide says "you a shell script"" [Undecided,Confirmed] 
[01:31] <bluekuja> proppy, thanks for reporting
[01:32] <fernando> moin all
[01:32] <bluekuja> hi fernando
[01:32] <soren> ajmitch: Sure, will do.
[01:32] <fernando> hi bluefoxicy
[01:32] <fernando> ops
[01:32] <fernando> hi bluekuja
[01:32] <fernando> =)
[01:32] <ajmitch> soren: thanks, I don't have much to test with here :)
[01:32] <bluekuja> :)
[01:33] <ajmitch> soren: I didn't put in the printer change, pitti wasn't entirely keen on it
[01:33] <proppy> bluekuja: mine was dup of bug #97355
[01:33] <ubotu> Launchpad bug 97355 in ubuntu-doc "Packaging Guide command error" [Undecided,Confirmed]  https://launchpad.net/bugs/97355
[01:33] <bluefoxicy> what
[01:34] <bluefoxicy> 2.6.23 has a new scheduler ... and tickless operation.  :(
[01:34] <bluekuja> proppy, oh it was already assigned
[01:34] <soren> ajmitch: I don't have much of a test setup here, either. I intend to give it a quick spin, and if it flies, get it into the archive asap, so we have a bit of time to discover bugs and weed them out before release.
[01:35] <ajmitch> it needs to go in today, to make it for beta
[01:36] <ajmitch> be sure to check debian/patches/chgpasswd.patch, I did that quickly
[01:36] <ajmitch> and I've been doing *far* too much PHP coding lately
[01:38] <proppy> is someone up to review #140915 ?
[01:38] <proppy> bug #140915
[01:38] <ubotu> Launchpad bug 140915 in ubuntu "Please merge poker-network (1.2.0-1) from debian unstable main" [Undecided,New]  https://launchpad.net/bugs/140915
[01:39] <ajmitch> this is a new upstream version, so you'll need to get a freeze exception from motu-uvf
[01:39] <ajmitch> !uvf
[01:39] <ubotu> uvf is Upstream Version Freeze.  For an exception, see https://wiki.ubuntu.com/FreezeExceptionProcess#head-9523bc4076ff011324d67cddc97969ec609618d6
[01:39] <ajmitch> looks like you probably have the info needed on there, but they need to be subscribed
[01:40] <bluekuja> proppy, I see no debdiffs there
[01:40] <bluekuja> and yes its new upstream
[01:40] <bluekuja> so need an exception
[01:40] <bluekuja> and a revu link
[01:40] <bluekuja> if accepted
[01:40] <ajmitch> soren: I'm going to have to sleep now, so if it all works out ok I can upload in the morning, or you may want to get it uploaded before then
[01:41] <bluekuja> (not a debdiff)
[01:45] <proppy> bluekuja: attached a debdiff
[01:45] <proppy> oh ok :)
[01:45] <proppy> lagging
[01:45] <proppy> I've attached the necessary files
[01:45] <proppy> except maybe the pbuilder.log which I need help with
[01:46] <bluekuja> proppy, you dont need to provide a debdiff on this case
[01:46] <bluekuja> look above
[01:47] <elmargol> How do I sign a Release file?
[01:47] <proppy> bluekuja:  I've followed the merge process in the packaging guide and the UVFs
[01:48] <bluekuja> proppy, it's a new upstream release
[01:48] <proppy> ok
[01:48] <bluekuja> proppy, so you need an approvation
[01:48] <bluekuja> from the UVF team
[01:48] <proppy> ok
[01:48] <bluekuja> we are on new freeze
[01:48] <bluekuja> you know
[01:48] <proppy> so next step is to suscribe uvf team ?
[01:48] <bluekuja> yea
[01:48] <proppy> ok thanks
[01:49] <bluekuja> and provide requested files
[01:49] <bluekuja> like build and install log
[01:49] <bluekuja> and then subscribe motu-uvf
[01:49] <bluekuja> and if accepted prepare a new package on revu
[01:49] <proppy> and *THEN* I will fill a merge request ?
[01:49] <bluekuja> no
[01:49] <bluekuja> you just make a new package
[01:49] <proppy> ok
[01:49] <bluekuja> with the new upstream release
[01:50] <proppy> *including* remaining ubuntu changes ?
[01:50] <bluekuja> proppy, of course
[01:50] <proppy> ok
[01:50] <bluekuja> proppy, you have to keep those
[01:50] <proppy> thanks a lot for clearing this up
[01:50] <bluekuja> and maybe try to debdiff it with latest ubuntu version
[01:50] <bluekuja> on the archive
[01:50] <bluekuja> leaving for lunch
[01:50] <bluekuja> brb
[01:51] <proppy> bluekuja: some are already applied in the new upstream version, only a few in debian/control file remains, (as you see in the debdiff)
[01:51] <proppy> thanks
[01:51] <proppy> ls
[01:51] <soren> ajmitch: When is "the morning"?
[01:51] <ajmitch> ~8 hours
[01:51] <soren> ajmitch: That's ok.
[01:51] <ajmitch> given that it's close to midnight now
[01:52] <proppy> Is universe activated by default in pbuilder ?
[01:52] <ajmitch> no, it's not
[01:52] <ajmitch> good night all :)
[01:52] <proppy> how can I active it ?
[01:52] <proppy> good night ajmitch
[01:54] <RAOF> night ajmitch
[02:01] <soren> proppy: prepend "universe/" to the section of the package you want to build.
[02:03] <Fujitsu> soren: pbuilders don't have ogre-modle.
[02:03] <Fujitsu> *model
[02:06] <proppy> just found out pbuilder login --save-after-login
[02:08] <zul_> morning
[02:08] <bluekuja> proppy, anyway you just have to update it with new source
[02:08] <bluekuja> and you're done
[02:09] <bluekuja> proppy, dont lose changes
[02:09] <bluekuja> of course
[02:10] <proppy> I have to add universe to the /etc/apt/source.list *inside the base.tgz* to be able to pbuilder poker-network package
[02:10] <bluekuja> proppy, no
[02:10] <bluekuja> proppy, use pbuilderrc
[02:10] <proppy> oh ok
[02:11] <proppy> way more fast
[02:11] <proppy> cause rebuilding base.tgz is heavy and slow
[02:14] <proppy> bluekuja: using COMPONENTS=main universe
[02:14] <elmargol> I have a general question are .deb packages signed? Or is only the Release file signed on the repository?
[02:14] <broonie> Packages aren't signed, trust is derived from the Release file.
[02:15] <elmargol> ah ok so I only have to sign the Release files?
[02:18] <Kopfgeldjaeger> hi
[02:19] <bluekuja> proppy, yes
[02:19] <bluekuja> uncomment it
[02:22] <proppy> bluekuja: thanks
[02:22] <bluekuja> proppy, np
[02:22] <bluekuja> :)
[02:31] <ScottK> dholbach: I have a change for ubuntu-dev-tools, but do not have bzr set up.  What's the best way for me to get the change uploaded?
[02:35] <geser> ScottK: either do a bzr checkout, apply, commit or try to gate it through someone else :)
[02:35] <geser> Hi Hobbsee
[02:36] <ScottK> geser: It's #2 I'm looking for.
[02:37] <Hobbsee> hi geser
[02:38] <bluekuja> Hobbsee, one fast question
[02:38] <bluekuja> Hobbsee, is ok to modify a makefile.in without a patch system?
[02:38] <bluekuja> (modify directly)
[02:39] <bluekuja> geser: ^^
[02:40] <geser> bluekuja: why should it be not ok?
[02:40] <geser> I've done that in the past
[02:40] <bluekuja> geser: by running autotools
[02:40] <bluekuja> wont mess changes up at next revision?
[02:41] <bluekuja> geser, but if you've done that in the past, it's ok then
[02:41] <bluekuja> thanks
[02:41] <pkern> bluekuja: You should ensure that the output of the autotool regeneration does not clutter the diff.
[02:41] <geser> that could only be a problem when you change the generated files
[02:42] <bluekuja> pkern, ok perfect
[02:42] <bluekuja> geser, yeah, that's it
[02:42] <geser> I usually patch Makefile.am and Makefile.in so the change doesn't get lost if someone runs autotools again
[02:42] <bluekuja> geser, yep, that's what I was saying
[02:42] <pkern> bluekuja: Uh, you said Makefile.in and I read configure.in...
[02:43] <bluekuja> pkern, yeah, I'm talking about makefile.in
[02:43] <pkern> bluekuja: Personally I would modify Makefile.am and re-run autotools on build.
[02:43] <pkern> (In this case automake...)
[02:43] <Fujitsu> pkern: Please don't...
[02:44] <Fujitsu> Minimal diff is always good.
[02:44] <pkern> Fujitsu: Is there a reason against it? Unpredictable builds?
[02:44] <pkern> Fujitsu: I said autotools on build, not on clean, heh.
[02:44] <Fujitsu> Adding dependencies and the like probably isn't ideal.
[02:44] <Fujitsu> Cleaner to just patch various things, IMO.
[02:46] <geser> pkern: when you use autotools during build you don't know if it still build in say 2-3 months because autotools change in between and now the package fails to build due to an error
[02:46] <pkern> It's probably a question if the package defaults to maintainer mode or not. \: If the build system is regenerated when a source file (i.e. Makefile.am) changes, that would suck.
[02:47] <pkern> geser: Well, in case of automake there are specific versions available to depend on. But yeah, that's the point with unpredictable builds.
[02:47] <pkern> geser: But the same could happen on every build-dep that changes.
[02:47] <geser> pkern: yes, but first you need to find out which version it needs
[02:47] <pkern> geser: That's stated in configure.ac.
[02:47] <geser> pkern: sure
[02:47] <bluekuja> geser: it was  about http://launchpadlibrarian.net/9376568/rkward_0.4.7a-1ubuntu2.debidff
[02:48] <proppy> bluekuja: how can I generate the install.log you've mentionned earlier ? with pbuilder ?
[02:48] <pkern> geser: I don't know the Ubuntu policy about that, that's right. That's why I said "personally".
[02:48] <bluekuja> proppy, just dpkg -i package.deb
[02:48] <bluekuja> proppy, and C&P the output
[02:49] <proppy> bluekuja: on a fresh debootstraped gutsy chroot ?
[02:49] <bluekuja> proppy, yep
[02:49] <proppy> ok
[02:49] <bluekuja> geser: if that's ok
[02:49] <geser> pkern: afaik it's mostly a personal style if you patch or regenerate
[02:50] <bluekuja> geser: I move to test and upload it
[02:50] <bluekuja> geser: looked at that debdiff?
[02:51] <geser> bluekuja: for me that debdiff looks ok
[02:51] <bluekuja> geser: k, thanks
[02:51] <pkern> Those #>- lines look strange. o_O
[02:51] <bluekuja> mmm
[02:52] <proppy> bluekuja: ok
[02:52] <bluekuja> pkern, why are like those?
[02:52] <geser> bluekuja: I'm not sure but isn't there a $(DESTDIR) missing in the changed lines in Makefile.in?
[02:53] <geser> I mean Makefile.am
[02:53] <pkern> geser: Well spotted (:
[02:54] <bluekuja> geser: where exactly?
[02:55] <bluekuja> like here $(mkinstalldirs) /usr/share/applications?
[02:55] <geser> yes
[02:55] <bluekuja> yeah, destdir
[02:55] <bluekuja> is missing
[02:55] <bluekuja> in all of them
[02:56] <bluekuja> also in uninstall-local:
[02:56] <bluekuja> gonna ping him to fix those
[02:56] <pkern> That is fun... they obviously messed with Makefile.in after generation through automake.
[02:57] <pkern> bluekuja: At least it is not necessary to patch commented-out lines.
[02:57] <bluekuja> pkern, yeah
[02:57] <bluekuja> pkern, for this time, I gonna tell him to just fix destdir stuff
[02:58] <bluekuja> without a patch system
[02:59] <pkern> http://paste.debian.net/37525
[02:59] <pkern> They do their own DESTDIR fixup, hah.
[02:59] <pkern> Morons.
[03:00] <bluekuja> :D
[03:00] <proppy> bluekuja: is there a way to apt-get install the deps of a given deb files, for easy dpkg -i it after ?
[03:00] <bluekuja> so the fix will get away
[03:00] <bluekuja> at next autotools run
[03:00] <pkern> bluekuja: La la la... they should have fixed the kde_ vars instead... so yeah, it would.
[03:01] <bluekuja> proppy, apt-get build-dep package
[03:01] <bluekuja> pkern, so you suggest a patch system then
[03:01] <proppy> bluekuja: I mean the deps not the build-dep
[03:01] <bluekuja> proppy, why not manually?
[03:01] <proppy> bluekuja: for generating the install.log
[03:01] <pkern> bluekuja: Rather beating upstream to use Automake in a sane way, heh.
[03:01] <bluekuja> pkern, lol
[03:01] <geser> proppy: apt-get -f install
[03:02] <bluekuja> yeah that would be definitely better
[03:02] <geser> but look what it wants to do
[03:02] <pkern> bluekuja: But yes, because you could place a comment about that brokeness in a patch file.
[03:02] <bluekuja> I hope it will make it geser
[03:02] <bluekuja> pkern, ok, I comment the bug
[03:02] <bluekuja> and ask for a patch system then
[03:02] <bluekuja> I already asked
[03:02] <bluekuja> but laserjock said it's not necessary
[03:03] <proppy> geser: so to generate a valid install.log for UVFe => dpkg -i *.deb ; apt-get -f install ; dpkg -i *.deb > install.log ?
[03:04] <geser> hmm, proppy I'm not sure but you could use piuparts for that
[03:05] <soren> Fujitsu: Huh?
[03:06] <proppy> geser: nice !
[03:06] <Fujitsu> soren: Adding universe/ to the section won't do much in pbuilder...
[03:07] <soren> Fujitsu: Oh, it's pbuilder? I though it was PPA.
[03:07] <Fujitsu> `Is universe activated by default in pbuilder ?'
[03:07] <Hobbsee> ScottK: looks like there are more blanket uvfe's?  where's the FAI one documented?
[03:09] <soren> Fujitsu: Yes, I see that now. My bad.
[03:09] <fernando> can i use ppa with other protocol?
[03:09] <fernando> sftp?
[03:09] <Fujitsu> fernando: Not at this time.
[03:09] <fernando> Fujitsu, thanks
[03:09] <geser> Hobbsee: didn't get fai a uvfe in bug #139637?
[03:09] <ubotu> Launchpad bug 139637 in fai "new upstream fai 3.2.1" [Undecided,Fix released]  https://launchpad.net/bugs/139637
[03:10] <Hobbsee> oh right, so i just missed it.
[03:12] <geser> Hi bddebian
[03:13] <bddebian> Heya gang
[03:13] <bddebian> Hi geser
[03:20] <proppy> suscribed motu-uvf for bug #140915
[03:20] <ubotu> Launchpad bug 140915 in ubuntu "Please merge poker-network (1.2.0-1) from debian unstable main" [Undecided,New]  https://launchpad.net/bugs/140915
[03:21] <zul> proppy: yes we know we usually get an email about it
[03:21] <proppy> sorry
[03:30] <elmargol> I created a feisty repository for gnunet. "deb http://gnunet.org/download/debian/ feisty universe"
[03:30] <elmargol> I get Failed to fetch http://gnunet.org/download/debian/dists/feisty/Release  Unable to find expected entry  universe/binary-i386/Packages in Meta-index file (malformed Release file?)
[03:30] <elmargol> Any ideas whats wrong?
[03:44] <pkern> elmargol: It obviously lacks Packages files in addition to Packages.gz files.
[03:44] <pkern> (At least so I guess, and don't ask me why.)
[03:45] <pkern> Hm, it probably uncompresses the file and then checks the checksum...
[03:45] <pkern> But I don't know that for sure.
[04:05] <dholbach> ScottK: did you get that change uploaded already?
[04:11] <MadMan2k> hi, is there some document describing how debian package versions are being compared?
[04:12] <MadMan2k> I just wondered reading the PPA docs when I saw that an appended "~" lowers the version number
[04:12] <Hobbsee> MadMan2k: man dpkg, see teh part about --compare-versions
[04:15] <MadMan2k> thanks, but is there als a more in detail documentation how to version packages?
[04:16] <jdong> hmm speaking of that, it's probably not a bad idea to do a spec on ~ version number usage....
[04:16] <jdong> I'm personally not satified with all the lettered names we currently use
[04:17] <jdong> there should be some sort of tiered numbering priority, like ~0 for totally unofficial or experimental, ~1 for PPA, ~2 for backports, etc....
[04:18] <Hobbsee> jdong: there is oen - i'ts mostly followed, too.
[04:18] <MadMan2k> I sometimes also see "+" in version numbers - is there perhabs a spec covering those special characters?
[04:18] <Hobbsee> jdong: of course, random packages from random places arent going to adhere to a ubuntu spec anyway.
[04:18] <jdong> Hobbsee: right; where is this spec?
[04:19] <Hobbsee> jdong: on how to do ubuntu versioning?  debian packaging guide, ubuntu packaging guides...
[04:19] <Hobbsee> ppa's have no consideration of version numbers
[04:19] <Hobbsee> backports is your domain anyway, so the rest of the archive wouldnt overly care
[04:20] <jdong> right....
[04:20] <jdong> I'll have to talk to an archive admin sometime about that
[04:20] <jdong> I'd like to switch to numeric versions on backport versions....
[04:21] <Hobbsee> ~backport1?
[04:21] <Hobbsee> or whichever
[04:21] <jdong> more like ~7.04backport1
[04:21] <jdong> so that way at least I'm guaranteed the numbers increment per release
[04:21] <jdong> and odn't end up with ~hoary > ~dapper issues :)
[04:22] <Hobbsee> ah yes
[04:22] <Hobbsee> that would be smart.
[04:22] <Hobbsee> jdong: pretty much pick a system and use it
[04:22] <Hobbsee> and update the backports doco
[04:22] <jdong> yeah, and tell whoever manages the backports launchpad foo script to update to it
[04:22] <jdong> I'll write a better section on the wiki on backport versioning :)
[04:23] <MadMan2k> could you perhaps point me to the document on how to do ubuntu versioning? I cant find anything like that in the packaging guide...
[04:43] <Kopfgeldjaeger> !packaging guide
[04:43] <ubotu> The packaging guide is at http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html - See https://wiki.ubuntu.com/MOTU/Packages/New for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/DeveloperResources - See also !backports
[04:44] <Hobbsee> MadMan2k: the part about using upstream-version-0ubuntu1 ?
[04:44] <Hobbsee> or adding ubuntu1 to debian revisions?
[04:44] <Hobbsee> i thought that was there, the latter part would be in the merge documentations
[04:45] <MadMan2k> no Im more intrested in the special cases like svn checkouts
[04:45] <MadMan2k> some pakcages have a "+svn<date>"
[04:45] <MadMan2k> some a "svn<revision>"
[04:46] <jdong> that seems to be a convention set by the package maintainer
[04:46] <Hobbsee> MadMan2k: that's because you want the 1.0 to replace the 1.0+svn<foo>.
[04:46] <MadMan2k> so theres no general convention on that?
[04:46] <jdong> the svn<date> convention is carried over from the cvs<date> convention
[04:46] <Hobbsee> MadMan2k: there are a few, it tends to be personal preference - as long as you take upgrades into account
[04:47] <jdong> svn also introduces an easier-to-reference unique revision identifier, hence the svn<revision> format
[04:47] <MadMan2k> Hobbsee, so an appended "+" also lowers the version number?
[04:47] <Hobbsee> MadMan2k: 1.0+svn<foo> is wrong.
[04:47] <Hobbsee> sarah@LongPointyStick:~$ dpkg --compare-versions 1.0 gt 1.0+svn && echo true
[04:47] <Hobbsee> sarah@LongPointyStick:~$
[04:47] <jdong> + increases
[04:47] <Hobbsee> oh, so +svn would usually mean +svn fixes.
[04:47] <Hobbsee> as in, a later version
[04:47] <jdong> Hobbsee: it's right if 1.0+svn means it's higher than 1.0
[04:47] <Hobbsee> that's slightly confusing
[04:47] <jdong> it's wrong if it is saying a pre-1.0 svn snapshot
[04:47] <Hobbsee> although if you checked the changelog, all would become clear
[04:47] <Hobbsee> exactly
[04:48] <Hobbsee> in which case you'd use 1.0~svn<foo> or something
[04:48] <Hobbsee> 1.0~beta<foo> is common enough
[04:48] <MadMan2k> the thing is that I want to put some svn versions in my PPA, so I need to know myself :)
[04:48] <Hobbsee> (all with -0ubuntu1 at the end, mostly)
[04:48] <Hobbsee> MadMan2k: is the svn version higher than the released version?
[04:49] <Hobbsee> MadMan2k: really, you can pick any version you happen to like the look of, as long as you make sure it wont conflict with any past, present, or future upgrades, from your or the ubuntu repository.
[04:49] <MadMan2k> yes, so considering what you just said it would be +svn
[04:49] <Hobbsee> yeah
[04:49] <Hobbsee> the idea between using 1.0~ppa1 is that it's then less than 1.0, so if 1.0 makes it into ubuntu, it gets upgraded to that.
[04:50] <MadMan2k> ok, thaks :)
[04:50] <MadMan2k> *thanks
[04:50] <Hobbsee> and there are some weird versions in the archive
[04:50] <Hobbsee> -input-synaptics comes to mind
[04:50] <Hobbsee> MadMan2k: aptitude changelog xserver-xorg-input-synaptics for some fun
[04:52] <zul> Hobbsee: can you +1 for dkms
[04:53] <Hobbsee> zul: just seen the mail.
[04:54] <Hobbsee> dholbach: please upload that as appropriate
[04:55] <Hobbsee> zul: or you can, if you wish.
[04:55] <zul> at work dholbach would be better
[04:56] <zul> or someone from the kernel team as well
[04:56] <Hobbsee> zul: OK
[05:26] <Hobbsee> oh, damned people who dont read the documentation.
[05:28] <Hobbsee> is StevenHarperUK@gmail.com here?
[05:29] <Hobbsee> hmm.  not on irc.
[06:05] <ScottK> dholbach: No.  It turned out to be slightly more complex than I thought.  Ther version I have now works for Debian, but not for Ubuntu.
[06:06] <dholbach> ScottK: hrm
[06:07] <ScottK> dholbach: The trick is that if you don't use the --mirror option pbuilder looks at the Ubuntu mirror even if --othermirror points you at Debian.
[06:09] <ScottK> jdong: Tell them to install Tracker and then after they remove it, KTorrent will feel like less hard drive usage.
[06:09] <jdong> ScottK: lol :)
[06:31] <ScottK> proppy: Are you there?
[06:32] <proppy> ScottK: yep
[06:33] <proppy> ScottK: I'll be always there for you
[06:33] <ScottK> Heh
[06:33] <jdong> haha
[06:33] <bddebian> heh3
[06:34] <ScottK> proppy: For your UVFe, one of the required elements is an install log.  In the case of your package it should be in a system that does NOT have any mysql bits installed already.
[06:34] <ScottK> Demonstrate that it installs correctly and I'll ack it (you need two).
[06:35] <proppy> ScottK: can I verify with you the procedure to generate this install.log
[06:35] <proppy> ScottK: debootstrap gutsy gutsy
[06:35] <proppy> ScottK: chroot gutsy
[06:35] <proppy> ScottK: dpkg -i *.deb
[06:35] <proppy> ScottK: apt-get -f install
[06:35] <proppy> ScottK: dpkg -i *.deb
[06:35] <proppy> is fine ?
[06:36] <ScottK> You shouldn't need the second dpkg -i *.deb should you?
[06:36] <ScottK> Generally yes and then whatever that spews on your screen, copy it into a text file and attach it to the bug.
[06:40] <bddebian> Shit, stupid x264 is maintianed in svn
[06:41] <ScottK> dholbach: Are you going to upload dkms?
[06:42] <Hobbsee> ScottK: benc was going to
[06:42] <Hobbsee> ScottK: the guy bumped the version number to not conflict
[06:42] <ScottK> Hobbsee: OK.  Just as long as someone does it....
[06:42] <dholbach> ScottK: thanks for prodding me - the kernel team is on it
[06:42] <ScottK> OK.
[06:43] <proppy> ScottK: thanks
[06:43] <ScottK> proppy: Did you attach the install log yet?
[06:45] <proppy> ScottK: working on it
[06:45] <ScottK> proppy: OK.
[06:51] <Hobbsee> bigon: uh, why @ Bug #141015
[06:51] <ubotu> Launchpad bug 141015 in ubuntu-dev-tools "Correctly pass path to dch" [Undecided,New]  https://launchpad.net/bugs/141015
[06:51] <MehdiHassanpour> geser: do you have a script to automate reprepro to add packages to apt repo?
[06:51] <Hobbsee> (and it's in bzr)
[06:52] <Hobbsee> bigon: it automatically scans to see where debian/changelog exists - why add hte extra part, which does exactly the same thing?
[06:52] <Hobbsee> ie, why fix what isnt broken?
[06:52] <jussi01> hmmm, could someone help me with this? http://paste.ubuntu-nl.org/37930/
[06:52] <geser> MehdiHassanpour: why should I have a script for it?
[06:53] <bigon> Hobbsee: well I had some problem with update-maintainer when you are already in the debian dir
[06:53] <MehdiHassanpour> don't know, just asked...
[06:53] <bigon> Hobbsee: the changelog was not updated
[06:54] <Hobbsee> bigon: from where is your update maintainer?
[06:54] <MehdiHassanpour> any one has a script to automate reprepro to add packages to apt repo?
[06:55] <Hobbsee> bigon: i've never seen that happen before, and i cant find it having been reported before.
[06:56] <Hobbsee> bigon: it sounds like a bung script, and relies on $DEBIANDIR actually being defined.  is this always the case?
[06:56] <bigon> Hobbsee: with debian telepathy bzr branch
[06:57] <Hobbsee> bigon: er, that buggers up.
[06:57] <Hobbsee> sarah@LongPointyStick:/devel/network-manager/src$ dch
[06:57] <Hobbsee> dch: debian/changelog unmodified; exiting.
[06:57] <Hobbsee> sarah@LongPointyStick:/devel/network-manager/src$ dch --changelog $DEBIANDIR/changelog
[06:57] <Hobbsee> dch: fatal error at line 402:
[06:57] <Hobbsee> Cannot find /changelog!
[06:57] <Hobbsee> Are you in the correct directory?
[06:57] <Hobbsee> (You could use --create if you wish to create this file.)
[06:57] <bigon> mmm
[06:57] <Hobbsee> so i'd say your script is screwed, and you need a later version fo update-maintainer.
[06:57] <Hobbsee> but i'd also say that your fix is EB&W.
[06:59] <bigon> Hobbsee: http://www.pastebin.be/5377
[07:00] <ScottK> bigon: Move down one level in your source tree and try it again.
[07:01] <Hobbsee> bigon: probably because it's looking for debian/control, not just control.
[07:01] <Hobbsee> er, s/control/changelog/
[07:01] <Hobbsee> bigon: so if you call your debian dir something else, then yes, it will probably break
[07:02] <Hobbsee> fortunately, for all debian packaging, the debian dir is called debian/, so the fix is still EB&W.
[07:02] <bigon> ScottK: well the bzr branch only contains the debian files
[07:02] <proppy> ScottK: does the install.log generated by our packaging farm are ok to attach: http://farmpoker3d.pokersource.info/packaging-farm/html/index.php
[07:02] <ScottK> proppy: Looking.
[07:03] <Hobbsee> bigon: how does it determine $DEBIANDIR?
[07:03] <proppy> ScottK: there are ther result of the following command http://farmpoker3d.pokersource.info/d.txt
[07:03] <proppy> ScottK: +	  chroot ${ROOT} sh -c "apt-get update && apt-get install --yes --force-yes ${INSTALL_DEBIAN_PACKAGES}" ; \
[07:03] <proppy> ScottK: +	  echo 'deb file:///usr/src ./' >> ${ROOT}/etc/apt/sources.list && \
[07:03] <bigon> Hobbsee: http://www.pastebin.be/5378
[07:03] <proppy> before
[07:05] <ScottK> proppy: I don't find and install log in there.  Can you give a link to exactly what you propose to attach?
[07:05] <proppy> ScottK: yep sorry for that
[07:05] <proppy> ScottK: let me regenerate it
[07:06] <\sh> hmm...
[07:07] <\sh> does anybody has problems coming up with X ? since last update and rebooted the laptop now, I don't have an *DM starting up...and I don't see anything in the Xorg.0.log file stat X is starting
[07:07] <geser> bigon: try adding "-c $DEBIANDIR/changelog" to the dch call at the end of the script
[07:07] <bigon> geser: I'ts what I've done
[07:08] <\sh> and startx is doing nothing...
[07:08] <Hobbsee> bigon: working fine here.
[07:08] <Hobbsee> bigon: i think yours is botched somehow.
[07:08] <Hobbsee> as in, with a debian/ only checkout, named something else.
[07:08] <Hobbsee> sarah@LongPointyStick:/devel/kde3.5.7/kdenetwork/foo$ /usr/bin/update-maintainer
[07:08] <Hobbsee> Maintainer changed to Ubuntu Core Developers <ubuntu-devel-discuss@lists.ubuntu.com>.
[07:09] <proppy> ScottK: http://farmpoker.pokersource.info/nohup.out
[07:10] <Hobbsee> bigon: debian/changelog is hardcoded in dch anyway
[07:11] <bigon> Hobbsee: yep it's why I pass the exact path of the changelog
[07:11] <Hobbsee> bigon: but it doesnt wokr.
[07:11] <Hobbsee> it breaks functionality
[07:11] <ScottK> proppy: OK.
[07:12] <proppy> ScottK: let me attach it
[07:14] <proppy> ScottK: done
[07:14] <proppy> bug #140915
[07:14] <ubotu> Launchpad bug 140915 in poker-network "Please merge poker-network (1.2.0-1) from debian unstable main" [Undecided,New]  https://launchpad.net/bugs/140915
[07:15] <bigon> Hobbsee: bigon@imladris:/tmp/libtelepathy-0.0.57$ ls
[07:15] <bigon> aclocal.m4  ChangeLog  config.guess  config.sub  configure.ac  debian   INSTALL     libtelepathy.pc.in  m4           Makefile.in  NEWS    spec  tools
[07:15] <bigon> AUTHORS     compile    config.h.in   configure   COPYING       depcomp  install-sh  ltmain.sh           Makefile.am  missing      README  src   xml
[07:15] <bigon> bigon@imladris:/tmp/libtelepathy-0.0.57$ cd src/
[07:15] <bigon> bigon@imladris:/tmp/libtelepathy-0.0.57/src$ update-maintainer
[07:15] <bigon> Please execute /usr/bin/update-maintainer in the source folder.
[07:16] <Hobbsee> bigon: yes, i used straight dch -i.
[07:16] <Hobbsee> well, dch
[07:16] <Hobbsee> bigon: what i'm wondering - why dont you call it as a hook when you build?
[07:16] <Hobbsee> why manually run it at all?
[07:16] <Hobbsee> oh, i guess if you do actually upload to ppa's.
[07:19] <bigon> Hobbsee: I don't see the issue in adding the --changelog flag since you already need to run update-maintainer in the debian dir or in the top-level directory of the package
[07:20] <Hobbsee> bigon: hmm.  actually, i'm wondering why u-m doesnt use dch to detect where the changelog and such is.
[07:20] <jussi01> so anyone got an answer to my question?
[07:20] <Hobbsee> bigon: as long as you dont bugger dch :P
[07:23] <jussi01> Where Do i put the flags mentioned in this: http://paste.ubuntu-nl.org/37930/ (if you missed it earlier)
[07:23] <Hobbsee> jussi01: unless you were on crack, you didnt install to a random prefix (which would violate debian policy).  more likely you dont have gimp-dev, or similar, as a build-dep.
[07:24] <ScottK> jussi01: We don't have a pacakge named gimp-2.0
[07:24] <Hobbsee> or at least, that's the usual case
[07:25] <Hobbsee> jussi01: you'd need libgimp2.0-dev, at least
[07:25] <jussi01> Hobbsee: ok, must have been on crack, only had gimp in there...no dev or nothin...
[07:25] <jussi01> thanks
[07:25] <Hobbsee> jussi01: that'll do it :)
[07:25] <jussi01> :)
[07:26] <Hobbsee> jussi01: you tned to need the -dev packages for it to wokr.
[07:26] <jussi01> Hobbsee: yeah, I did know that. just well, its been a while since ive had time to package much
[07:26] <Hobbsee> otherwise it with kersplatteth, as you see.
[07:26] <Hobbsee> :)
[07:26] <jussi01> lol
[07:28] <jussi01> gah, was just about to thank her...
[07:28] <jussi01> :)
[07:33] <jussi01> Hmmm, next problem if someones got a min. what am I missing from my deps now? checking for XML::Parser... configure: error: XML::Parser perl module is required for intltool
[07:36] <pochu> jussi01: looks like libxml-parser-perl
[07:37] <jussi01> pochu: thanks...
[07:41] <ScottK> Funny how saying you fixed the bug in debian/changelog because you planned on doing it "in a minute" isn't enough to actually solve the problem....
[07:42] <jussi01> lol
[07:51] <ScottK> proppy: Ack'ed by me.
[07:53] <\sh> hmm...is there any search query for lp where I can find out which packages are in FTBS state?
[07:53] <ScottK> leonel: How goes clamav?
[07:54] <zul> \sh: look for ftbfs in the bug tracker?
[07:54] <\sh> zul, you mean tagged as "ftbfs"?
[07:54] <zul> yep
[07:55] <\sh> let's see
[07:55] <leonel> ScottK: Just Arriving in  30 minutes  I'll start over  to patch those 2 cves
[07:55] <ScottK> leonel: Great.
[07:56] <ScottK> zul: You up for looking at a UVFe?
[07:56] <zul> not til i get home
[07:56] <ScottK> OK
[07:57] <\sh> zul, that's not much
[08:01] <jussi01> could someone remind me of the correct syntax for closing a bug in the changelog file?
[08:01] <arthur-> jussi01: LP: #nnnn
[08:01] <arthur-> jussi01: and Closes: #nnnn in Debian
[08:02] <jussi01> arthur-: thanks
[08:10] <proppy> ScottK: thanks a lot
[08:10] <ScottK> No problem.  Thanks for minding the Ubuntu version of the package.
[08:12] <proppy> ScottK: What is the next thing I should do ?
[08:13] <ScottK> proppy: Now the thing is for one of the other motu-uvf members to ack/approve it.
[08:13] <ScottK> So, wait would be the answer to your question.
[08:13] <proppy> ScottK: thanks a lot for clearing this up :)
[08:22] <proppy> bye
[09:09] <zorg_the_false> q. im trying to create a repository, and i got it working with dpkg-scanpackages. but it creates a warning in the user. because it is not signed. anybody know where i could find info on how to generate the files needed to remove this warning
[09:10] <zorg_the_false> like which files are needed for the repository to be authenticated. where can i find documentation about this ?
[09:10] <zul> zorg_the_false: why not use ppa
[09:11] <zorg_the_false> because i need to build my own repository :)
[09:31] <zorg_the_false> zul: i found it :)
[09:31] <zorg_the_false> apt-ftparchive -c apt-release.conf release . <- to generate the Release file
[09:31] <zorg_the_false> gpg --yes -abs -o Release.gpg Release <- to sign it :)
[10:44] <leonel> when should I report a bug as public ?
[10:44] <leonel> ScottK: clamav patches  done   clamav-milter needs testing
[10:44] <ogra> always unlessits a big security breakage or has confidential data from you
[10:45] <leonel> making it public
[10:45] <leonel> it's been public in debian
[11:34] <ScottK> leonel: Great.  Public was the right answer as the vulnerabilty has already been disclosed.
[11:35] <ScottK> keescook: Could you please have a look at Bug 141073.  As leonel has said the clamav-milter patch is untested, but none of us use it so ...
[11:35] <ubotu> Launchpad bug 141073 in clamav "Remote DoS and Remote execution" [Undecided,New]  https://launchpad.net/bugs/141073
[11:54] <gnomefreak> does anyone know where to set dpi at? seems mine is way too small from clean upgrade from feisty (clean == base install nothing added)
[11:54] <gnomefreak> i dont have a setting in xorg.conf
[11:55] <gnomefreak> i see font paths but no real setting for system wide dpi
[11:55] <gnomefreak> 126x121 dots per inch should be closer to 96 97
[11:55] <gnomefreak> maybe even 100
[11:56] <gnomefreak> i cant find the bug that was first reported but if its set fix released either it wasnt fixed or it was messed with again :(
[12:00] <_MMA_> gnomefreak: If it related to fonts its in Fonts->Details. (button at the bottom)
[12:01] <gnomefreak> ok looking ty
[12:01] <gnomefreak> wait i dont have that in xorg.conf
[12:01] <gnomefreak> so im assuming you mean apppearance
[12:01] <_MMA_> Yeah.
[12:01] <_MMA_> I forgot we lost the Font menu. :)
[12:01] <gnomefreak> its set to 96 :(
[12:01] <_MMA_> hmm...
[12:02] <gnomefreak> why is my res showing the numbers above
[12:02] <gnomefreak> xdpyinfo | less shows dimensions:    1600x1200 pixels (323x252 millimeters) resolution:    126x121 dots per inch
[12:03] <gnomefreak> all the fonts are set to 10 is that correct? seems a bit low
[12:03] <_MMA_> I messed with mine.
[12:03] <_MMA_> (font size that is)
[12:04] <gnomefreak> i just bumped them to 12
[12:04] <_MMA_> Maybe reconfigure xorg?
[12:04] <_MMA_> After an update my terminal font was borked but a logout/in fixed it.
[12:05] <gnomefreak> looks better but now kind of ugly maybe i just need to screw around with the settings but i would think this needs to be fixed if im not the only person
[12:30] <ajmitch> soren: how would you feel about a UVFe for a package whose diffstat is like:
[12:30] <ajmitch>  215 files changed, 3798 insertions(+), 1181 deletions(-)
[12:30] <ajmitch> just a small python checker (pylint) :)
[12:32] <ajmitch> this is mainly for kiko, he says that the current version in gutsy really doesn't work too well for what they need
[12:36] <leonel> anyone knows if feisty will have a  postgresql  update  ?
[12:37] <leonel> yesterday was   released  8.2.5