[12:55] <nixternal> StevenK: did you check out krename merge the othernight? bug 112528
[12:55] <ubotu> Launchpad bug 112528 in krename "[Gutsy Merge]  krename_3.0.14-0ubuntu1" [Undecided,Unconfirmed]  https://launchpad.net/bugs/112528
[12:55] <nixternal> getting that merged will close 2 bugs for krename
[12:55] <nixternal> brb
[12:57] <Acksys> I'd like to get set up with a mentor.
[12:57] <Acksys> What's the best way?
[01:51] <etank> what is the process of getting teamed with a mentor?
[01:54] <gnomefreak> etank: talk to the person offering the mentoring maybe. i guess it depends on what you want mentoring in and who is willing to help in that
[01:55] <etank> gnomefreak: ok.
[02:20] <wolfeon> oh damn it :/
[02:20] <wolfeon> keep forgetting to submit my patches :)
[02:20] <wolfeon> "send patches or stfu" :D
[02:48] <TheMuso> Hey MOTUs and MOTU hopefuls.
[02:48] <Simon80> hi Dr. Nick!
[02:48] <RAOF> Hey TheMuso
[02:49] <Simon80> I'm just being random
[03:02] <paran> is feisty-backport not opened yet?
[03:02] <nxvl> hi
[03:03] <nxvl> i want to help, and be part of the MOTU
[03:03] <nxvl> i have read the web
[03:03] <RAOF> nxvl: Excellent!  How do you want to help?
[03:03] <nxvl> and write to sistpoty but i don't have any answer yet
[03:04] <paran> If I look in launchpad it seems like ktorrent have been backported to feisty, but there is nothing in the archives.
[03:04] <nxvl> RAOF: i will like to help with ruby, wich is the lenguage with i feel more comfortable
[03:04] <j-dizzle> paran: it's open... I'm on break while exam season's here....
[03:04] <j-dizzle> paran: and infinity said he'd fix the backports build problem for ktorrent.....
[03:04] <j-dizzle> "this morning"
[03:04] <j-dizzle> where this morning was 3 days ago
[03:04] <nxvl> RAOF: and as i read it seems to need lot of help
[03:04] <j-dizzle> so umm.... yeah.....
[03:05] <RAOF> nxvl: And you want to help by... fixing bugs in ruby packages?  Packaging new ruby programs?
[03:05] <paran> j-dizzle: lol
[03:05] <nxvl> RAOF: yes, packaging, reporting bugs, maybe fixing
[03:05] <nxvl> im not a ruby expert
[03:05] <nxvl> but i will learn
[03:06] <j-dizzle> paran: all the devs are at their conference thing, so it's been an odd week :)
[03:06] <RAOF> Right, so reporting bugs you can do right now, to launchpad.net :)
[03:06] <j-dizzle> not to mention I'm supposed to be learning how curl and stokes theorem works....
[03:06] <nxvl> RAOF: that i know ;)
[03:06] <bddebian> Heya gang
[03:07] <paran> j-dizzle: there is no rush for me, I have backported it myself with some extra patches from SVN. was only wondering why it wasn't in archives
[03:07] <RAOF> hey bddebian
[03:07] <bddebian> Hello RAOF
[03:07] <nxvl> RAOF: but i want to make packages, and try to fix bugs
[03:07] <j-dizzle> paran: ok; "mystery buildd magic" I guess is the official explanation.
[03:07] <j-dizzle> paran: I have some personal conspiracy theories... but I'd rather not share them :D
[03:07] <j-dizzle> haha
[03:07] <RAOF> nxvl: Ok.  Have you read the packaging guide?  That's how I learnt to build debian/ubuntu packages.
[03:08] <harrisony> nxvl,  https://wiki.ubuntu.com/MOTU/Teams/Ruby sounds good for you :)
[03:08] <paran> j-dizzle: exam periods is a rather good excuse for you not working
[03:08] <paran> j-dizzle: although I seem to spend _more_ time on things unrelated to studies when I have those.. :)
[03:08] <j-dizzle> paran: I'm trying to prevent the same from ahppening here :D
[03:09] <j-dizzle> I'm pretty sure I bombed my calc test this morning :)
[03:09] <j-dizzle> I'm awaiting the "you've failed, you miserable piece of garbage" e-mail... :D
[03:09] <paran> calc as in calculus?
[03:09] <nxvl> RAOF: im reading
[03:09] <j-dizzle> yep
[03:09] <j-dizzle> 18.02, multivariable calc
[03:09] <nxvl> harrisony: thnx
[03:10] <harrisony> nxvl, can i have a link to your launchpad profile?
[03:11] <nxvl> harrisony: https://launchpad.net/~nvalcarcel
[03:12] <nxvl> harrisony: i haven't use it very much
[03:12] <harrisony> nxvl, have you been told about REVU?
[03:12] <paran> j-dizzle: ah, I know that feeling. I also have a failed multivar course that I will pass any year now
[03:13] <nxvl> harrisony: nop
[03:13] <j-dizzle> well... 2 weeks left to go
[03:13] <j-dizzle> then my first term at the suicide mansion will come to an end :)
[03:13] <harrisony> !revu > nxvl
[03:13] <harrisony> the bot will pm you
[03:16] <nxvl> im reading
[03:16] <nxvl> well, first i need to know how to make packages
[03:16] <nxvl> :D
[03:20] <harrisony> yep also check out https://wiki.ubuntu.com/UbuntuOpenWeek have a look at the package sessions and MOTU related sessions logs as they are quite good
[03:21] <minghua> !packagingguide > nxvl
[03:30] <_MMA_> Hi all. Ubuntu Studio 7.04 has been released. http://ubuntustudio.org Thanx to everyone. :)
[03:31] <bddebian> Is it just me or do we have people coming out of the woodwork lately? :)
[03:32] <Acksys> What is the best way to get hooked up with a mentor?
[03:34] <bddebian> Acksys: https://wiki.ubuntu.com/MOTU/Mentors
[03:35] <Acksys> Do I need to pick one that reflects the area in which I'd like to contribute? Because I'm not sure about that yet.
[03:35] <bddebian> Nope.  In fact you don't "have" to have one.  You are welcome to ask questions here.
[03:36] <Acksys> Well, I have some programming experience, but no experience in a real development environment.
[03:36] <bddebian> RAOF: And it shows. ;-P
[03:36] <Acksys> So I'm at somewhat of a loss about where to begin.
[03:36] <minghua> ubuntustudio has a nice looking website
[03:36] <bddebian> RAOF: j/k
[03:36] <RAOF> bddebian: :P
[03:36] <bddebian> Acksys: Do you have any specific areas of interest?
[03:36] <RAOF> bddebian: Only in stupid things like assigning bugs to u-u-s & u-m-s
[03:37] <_MMA_> minghua: Thanx
[03:37] <Acksys> My major is graphic communications.. that's a print management major, so I'm interested in graphics
[03:37] <Acksys> and music as well
[03:38] <bddebian> Acksys: Look for some bugs in music or graphics packages and fix them. :-)
[03:39] <Acksys> bddebian: You make it sound easy.
[03:39] <Acksys> I'll give it a shot.
[03:39] <_MMA_> ;)
[03:40] <RAOF> https://launchpad.net/ubuntu/+bugs?field.tag=bitesize is a list of bugs marked as "bitesized" ie: should be quick/easy to fix.
[03:40] <Acksys> ah, ok
[03:41] <RAOF> It might be good to start there, since most of the work involved in fixing those (should) be in the learning of the various processes :)
[03:42] <Acksys> RAOF: That looks like a good place to start, thanks for the info.
[03:43] <nxvl> i have send mi first patch
[03:43] <nxvl> :D
[03:58] <chillywilly> um, so the only way to do a desktop install via the desktop feisty iso is to boot into a full desktop?
[03:58] <chillywilly> and double click on the "install" icon
[03:58] <minghua> chillywilly: check out alternative install CD
[03:58] <chillywilly> it's just kinda weird if you ask me
[03:59] <bddebian> chillywilly: Oh hush up and go back to your rbuild or whatever the fsck it's called. ;-P
[03:59] <chillywilly> I hadn't downloaded and burnt that one
[04:00] <chillywilly> anaconda is a nice installer and customizable via python :)
[04:00] <persia> chillywilly: If you *really* want, you can manually partition and debootstrap using the pool directory on the regular CD, but it won't be very friendly.
[04:00] <harrisony> anaconda is used by fedora
[04:00] <chillywilly> but no I am building a distro using rPath linux appliance platform for the record ;P
[04:16] <_MMA_> chillywilly: Why aren't you on: #rpath #rpath-support #foresight or #conary. Those are the places you should ask.
[04:17] <chillywilly> I am on #conary
[04:17] <chillywilly> ask what?
[04:18] <chillywilly> I didn't ask anything here :)\
[05:13] <persia> Could someone please advise me as to how to automatically generate -dbgsym packages with sbuild?
[05:14] <minghua> persia: the dh_strip(1) man page (assuming you have a debhelper >= 5)
[05:15] <persia> minghua: Thanks.  Now to complicate things, I need to override for CDBS :)
[05:17] <persia> minghua: Thanks a lot.  You've pointed me in the right direction.  I just need to install pkg-create-dbgsym in the chroot.
[05:19] <freeflying> minghua: will you merge scim into gutsy?
[05:20] <minghua> freeflying: not now, don't have time
[05:20] <minghua> persia: Hmm, I didn't know about pkg-create-dbgsym.  Is that a package name?
[05:20] <freeflying> minghua: ok, I've done
[05:21] <minghua> freeflying: sure, thanks
[05:21] <RAOF> It's what the buildds use to automatically create the foo-dbgsym packages for everything, right?
[05:21] <RAOF> (The package, I mean)
[05:21] <persia> minghua: Yep.  It diverts dh_strip to always generate -dbgsym packages.  Handy for local testing.
[05:22] <freeflying> imbrandon: ping
[05:32] <minghua> persia: I see.  I also found out it's an Ubuntu-only package.  No wonder I haven't heard of it before.
[05:33] <persia> minghua: I think it's fairly new too (perhaps six months old, or so?)
[05:35] <minghua> persia: launchpad says it has existed since edgy
[05:35] <minghua> 2006-07-04 first upload, acutally
[05:35] <minghua> so yes, fairly new
[05:36] <persia> minghua: Ah - almost a year old.  My apologies for misremembering.
[05:37] <dabaR> persia: did you get a response on where to file a bug on the ubuntu web site?
[05:38] <persia> dabaR: For the ubuntu website, I have an answer, but I haven't really followed up on where to file a bug about the behaviour of patches.ubuntu.com (which might be Soyuz?  I'm not sure).
[05:39] <dabaR> persia: I would personally file it against the ubuntu web site, but you're right, that may be wrong.
[05:42] <persia> dabaR: Just yesterday I had what I thought was a Malone bug turn out to be a duplicate of a Soyuz bug, so I want to avoid causing more extra work for the triagers.  It's only wishlist anyway (preserve last three ubuntu patches, for convenience of packages.qa.debian.org, instead of only the lastest patch; alternately, provide a symlink "latest" in each directory for link convenience).
[05:57] <dabaR> sharms: Do you know that both the  Archive and the About links on your blog are broken?
[06:57] <StevenK> nixternal: Hrm? What about krename?
[06:58] <nixternal> just wondering if you had looked at it for the merge previously? I think last time talking about getting it into Debian threw it off
[06:58] <nixternal> I still haven't received contact back from the maintainer
[06:58] <StevenK> How long has it been?
[06:59] <nixternal> Saturday
[06:59] <StevenK> Hrm. I'd give it a little longer.
[08:09] <ceros> i'm trying to upload my packages again
[08:09] <ceros> dput -f isn't working for me
[08:10] <RAOF> You've changed ~/dput.conf so that revu is the default server?
[08:10] <ceros> yes
[08:12] <RAOF> And you've added yourself to the revu team, and the revu keyring has been sync'd?
[08:12] <persia> StevenK: Thank you.
[08:13] <ceros> i don't know if the keyring has been synced
[08:14] <RAOF> How long ago did you add yourself to the team?
[08:14] <persia> ceros: As far as I know, last sync was about 18 hours ago.
[08:14] <ceros> about 2 or 3 days ago
[08:16] <bluefoxicy> when something has a Replaces: foo
[08:16] <RAOF> And what exactly isn't working/what errors are given?
[08:16] <bluefoxicy> and I try to install a .deb and it goes "Cannot satisfy dependency:  foo"
[08:16] <bluefoxicy> what does that mean?
[08:16] <ceros> Error '553 Could not create file.' during ftp transfer of sauerbraten_0.0.20070413-0ubuntu1.dsc
[08:17] <bluefoxicy> assuming I have the first thing installed already.
[08:17] <bluefoxicy> Does it mean the dependency checking code is horribly broken?
[08:17] <ceros> i'm trying to upload again since my last attempt errored out
[08:17] <ceros> when it was about to upload the changes file
[08:17] <RAOF> ceros: It's possible that you've got some files from your previous attempt blocking the new files.
[08:18] <ceros> i can't force it to upload again?
[08:18] <RAOF> No, you need to prod a REVU admin.
[08:18] <RAOF> Who can look at incoming, and delete stuff or whatever
[08:20] <persia> bluefoxicy: Replaces: means that the package is allowed to share filenames with the replaced package.  It should generally only be used where multiple binaries are built from the same source, and some files moved,  or there is a transition (in which case it should Conflicts: as well).  For either case, it may well depend on some version of the replaced pacakge to ensure the user is never without the affected file.
[08:21] <RAOF> I forget who the actual admins are, though.  crimsun is, I think.
[08:22] <minghua> bluefoxicy: do you have a versioned Replaces?
[08:22] <RAOF> ceros: Bah, silly me.  wiki.ubuntu.com/MOTU/Packages/REVU
[08:24] <RAOF> ceros: that page says admins are siretart, sistpoty, ajmitch, raphink.
[08:24] <ceros> ok
[08:24] <bluefoxicy> minghua:  no, it just seems gdebi doesn't like libusplash-dev instead of usplash-dev
[08:24] <harrisony> RAOF, you live in australia?
[08:24] <RAOF> harrisony: Yup, Sydney.
[08:24] <bluefoxicy> minghua: but libusplash-dev Replaces usplash-dev
[08:24] <bluefoxicy> it won't satisfy dependencies though.
[08:25] <harrisony> RAOF, how come i dont see you in #ubuntu-au , what suburb in sydney?
[08:25] <persia> bluefoxicy: If they were the same, libusplash-dev would need to Provides: usplash-dev.  Wait a while, and it will become more stable.
[08:26] <RAOF> harrisony: Because if I joined every relevant IRC channel, I wouldn't get even what little work I do get done done :)
[08:26] <harrisony> haha
[08:29] <minghua> bluefoxicy: that's correct behavior
[08:29] <minghua> bluefoxicy: Replaces has nothing to do with satisfying dependency, it's Provides' job.
[08:31] <bluefoxicy> ok
[08:31] <bluefoxicy> then the other package is broken
[08:32] <minghua> okay, next time I should read all conversations before repeating what persia said...
[08:32] <persia> minghua: No, your phrasing is easier to understand :)
[08:47] <minghua> persia: :-)
[08:47] <minghua> not exactly all CJK bugs
[08:47] <minghua> I'm just subscribed to bugmail of all scim related packages, and triage them on a best-of-effort basis
[08:48] <persia> minghua: No, but I'll at least concentrate on fixes, rather than grabbing easy "gutsy isn't ready yet" bugs :)
[08:48] <minghua> persia: yeah, sounds a good idea
[08:49] <minghua> persia: you can spend you time working on the code, and let me do the commenting work :-)
[08:49] <persia> minghua: :)
[08:49] <minghua> persia: as I don't have a gutsy system right now, doing really packaging is a little problematic
[08:49] <persia> minghua: vm?  chroot?
[08:50] <minghua> chroot is not exactly convenient for testing input method stuff
[08:50] <minghua> it usually requires a working X
[08:51] <minghua> as for VM, I've never played with one
[08:51] <RAOF> I've recently set up a gusty VM with KVM, that was pretty easy.
[08:51] <minghua> I suppose I can update my feisty pbuilder chroot and do some test building stuff
[08:52] <minghua> but I only want to upload stuff I'm very confident of this way if that's all my testing
[08:53] <persia> minghua: For chroot, run the X server on a different vterm.  Of course, when gutsy crashes, feisty might :).  For VM, try vmware-player and http://www.vmware.com/vmtn/vm/ubuntu.html.  There's an ubuntu.org link too, but I can't find it right now.
[08:53] <minghua> my problem is, trying to keep an up-to-date development system with both GNOME and KDE installed is a bit taxing to my DSL line
[08:54] <Treenaks> minghua: get a better internet connection :)
[08:54] <minghua> persia: my main system is sid, not feisty :-)
[08:54] <persia> minghua: In that case, you'd do better to wait until later.
[08:54] <minghua> yeah I know how to set a chroot with X
[08:54] <persia> minghua: sid?  My sid VM is less stable than my gutsy VM, but perhaps that's just me.
[08:55] <minghua> but things are always a bit iffy and I don't want to mess with my good sid system
[08:55] <minghua> I think it depends on what "stable" means
[08:56] <Treenaks> it's our Burger King! :)
[08:56] <minghua> I am quite confident on the kernel and basic stuff in sid
[08:56] <minghua> although I've been experiencing an OO.o bug and a video driver bug recently
[08:56] <persia> minghua: Stability is king.  That's why I like using VMs, but I don't know that vmware-player works on sid.  In reference to "stable": I am currently les surprised by changes to gutsy than to sid.  I expect this to change next week, after UDS.
[08:56] <Treenaks> persia: kvm should work on sid
[08:57] <Treenaks>  kvm
[08:57] <minghua> persia: yeah, sid is rather turbulent right now
[08:57] <persia> Treenaks: Doesn't kvm have processor requirements?
[08:57] <Treenaks> persia: oh... yeah..
[08:57] <Treenaks> persia: it needs intel vt or amd-v
[08:57] <RAOF> Surely everyone has a <1 yr old Intel or AMD chip :P
[08:58] <Treenaks> RAOF: ;)
[08:58] <minghua> Treenaks: apparently not a choice for my AMD K6 CPU then :-)
[08:58] <persia> RAOF: No.  My main computers are XScale 624 and Athlon X2 4400+.
[08:58] <RAOF> Old school!
[08:58] <RAOF> persia: The X2 supports kvm, doesn't it?
[08:58] <Treenaks> minghua: xen?
[08:58] <persia> RAOF: Not the first batch off the ship.  A newer one might.
[08:58] <minghua> maybe vserver, I think
[08:59] <minghua> or vmware stuff
[08:59] <minghua> although my priority is taking care of my Debian package now
[09:00] <minghua> so sid system is good enough :-P
[09:16] <ajmitch> morning
[09:16] <geser> morning ajmitch
[09:22] <sorsis> /lastlog sorsis
[09:58] <BugMaN> hi all
[10:20] <persia> If I upload a foo-1.2-0ubuntu1 revision, and Debian later publishes a foo1.2-1 version, is a sync possible so long as the same orig.tar.gz is in use?
[10:21] <crimsun> yes.
[10:21] <persia> crimsun: Thanks.
[10:22] <crimsun> cf. galago-python, galago-gtk-python recently (this devel cycle).
[10:22] <crimsun> err, was that versioning you used intentional?
[10:23] <crimsun> (I presumed you meant foo_1.2-0ubuntu1 and foo_1.2-1)
[10:23] <persia> crimsun: No, there was a typo - it should have been as you typed.  I somehow managed to commit my comment whilst still composing :)
[10:24] <crimsun> ah, I've been a victim of that, too.
[10:26] <minghua> persia: did you really mean foo-1.2 and foo1.2?
[10:26] <minghua> persia: i.e., the difference of a hyphen in the package name?
[10:26] <persia> minghua: Not at all.  I really meant foo_1.2-0ubuntu1 and foo_1.2-1
[10:28] <freeflying> crimsun: arounds
[10:28] <crimsun> freeflying: hi
[10:28] <freeflying> crimsun: would you likde sponsor uplad
[10:29] <crimsun> freeflying: sure, url?
[10:29] <freeflying> crimsun: a momnet plz
[10:31] <freeflying> crimsun: or I mail u
[10:31] <crimsun> freeflying: I'm on a very slow connection now, so a URL is probably best
[10:33] <freeflying> crimsun: http://<IP_ADDRESS>:~/freeflying/scim/scim_1.4.6-1ubuntu1.dsc
[10:34] <freeflying> crimsun: http://<IP_ADDRESS>~/freeflying/scim/scim_1.4.6-1ubuntu1.dsc
[10:35] <freeflying> crimsun: can you access to it
[10:47] <crimsun> freeflying: testing
[10:47] <crimsun> freeflying: yes
[10:48] <freeflying> crimsun: all others package has build-dep on it need rebuild against it, or they can not work
[10:49] <crimsun> freeflying: ok, can you link me to the diff.gz?
[10:50] <freeflying> crimsun: http://<IP_ADDRESS>~/freeflying/scim/scim_1.4.6-1ubuntu1.diff.gz
[10:50] <crimsun> freeflying: did you work with minghua on this merge?
[10:51] <freeflying> crimsun: minghua said he hasn't time now for merge, so I did
[10:51] <crimsun> freeflying: ok.  And you've tested it?
[10:51] <minghua> crimsun: yeah, he asked earlier today, I told him to go ahead
[10:51] <freeflying> crimsun: sure, I'm using it now
[10:51] <crimsun> minghua: ok.
[10:51] <crimsun> freeflying: thanks.
[10:52] <crimsun> all right, grabbing orig.tar.gz
[10:52] <freeflying> debian's powerpc builld dosen't work now, I can not close the bug of skim now
[10:56] <crimsun> err, the previous Ubuntu changelog entries are missing from debian/changelog
[10:58] <TheMuso> c
[10:58] <TheMuso> ugh
[10:58] <TheMuso> evening folks.
[10:58] <crimsun> freeflying: would you readd the missing previous Ubuntu changelog entries, please?
[10:58] <crimsun> hi TheMuso
[10:59] <freeflying> crimsun: ok
[11:01] <persia> good evening TheMuso.
[11:05] <elkbuntu> oi you. who keeps signing me up for stuff
[11:06] <crimsun> I hear a certain Melissa would like to join the ubuntu-audio LP team...
[11:06] <jmg> lp?
[11:06] <crimsun> jmg: Launchpad
[11:06] <jmg> notice there is a melissa at google
[11:07] <jmg> all the same :)
[11:07] <crimsun> I was referring to "elkbuntu" Melissa
[11:07] <jmg> elkbuntu: greetings
[11:08] <elkbuntu> hi jmg
[11:08] <elkbuntu> crimsun, i'm thinking it's mr mitchell
[11:09] <crimsun> hmm!
[11:09] <elkbuntu> crimsun, i somehow was signed up to a motu session the first day
[11:09] <elkbuntu> crimsun, now this
[11:10] <elkbuntu> and goodness knows how many else i havent noticed through the week
[11:10] <freeflying> crimsun: done
[11:11] <crimsun> freeflying: new URLs?
[11:11] <freeflying> crimsun: same as above
[11:13] <persia> Is it a Debian bug is a Build-Depends is not specified that causes a build failure for Ubuntu (where the Debian package built successfully)?
[11:13] <StevenK> persia: Curious. Which package, and which package is missing?
[11:14] <persia> StevenK: aqsis and libtiff (or, probably, really libtiffxx0).
[11:14] <ajmitch> elkbuntu: yes?
[11:15] <StevenK> Perhaps one of the Build-Depends in Debian pulls in the tiff libraries?
[11:15] <StevenK> And doesn't on Ubuntu.
[11:15] <ajmitch> elkbuntu: I told you I don't subscribe you to specs
[11:15] <StevenK> persia: I saw your removal bug, and dealt with it.
[11:15] <elkbuntu> ajmitch, then wtf is happening? you and hobbsee were plotting evil things before we came here :
[11:15] <ajmitch> I'm evil, not mean
[11:16] <elkbuntu> ajmitch, ah, so it must be hobbsee then
[11:16] <elkbuntu> is she in the same session as you at the moment?
[11:16] <ajmitch> nope
[11:16] <persia> StevenK: For wstools?  Thanks.  Only 5 packages to go :)
[11:16] <StevenK> Heh
[11:16] <crimsun> freeflying: uploaded.
[11:16] <freeflying> crimsun: thanks
[11:17] <elkbuntu> hmm, i wonder where she is then
[11:17] <ajmitch> well I'm in a mdadm/lvm/evms session
[11:17] <ajmitch> which I doubt she's interested in
[11:19] <minghua> persia: according to aqsis's debian build log (http://buildd.debian.org/pkg.cgi?pkg=aqsis), Debian uses libtiffxx0c2
[11:20] <TheMuso> I see no schedule for today
[11:20] <StevenK> TheMuso: It's there, just not linked to.
[11:20] <persia> minghua: Ubuntu does as well - I just saw "TIFF C++ bindings" when first commenting.
[11:20] <TheMuso> gotcha
[11:20] <StevenK> TheMuso: You have no idea how much self-control that took. :-P
[11:22] <minghua> persia: okay.  in Debian libtiffxx0c2 is pulled in by libtiff4-dev
[11:22] <TheMuso> early finish today
[11:22] <StevenK> There's a big dinner on, isn't there?
[11:23] <ajmitch> StevenK: yep, around 7:30 tonight
[11:26] <StevenK> minghua: In Ubuntu as well.
[11:26] <crimsun> aka the big ole dinner in which everyone eats way too much and gets drunk
[11:26] <ajmitch> and then the later evening when people get even drunker
[11:27] <ajmitch> except that many have a flight at about 6:30 AM
[11:28] <StevenK> ajmitch: Like yourself?
[11:28] <persia> minghua: Interestingly enough, yellow pulled all of libtiff4, libtiff4-dev, and libtiffxx0c2 before trying to compile.  I'm suspicious of scons for this one.
[11:28] <ajmitch> nah, my flight is after lunch
[11:28] <minghua> persia: ah, scons
[11:29] <minghua> persia: I met a mysterious FTBFS related to scons in Debian as well a few days ago
[11:30] <persia> minghua: rumor has it that scons packages build correctly until uploaded to production :)
[11:30] <StevenK> persia: Sounds about right.
[11:30] <StevenK> persia: scons ought to be avoided.
[11:31] <minghua> the only thing I know about scons is its colorful output :-)
[11:31] <persia> StevenK: I agree, but Upstream does as Upstream wills.  I'm not sure I want to maintain a backport to autoconf ;)
[11:31] <StevenK> persia: Actually, I'd find it amusing if a package Build-Depends on scons and Build-Conflicts on scons because it's so horrid.
[11:32] <persia> StevenK: Amusing yes, but surely a sufficient bug not to be tolerated (although I am tempted)
[11:33] <crimsun> hah, I really misinterpreted that.  I thought you were saying that autoconf build-depends on scons.
[11:33] <StevenK> Twitch
[11:34] <crimsun> that would be quite tragic/humourous.
[11:34] <persia> crimsun: That would be a feature :)
[11:34] <Treenaks> that would make little baby bunnies cry
[11:34] <Treenaks> a lot of them
[11:34] <Treenaks> at the same time
[11:35] <gnomefreak> how do i sign into revu to reply to a comment?
[11:35] <persia> gnomefreak: "recover" the password you were probably never sent of the email address on the registered key.
[11:35] <elkbuntu> announcement: amaranth just got kicked out of the hotel room by the maid
[11:35] <gnomefreak> persia: i tried that but it gave me None and it doesnt work
[11:35] <elkbuntu> that is all. i must now go rofl
[11:36] <crimsun> elkbuntu: just what  /was/  he doing in that hotel room...
[11:36] <Treenaks> elkbuntu: so.. he's sitting on the floor, naked?
[11:36] <Treenaks> elkbuntu: just outside the room
[11:36] <elkbuntu> he's walking around now, ask him
[11:36] <Treenaks> elkbuntu: *BAD MENTAL IMAGE*
[11:37] <persia> gnomefreak: Sorry, that's what I did.  Perhaps someone with more REVU experience could help?
[11:37] <Hobbsee> gnomefreak: on the main page
[11:37] <gnomefreak> when i click recover it gives me a couple of lines
[11:38] <gnomefreak> to decrypt ..... than > gpg command   than now paste the lines below ... no lines are there
[11:38] <elkbuntu> Treenaks, do you think i'm IRCing from above a porcelain bowl or something?
[11:38] <gnomefreak><EMAIL_ADDRESS>[11:39] <persia> gnomefreak: You need an admin.
[11:39] <gnomefreak> :(
[11:40] <Treenaks> elkbuntu: maybe
[11:40] <gnomefreak> also why would a build fail in pbuilder and not with dpkg-buildpackage  (patch failing in pbuilder)
[11:42] <persia> gnomefreak: That can happen if your source tree was dirty before dpkg-buildpackage, or if your Build-Depends are insufficiently satisfied (for your patch system), or lastly, if you are patching after the autoconf fun, and need to patch configure.ac or configure.in (or similar for other build systems).
[11:42] <crimsun> magic patch?
[11:42] <crimsun> gnomefreak: have you uploaded a package to revu?
[11:43] <gnomefreak> yes
[11:43] <gnomefreak> http://revu.tauware.de/details.py?upid=5092
[11:43] <gnomefreak> it builds fine here without pbuilder ;)
[11:45] <ajmitch> I'm used to that, thanks for your helpful input
[11:45] <Hobbsee> :)
[11:51] <persia> Does anyone know whether Soyuz uses chroot or schroot for the sbuild processes?
[11:52] <pochu> persia: I would ask that in #launchpad ;)
[11:53] <persia> pochu: Oh well.  Thanks.
[11:55] <joejaxx> Good Morning Everyone
[11:55] <pochu> hi joejaxx
[11:56] <joejaxx> hello pochu :)
[12:02] <gnomefreak> hmmmmmmm
[12:05] <gnomefreak> brb something is off here
[12:05] <TheMuso> persia: schroot and sbuild are rather tied together, so I'd say schroot.
[12:07] <persia> TheMuso: The man page for sbuild-setup makes lots of references to buildd.chroot, which makes me unsure.  I wouldn't be surprised if dchroot was the mechanism of preference.
[12:09] <TheMuso> Heya imbrandon.
[12:09] <Hobbsee> StevenK: do you remember how to use requestsync for gutsy, when running feisty?
[12:10] <gnomefreak> crimsun: this is due to something that was updated in gutsy because before today (for me) it built fine.
[12:10] <shawarma> Hobbsee: eh? You specify the distro on the command line?
[12:10] <gnomefreak> and if you go through and # out in 00list you will end up with no patches
[12:11] <gnomefreak> i tried in 2 gutsy chroots and a gutsy main sys.
[12:11] <Hobbsee> shawarma: says i dont have gutsy in apt-cache madison
[12:11] <Hobbsee> although i do have the source version
[12:12] <pochu> mr_pouit: around? I'm packaging scribes for Debian (since the packager i revu doesn't intend to do it), and I saw you said the .svgs have a CC license. Where have you read it? :)
[12:12] <shawarma> Hobbsee: Oh, really? Ah, yes, that makes sense.
[12:12] <shawarma> Hobbsee: You can just specify the base version?
[12:12] <shawarma> Hobbsee: As the last argument.
[12:13] <shawarma> Hobbsee: forget it.
[12:13] <shawarma> Hobbsee: I'm on crack.
[12:14] <persia> Hobbsee: change your sources, update (don't upgrade), requestsync, fix your source, update?   (sed --in-place s/feisty/gusty/ & reverse)
[12:14] <minghua> sounds painful
[12:15] <minghua> maybe add gutsy and pin it down is a better idea
[12:15] <shawarma> Hobbsee: apt-cache madison actually lists it, but requestsync fails to get it?
[12:19] <Hobbsee> shawarma: it lists the feisty version
[12:19] <Hobbsee> well...
[12:19] <Hobbsee> sarah@LongPointyStick:~/Desktop$ madison fillets-ng
[12:19] <Hobbsee> fillets-ng |    0.7.3-3 | http://archive.ubuntu.com feisty/universe Packages
[12:19] <Hobbsee> fillets-ng |    0.7.3-3 | http://archive.ubuntu.com gutsy/universe Sources
[12:19] <Hobbsee> shawarma: ^ is what i get
[12:21] <Hobbsee> shawarma: yes, i can, but that doesnt list the changes between the base version, and the latest, as the latest is in experimental...
[12:23] <gnomefreak> is there a way to find out what was upgraded in last 24 hours?
[12:23] <geser> on your system?
[12:23] <gnomefreak> yeah
[12:23] <gnomefreak> or chroot
[12:24] <geser> /var/log/dpkg.log
[12:24] <Treenaks> /var/log/dpkg.log
[12:24] <gnomefreak> i remember binutils
[12:24] <gnomefreak> ty
[12:26] <ubotu> Launchpad bug 113870 in octave2.1-forge "feisty, package octave-forge2.1: missing sparse.oct" [Undecided,Confirmed]  https://launchpad.net/bugs/113870
[12:27] <StevenK> Hobbsee: That looks fine.
[12:27] <StevenK> In fact, I get the same output.
[12:31] <imbrandon> wow one little digg and you can satuate a 100MB/s connection heheh http://www.imbrandon.com/misc/bandwidth/current.jpg
[12:31] <Hobbsee> oh wiat, it worked.
[12:32] <minghua> imbrandon: how did you end up on digg?
[12:33] <imbrandon> ubuntustudio release ( i have a mirror )
[12:37] <mr_pouit> pochu: I can't remember exactly, but I think I made 'grep -Ri copyright *' or 'grep -Ri license *', and there were some occurrences in the .svg ^^
[12:42] <pochu> mr_pouit:             <cc:license
[12:42] <pochu>                rdf:resource="http://creativecommons.org/licenses/by-nc-sa/2.5/" />
[12:42] <pochu> mr_pouit: thanks! :)
[12:42] <mr_pouit> np ;)
[12:52] <gnomefreak> who is a revu admin?
[12:52] <Hobbsee> gnomefreak: what's up?
[12:53] <gnomefreak> Hobbsee: i cant get my password to comment
[12:53] <Hobbsee> ah.   no idea
[12:53] <gnomefreak> when i use recover it never gives me a sig. to decrypt
[12:55] <thp> If I have packaged a piece of software for Debian, and it is in Debian unstable already, what needs to be done to get the same package into Ubuntu (and maybe always update the package in Ubuntu when it's updated in Debian)?
[12:55] <StevenK> At this point, nothing.
[12:55] <StevenK> We're early in the release cycle for Gutsy, so it will get pulled in automatically.
[12:56] <thp> when does these updates happen and where can I see what packages have been pulled?
[12:57] <StevenK> For packages that are in Debian but not in Ubuntu, they happen on the whim of the ubuntu-archive team.
[12:57] <TheMuso> joejaxx: When troy_s is around tomorrow my time, I'll see about getting access to his. What needs building
[12:57] <TheMuso> oops wrong channel
[12:57] <StevenK> As for seeing what packages have been pulled, you could search in Launchpad.
[12:58] <thp> so, if i want to package for Debian and have the package in Ubuntu, I don't have to do anything but just wait until it gets synchronized? so no motu upload is necessary or such?
[12:58] <gnomefreak> StevenK: wouldnt someone need to tell the archive team what package it is since not all debian packages come over to ubuntu?
[12:59] <minghua> gnomefreak: I believe not
[12:59] <StevenK> gnomefreak: No, they just get pulled over.
[12:59] <gnomefreak> oh
[01:01] <gnomefreak> hmmm it seems it still builds on feisty :(
[01:02] <geser> thp: this is only true till the automatic import stops. after that a sync request (acked by a MOTU) is needed
[01:03] <thp> geser: the package i'm talking about is http://packages.qa.debian.org/g/gpodder.html -- does it qualify for automatic importing from Debian to Ubuntu or do I have to beg a MOTU to have a look?
[01:04] <thp> or is it only synced from Debian testing?
[01:04] <StevenK> It will be synced from unstable.
[01:05] <StevenK> thp: Exercise patience, it will find it's way over here.
[01:06] <TheMuso> Most people are only running gutsy in a chroot at this point anyway.
[01:08] <thp> ok, thanks. just wanted to know if there is anything i have to do or if it will do that automatically =)
[01:08] <geser> thp: you have time to get it included till mid August
[01:09] <thp> and if gutsy is shortly before release, it will be frozen and after the gutsy release ubuntu will pull again the latest package version from debian unstable, right?
[01:09] <geser> yes
[01:09] <thp> so when working on Debian, i'm indirectly contributing to ubuntu :) that's cool.. thanks for your time and the answers.. see ya
[01:14] <Lutin> hey DktrKranz
[01:14] <DktrKranz> hi Lutin
[01:53] <gnomefreak> ok this is getting really odd
[01:57] <gnomefreak> does dpkg-buildpackage -rfakeroot -S -sa not apply patches?
[01:59] <persia> gnomefreak: If debian/rules specifies patching, it should.
[02:00] <gnomefreak> persia: it fails when testing the build with fakeroot ./debian/rules binary  "OR"  dpkg-buildpackage -rfakeroot -nc  but doesnt fail using the -S -sa
[02:01] <minghua> well, dpkg-buildpackage -S only builds the _source_ package
[02:02] <persia> gnomefreak: Try `dpkg-buildpackage -rfakeroot` without the -nc.  You need to clean before you patch.
[02:02] <gnomefreak> i get dpkg-source: warning: executable mode 0755 of `debian/patches/80_app_name.dpatch' will not be represented in diff on all patches but should still be fine i would have thought
[02:02] <gnomefreak> persia: these patches have been here. ive been building this package for 2+ months
[02:03] <gnomefreak> trying it without the -nc and maybe the patches need to be updated for gutys :(
[02:03] <persia> gnomefreak: That's probably the issue.  Copy the files you changes somewhere else, grab the original sources, and patch back to what you think it should be.  Likely you ran debuild (or the quivalent) twice in a row at some point in the past (or at least, that's what usually happens to me).
[02:04] <gnomefreak> i use fakeroot ./debian/rules clean before each build just habit :( i know dpkg-buildpackage will clean for me but habit
[02:06] <xxxxx1> morning!
[02:06] <gnomefreak> xxxxx1: morning
[02:12] <TheMuso> geser: I'm happy to sponsor bluekuja for apt-move, as I am working with him on other merges.
[02:12] <TheMuso> geser: Unless you would rather do it.
[02:21] <geser> TheMuso: he asked me already about merging apt-move and it's ok if he does it
[02:23] <TheMuso> geser: I know.
[02:23] <TheMuso> I suggested he do so.
[02:24] <TheMuso> Just letting you know I'm willing to sponsor.
[02:29] <Amaranth> Hobbsee: So how do I make pbuilder give me a shell when a build fails?
[02:30] <ajmitch> put in a hook
[02:30] <siretart> Amaranth: look in /usr/share/doc/pbuilder for example hooks
[02:30] <siretart> Amaranth: there is a hook for that there
[02:30] <Amaranth> Pretend I have no idea what you're talking about :)
[02:30] <TheMuso> Shell on build failure is damn handy.
[02:30] <Amaranth> siretart: alright, cool
[02:31] <Amaranth> neat
[02:31] <StevenK> I find it is irritating sometimes, but most times it is a big help.
[02:31] <Amaranth> so i have to use --hookdir all the time or can i add this to a config file somewhere?
[02:31] <Hobbsee> what they said
[02:31] <StevenK> % cat .pbuilderrc
[02:31] <StevenK> HOOKDIR=/home/steven/.pbuilder/hooks
[02:31] <Hobbsee> in .pbuilderrc
[02:31] <Amaranth> ah
[02:31] <TheMuso> The only time its a pain is if you need to generate a log file.
[02:32] <StevenK> TheMuso: I don't find that, since I tend to only generate a logfile if the build was sucessful.
[02:32] <TheMuso> StevenK: Ah.
[02:33] <TheMuso> I find logfiles useful sometimes if a build fails, and I can't get enough info from whats shoing on the console when I'm in a shell inside the chroot.
[02:33] <Amaranth> arg
[02:33] <Hobbsee> StevenK: i dont think mithrandir will come and kill you if you get it wrong - too far away
[02:33] <Amaranth> compiz doesn't have make dist or distcheck
[02:33] <StevenK> Hobbsee: :-P
[02:34] <StevenK> I don't think I've gotten it wrong.
[02:34] <Amaranth> and dpkg-buildpackage -S will put this file in the .tar.gz (doing a native package for now) but in the pbuilder it's missing
[02:34] <Treenaks> Hobbsee: you on the other hand... :)
[02:34] <StevenK> Mind you, I don't think I'll bother, since it seems to be about as pointless as my clanlib merge.
[02:35] <Hobbsee> Treenaks: true
[02:36] <Amaranth> so, need some build system help
[02:36] <Amaranth> :)
[02:36] <Amaranth> i have this file that doesn't get copied into obj-i486-linux-gnu so the build fails
[02:37] <Amaranth> it's in extra_DIST
[02:37] <StevenK> Hrm. Then again, it reduces the debdiff to 1.5K as opposed to 48K.
[02:37] <persia> Amaranth: You can force it in configure: if you really want.
[02:37] <shawarma> Amaranth: Not EXTRA_DIST?
[02:37] <Amaranth> EXTRA_DIST, right
[02:38] <Amaranth> i don't want to force it, the build system upstream is broken
[02:38] <shawarma> Amaranth: Ah, good. It's case-sensitive, so..
[02:38] <Amaranth> but when i'm not making a package in pbuilder i can hack around it :)
[02:39] <gnomefreak> is anyone else having issues building packages with dpatch error?
[02:40] <Hobbsee> gnomefreak: dpatch error?  dpatch has many errors...
[02:40] <Hobbsee> well, can have
[02:40] <gnomefreak> test -d debian/patched || install -d debian/patched
[02:40] <gnomefreak> dpatch  apply-all
[02:40] <gnomefreak> applying patch 10_components_no_exec to ./ ... failed.
[02:40] <gnomefreak> make: *** [patch-stamp]  Error 1
[02:40] <Treenaks> wow, nice descriptive error
[02:40] <gnomefreak> :)
[02:40] <gnomefreak> yeah no kidding
[02:41] <shawarma> gnomefreak: It means it didn't work. Easy.
[02:41] <shawarma> :-p
[02:41] <gnomefreak> i started with fresh everything and same error
[02:41] <gnomefreak> shawarma: got that much ;)
[02:41] <shawarma> gnomefreak: Right, ok. Just trying to be helpful.
[02:41] <StevenK> gnomefreak: The patch output is in debian/patched/<patch>
[02:42] <gnomefreak> can't find file to patch at input line 11
[02:42] <gnomefreak> Perhaps you used the wrong -p or --strip option?
[02:42] <gnomefreak> The text leading up to this was:
[02:42] <StevenK> gnomefreak: The file mentioned in the patch was no found in .
[02:42] <StevenK> s/no/not/
[02:42] <gnomefreak> looking for it now
[02:45] <StevenK> gnomefreak: Any luck?
[02:46] <gnomefreak> StevenK: let you know in a few
[03:31] <afflux> TheMuso: you rejected bug 112867 because it already got merged, but the package is still mentioned on DaD and I can't find 8.2a-1 or newer in the archives
[03:31] <ubotu> Launchpad bug 112867 in conquest "Please merge conquest 8.2a-1 (universe) from Debian unstable (main)" [Undecided,Rejected]  https://launchpad.net/bugs/112867
[03:31] <TheMuso> afflux: I'll have another look in a bit.
[03:32] <afflux> no need to hurry
[03:37] <Lutin> seems that it hasn't been meged actually
[03:37] <Lutin> merged*
[03:37] <TheMuso> Lutin: Yeah I know.
[03:37] <TheMuso> I'll take care of it.
[03:37] <Lutin> TheMuso: ok :)
[03:39] <Treenaks>  http://www.cafepress.com/cp/prod.aspx?p=foodfight.132171648
[03:40] <joejaxx> Treenaks: :P
[03:45] <TheMuso> afflux: Ok, I updated the bug.
[03:46] <afflux> TheMuso: thank you. I'll update the diff because I did not include the previous ubuntu changelog entrys.
[03:46] <TheMuso> Which I noted in the bug.
[03:46] <afflux> oh, just read it :)
[03:51] <freeflying_> looking for sponsor upload to main http://<IP_ADDRESS>/~freeflying/scim/scim-pinyin_0.5.91-0ubuntu8.dsc
[03:53] <xxxxx1> StevenK: ping?
[03:53] <StevenK> xxxxx1: Pong.
[03:53] <xxxxx1> great
[03:53] <xxxxx1> steven, i have a question for you
[03:53] <xxxxx1> should I post my package with ubuntu-motu as maintainer and me as xsbc-original.. ?
[03:54] <xxxxx1> or stay only with maintainer and after he's approval became with these model
[03:54] <xxxxx1> ?!
[03:54] <Hobbsee> the former
[03:55] <xxxxx1> Hobbsee: only maintainer?
[03:55] <Hobbsee> as in, maintainer being motu, and xsbc as you
[03:56] <xxxxx1> lintian asks NMU
[03:56] <xxxxx1> W: ecryptfs-utils source: changelog-should-mention-nmu
[03:56] <xxxxx1> W: ecryptfs-utils source: source-nmu-has-incorrect-version-number 15-0ubuntu1
[03:56] <xxxxx1> i should create a lintian-override for source or just ignore them?
[03:57] <persia> xxxxx1: Ignore that warning.  Every Ubuntu upload is an NMU.
[03:57] <xxxxx1> ok. thx guys :)
[04:01] <TheMuso> argh. Whats the most reliable way to use a variable in a for loop within debian/rules?
[04:01] <TheMuso> I've seen examples that use $$, but that doesn't seem to be working for me.
[04:01] <StevenK> $$var should work
[04:01] <persia> TheMuso: Take a look at docbook - it has a good example
[04:02] <StevenK> for i in in foo ; do echo $$i ; done
[04:02] <TheMuso> persia: Thanks.
[04:02] <TheMuso> hmmm ok.
[04:02] <persia> TheMuso: StevenK is also right.
[04:10] <sharms> dabaR: thanks for the info
[04:16] <persia> TheMuso: When you have a bit of time, would you mind testing to see if a new candidate version of audacity works with JACK on powerpc?
[04:16] <TheMuso> persia: Unfortunately that box is headless.
[04:16] <persia> TheMuso: Ah.  No worries then.
[04:16] <TheMuso> And its only a G3 300.
[04:17] <nixternal> alright StevenK, I am getting the ball rolling here. Signed up for everything on Alioth, attempting to join the Qt/KDE Packaging team, getting my key signed with in the next week or so...outlook looks good!
[04:17] <nixternal> waiting for Ana to approve/deny
[04:17] <StevenK> Great.
[04:18] <StevenK> Which means krename will be handled by the team as well?
[04:19] <nixternal> It would be nice
[04:19] <nixternal> the KDE Extras team at least should have it anyways imho
[04:19] <nixternal> if they had it, I don't think there would be this lapse in updates
[04:19] <TheMuso> afflux: Working on the merge now.
[04:20] <afflux> thank you
[04:20] <TheMuso> afflux: Apologies about that. I got mixed up with version numbers, assuming there was a greater version number there, without actually checking. :)
[04:22] <afflux> Yes, I guess this "a" in the version is confusing
[04:26] <ajmitch> bye :)
[04:28] <nixternal> heh, they pulled the plug huh
[04:34] <Ademan_> what's the difference between the dia-gnome and dia packages?  All the dia-gnome package says is that it's the GNOME version, what exactly does that mean?  I mean they both use Gtk+...
[04:37] <geser> without checking I'd guess dia-gnome is linked against the Gnome libs and dia isn't
[04:38] <Ademan_> but for what purpose i guess is my question
[04:38] <persia> Does anyone have any suggestions about how I might debug http://pastebin.ca/482976?  LImited exploration with gdb and valgrind hasn't pointed me at anything particular yet.
[04:40] <Ademan_> sorta seems like you're out of memory, but that shouldn't happen lol
[04:40] <Ademan_> definitely seems like g_malloc() is failing
[04:41] <Ademan_> or returning NULL maybe
[04:41] <Ademan_> which generally indicates out of memory
[04:41] <Ademan_> http://mail.gnome.org/archives/gtk-app-devel-list/1999-November/msg00151.html    ah apparently g_malloc() won't return null, it aborts your program
[04:42] <Ademan_> so i suppose that could be the problem you're describing
[04:42] <persia> Ademan_: Nope.  Plenty of memory available,  Just allocations are odd.  I'm guessing that I'm not checking the memory bounds correctly, but I'm not sure where.
[04:42] <Ademan_> this is your own app?
[04:44] <persia> Ademan_: No.  Just one I'm working on.
[04:46] <Ademan_> hrm well i honestly don't know, it just seems as though every error is a failed memory allocation
[04:47] <pochu> Ademan_: regarding dia, dia-gnome includes the files in /usr/share/applications/, while dia doesn't
[04:48] <Ademan_> pochu: *.desktop files?
[04:50] <pochu> Ademan_: yes
[04:51] <Ademan_> ah cool, thanks
[04:51] <pochu> yw
[05:26] <ceros> hello, are any revu admins here?
[05:26] <xxxxx1> yep
[05:28] <ceros> i'm trying to reupload a package
[05:28] <ceros> it has the same name so i was wondering if it can be deleted from the incoming folder
[05:28] <xxxxx1> no, just overwrite
[05:29] <ceros> it's not working for me
[05:29] <xxxxx1> revu maintain the versions
[05:29] <ceros> isn't it dput -f
[05:29] <xxxxx1> -f is necessary only if you already have .upload file
[05:30] <xxxxx1> just upload again
[05:30] <ceros> just tried
[05:30] <ceros> error 533 could not create file
[05:30] <xxxxx1> what's your package?
[05:30] <ceros> sauerbraten
[05:30] <xxxxx1> can you paste link?
[05:30] <ceros> ftp://revu.tauware.de/incoming/sauerbraten_0.0.20070413-0ubuntu1.tar.gz
[05:31] <xxxxx1> no.
[05:31] <xxxxx1> the http link
[05:32] <ceros> you mean this one? http://revu.tauware.de/details.py?upid=4204
[05:32] <xxxxx1> yep
[05:33] <ceros> there was an error trying to upload the first time
[05:33] <ceros> it errored while trying to upload my changes file
[05:33] <ceros> now i can't upload at all
[05:34] <xxxxx1> you have created the source properly? sign the package too?
[05:34] <ceros> yes
[05:35] <xxxxx1> paste the error
[05:35] <afflux> ceros: do you know that debian is already working on sauerbraten?
[05:35] <ceros> Error '553 Could not create file.' during ftp transfer of sauerbraten_0.0.20070413-0ubuntu1.dsc
[05:35] <ceros> Note: This problem might be caused by files already existent on the server.
[05:35] <ceros>       For the official Debian upload queues, the dcut(1) utility can be used
[05:35] <ceros>       to remove stale files from unsuccessful uploads.
[05:36] <ceros> afflux: which version?
[05:36] <afflux> debian has 200612something in the repos and is working on 20070413
[05:38] <ceros> i didn't know they were working on 20070413
[05:39] <ceros> i checked http://www.debian.org/devel/wnpp/
[05:39] <ceros> didn't see it
[05:43] <afflux> ceros: check http://svn.debian.org/wsvn/pkg-games/packages/trunk/
[05:50] <ceros> alright thanks afflux
[05:57] <leonel> ScottK: ping
[06:20] <jussi01> Good afternoon motu's!!
[06:21] <jussi01> Has anyone got somthing that needs doing... Im in between projects at the moment. Id like something specific if possible... :D
[06:24] <DarkSun88> Hi all
[06:42] <bddebian> Heya gang
[06:44] <pochu> hi bddebian
[06:45] <bddebian> Hello pochu
[06:46] <geser> Hi bddebian
[06:47] <bddebian> Heya geser
[07:01] <xxxxx1> bddebian: <o/
[07:02] <bddebian> Hello xxxxx1
[07:31] <xxxxx1> http://revu.tauware.de/details.py?upid=5105
[07:31] <xxxxx1> ecryptfs-utils
[07:31] <xxxxx1> :)
[07:39] <geser> FTBFS for me
[07:40] <geser> cp: cannot stat `./debian/tmp/lib/security/pam_ecryptfs.so': No such file or directory
[07:43] <xxxxx1> ?
[07:51] <geser> xxxxx1: the file is not there and can't be copied into the deb
[07:52] <xxxxx1> hmm
[07:52] <xxxxx1> i had tested many times.
[07:52] <geser> in a pbuilder?
[07:52] <xxxxx1> directly in my gutsy jail
[07:53] <xxxxx1> probably you need the libpam dev files.
[07:53] <xxxxx1> pbuilder don't install depends
[07:53] <xxxxx1> build deps.
[07:53] <xxxxx1> try to check.
[07:53] <xxxxx1> Build-Depends: debhelper (>= 5), autotools-dev, libkeyutils-dev, libgcrypt11-dev
[07:53] <xxxxx1> , libpam0g-dev, libssl-dev
[07:53] <geser> sure does pbuilder install build-depends
[07:54] <xxxxx1> if the file is not in the place, is not compiled.
[07:54] <geser> if it doesn't build in a pbuilder it will sure fail also on the buildds
[07:55] <ranf> hi
[07:55] <xxxxx1> can you check these dep?
[07:55] <xxxxx1> in your pbuilder root
[07:57] <geser> pbuilder installs B-D as specified in the control file
[08:57] <gnomefreak> bddebian: thank you for comment on revu you found major bug
[09:25] <pochu> it seems that debian doesn't have a dh_iconcache
[09:27] <man-di> pochu: no, it hasnt
[09:38] <xxxxx1> http://revu.tauware.de/details.py?upid=5110
[09:38] <xxxxx1> ecryptfs-utils
[09:43] <Fahuadai> Hello
[10:01] <jayteeuk> Hi all.
[10:01] <jayteeuk> Could someone offer me some guidance on bug #93413 please.
[10:01] <ubotu> Launchpad bug 93413 in vpnc "vpnc dead peer detection disconnects immediately" [Medium,Confirmed]  https://launchpad.net/bugs/93413
[10:01] <Fahuadai> hi
[10:02] <jayteeuk> Severe regression from Edgy (version 0.3.3 I think) to Feisty (version 0.4.0).
[10:04] <jayteeuk> The introduction of dead peer detection in 06_stolen_from_head.dpatch basically renders vpnc useless for a number of users.
[10:05] <crimsun> jayteeuk: have you created a debdiff?
[10:06] <jayteeuk> I created a patch (09_config_disable_dpd.dpatch attached to the ticket) which adds an extra config option to disable dead peer detection.
[10:06] <crimsun> err, that's ~1000 lines to revert
[10:06] <crimsun> fairly significant in size and definitely not "eyeballable"
[10:06] <jayteeuk> Please bear in mind this is the first time I've tried to submit a patch, so I'm a total n00b. :)
[10:08] <jayteeuk> Upstream, vpnc HEAD contains a patch which adds an option to set the DPD timeout, where a value of 0 disables DPD.  I think this is a cleaner fix than mine.
[10:08] <crimsun> http://lists.unix-ag.uni-kl.de/pipermail/vpnc-devel/2007-April/001498.html  would be more sane than reverting 06.
[10:08] <crimsun> now.  Have you  /tested/  that patch?
[10:09] <jayteeuk> Not the one suggested there, no.  I've tested mine and use it on a daily basis.
[10:09] <crimsun> ok, so what you should do is roll r170 from svn trunk into a new source package and test it [not your fix] .
[10:11] <crimsun> I can walk you through it if you have ~15m
[10:11] <jayteeuk> Sure.
[10:11] <crimsun> first, create a scratch dir and cwd into ti
[10:11] <crimsun> into it$
[10:12] <jayteeuk> 1 mo while I arrange my windows. :)
[10:12] <geser> as I'm also affected from this bug, I could do a SRU for it
[10:13] <jayteeuk> OK, I'm ready. :)
[10:13] <crimsun> jayteeuk: apt-get source vpnc
[10:13] <jayteeuk> Yep.
[10:16] <jayteeuk> So now I have a vpnc-0.4.0 directory with the debian package management stuff but none of the patches applied.
[10:16] <crimsun> jayteeuk: ok, now in the scratch dir (not in the root of the extracted Debian source package) extract the r170 diff
[10:17] <jayteeuk> The r170 diff?  Is that the one from the URL above?
[10:18] <crimsun> yes
[10:18] <jayteeuk> OK, so just save that in the scratch dir?
[10:18] <jayteeuk> Baby steps, I'll learn. :)
[10:19] <crimsun> well, you don't want the HTMLized
[10:19] <jayteeuk> Actually it's probably HTML formatted so I'll copy/paste it.
[10:19] <jayteeuk> Yeah. :)
[10:20] <jayteeuk> OK.
[10:20] <crimsun> the other way of doing it is probably a bit more painstaking
[10:21] <jayteeuk> I'll go with whichever way you think will result in me not having to come back and ask how to do it again.
[10:21] <jayteeuk> Unfortunately I'm completely at the mercy of you and what I read of the transcript of one of the Ubuntu Week sessions.
[10:22] <crimsun> ok.  Have you saved the copied-n'-pasted diff?
[10:22] <jayteeuk> Yes.
[10:22] <crimsun> ok.
[10:22] <jayteeuk> I now have an r170.diff in the scratch dir.
[10:23] <crimsun> we'll attempt to use dpatch-edit-patch(1)
[10:23] <crimsun> cwd into the extracted source dir
[10:24] <jayteeuk> OK, I've read about that in the aforementioned transcript, but not gone through the process yet.  Here goes!
[10:24] <jayteeuk> Done.
[10:25] <crimsun> dpatch-edit-patch patch 09_dpd_timer_disable 08_auth_failed_return_code
[10:26] <jayteeuk> "Now launching an interactive shell..."
[10:26] <crimsun> patch -p1 --dry-run </tmp/diff
[10:26] <xxxxx1> http://revu.tauware.de/details.py?upid=5105 : ecryptfs-utils
[10:26] <crimsun> you'll get one reject
[10:27] <crimsun> s/get/see/
[10:27] <jayteeuk> Should I replace /tmp/diff with the r170.diff?
[10:27] <crimsun> yes
[10:27] <crimsun> (/tmp/diff is what I used)
[10:28] <jayteeuk> Yes, I've got one rejection in config.h
[10:28] <StevenHarperUK_> Hi : I have just registered my lauchpad project https://launchpad.net/usb-adsl-modem-manager  I have a working application but I could really do with Mentoring : can anyon epoint me in the right direction please
[10:29] <crimsun> jayteeuk: ok, now remove the --dry-run and actually apply the diff
[10:29] <crimsun> jayteeuk: you'll need to fix up config.h by hand
[10:30] <jayteeuk> OK, I'll have a look at what failed...
[10:31] <crimsun> it's a one-liner that failed due to additional members that were added
[10:32] <jayteeuk> Yep.  I think I'm OK to add that line where it is in the r170 diff, after CONFIG_UDP_ENCAP_PORT
[10:33] <ivoks> StevenHarperUK_: does it support ethernet modems?
[10:33] <crimsun> jayteeuk: after you save it, you need to remove *.orig and *.rej
[10:33] <ivoks> oh, only pppoa?
[10:33] <StevenHarperUK_> ivoks:Ethernet Modems?
[10:34] <crimsun> jayteeuk: (along the lines of find -name '*.orig'|xargs rm && find -name '*.rej'|xargs rm)
[10:34] <jayteeuk> rm *.{orig,rej}
[10:34] <ivoks> StevenHarperUK_: yes, modems that are connected to ethernet card (better solutions than usb adsl modem)
[10:34] <bddebian> bashism! eeks :)
[10:34] <jayteeuk> OK, that's done.
[10:34] <crimsun> jayteeuk: exit 0
[10:35] <jayteeuk> "Creating new patch..."
[10:35] <StevenHarperUK_> ivoks: if you ead my Wiki the reason I want to add USB modem support is for all the modems already out there and the old PC's that people put Ubuntu on for relatives etc
[10:35] <crimsun> jayteeuk: then, echo 09_dpd_timer_disable|tee -a debian/patches/00list
[10:35] <StevenHarperUK_> ivioks:  ** ready my wiki
[10:36] <jayteeuk> OK.
[10:36] <crimsun> jayteeuk: next, ensure that you have the devscripts package installed.
[10:36] <ivoks> yeah, usb modems are weak link and it would be great it they could work
[10:36] <StevenHarperUK_> I have them working
[10:37] <StevenHarperUK_> I work for a Major ISP in the UK
[10:37] <StevenHarperUK_> I have acess to all teh USB modem version they have sent out
[10:37] <jayteeuk> Apparently not, but that's being rectified....
[10:37] <StevenHarperUK_> they all work with my app
[10:37] <ivoks> StevenHarperUK_: great
[10:37] <ivoks> StevenHarperUK_: so, what help do you need?
[10:37] <ivoks> packaging?
[10:37] <StevenHarperUK_> I have written the app: I need help with the proccess to get it packaged n noticed n used
[10:38] <StevenHarperUK_> Yeh
[10:38] <StevenHarperUK_> & testing
[10:38] <StevenHarperUK_> I have no access to a DSL line that needs PPPoe Auth
[10:38] <ivoks> well, i can't help you with testing (in croatia we don't have speadtouch usb modems)
[10:38] <ivoks> speed even :)
[10:38] <jayteeuk> crimsun: OK, now I've got devscripts installed.
[10:38] <crimsun> jayteeuk: then, dch -v0.4.0-2ubuntu1.1 -Dfeisty-proposed
[10:38] <StevenHarperUK_> In the UK every ISP sent them out
[10:39] <ivoks> but i could help you with packaging
[10:39] <StevenHarperUK_> I have a SVN project
[10:39] <ivoks> i noticed, yes
[10:39] <StevenHarperUK_> http://www.squeezedonkey.com/svn/linux/
[10:39] <StevenHarperUK_> Branch 0.3 is best
[10:39] <jayteeuk> OK, I've understood everything up to that. :)
[10:40] <StevenHarperUK_> Basically you have to run the App with > python USBAdslModemManager
[10:40] <crimsun> jayteeuk: dch is a helper utility; -v accepts a version string; -D accepts a distribution
[10:40] <jayteeuk> Ah, I'm creating a changelog entry?
[10:40] <crimsun> jayteeuk: yes.
[10:40] <StevenHarperUK_> I will need all teh Menu shortcuts n stuff - I am going to add auto start on login / computer startup
[10:40] <ivoks> StevenHarperUK_: oh, it's a gui app?
[10:40] <StevenHarperUK_> I know how to do them bits
[10:40] <StevenHarperUK_> Yeh
[10:40] <StevenHarperUK_> You can try it
[10:40] <StevenHarperUK_> it wont break anything
[10:40] <jayteeuk> So -v specifies the new version of the package, and -D specifies which distribution the package will go to?
[10:41] <ivoks> heh i will, but not at 11PM :)
[10:41] <ivoks> tomorrow ;)
[10:41] <StevenHarperUK_> Theres no setup
[10:41] <StevenHarperUK_> just SVN it out n run the python
[10:41] <ivoks> i know
[10:41] <StevenHarperUK_> k
[10:41] <crimsun> jayteeuk: yes.
[10:41] <ivoks> i'll take a look at it tomorrow
[10:41] <StevenHarperUK_> The app extracts the firmware - and then sets up the PPP and secrets
[10:42] <StevenHarperUK_> then dials up and the tray icon shows the status
[10:42] <ivoks> for autostart, menu entry - don't worry, that's easy to set up
[10:42] <StevenHarperUK_> Can  you drop me an Email ?
[10:42] <ivoks> extracts firmware from?
[10:42] <StevenHarperUK_> Well it uses firmware binary to get the correct one from teh modem
[10:42] <ivoks> StevenHarperUK_: ivoks AT name_of_the_best_distribution_out_there DOT com
[10:42] <ivoks> :)
[10:43] <StevenHarperUK_> ta
[10:43] <jayteeuk> Right.  So what would be appropriate in this case?  Should I just say I merged the r170 patch from svn?
[10:43] <ivoks> StevenHarperUK_: so, firmware is not free?
[10:43] <jayteeuk> Possibly explain what it does -- add an extra config option to specify DPD timeout?
[10:43] <StevenHarperUK_> Im not sure
[10:43] <StevenHarperUK_> ther is supposeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeed to be a fre eone
[10:43] <StevenHarperUK_> sorry jammed key
[10:43] <crimsun> jayteeuk: yes
[10:43] <StevenHarperUK_> and it should work like the one I have
[10:43] <crimsun> jayteeuk: e.g., http://pastebin.ca/483642
[10:44] <jayteeuk> Ah, thanks. :)
[10:44] <ivoks> StevenHarperUK_: i don't doubt it will work
[10:44] <ivoks> StevenHarperUK_: but the license is important
[10:44] <StevenHarperUK_> I have tested it for days
[10:44] <StevenHarperUK_> Yes I know
[10:44] <StevenHarperUK_> Ill check that nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnow
[10:44] <nixternal> ARGH! how come reportbug sent my bug to Ubuntu and not Debian
[10:44] <StevenHarperUK_> sorry Jammed Key again
[10:44] <nixternal> GRRRR
[10:44] <ivoks> StevenHarperUK_: great, send me a mail with results
[10:45] <crimsun> nixternal: anti-Vista user measures.
[10:45] <ivoks> StevenHarperUK_: we have to have clear view on those firmwares in firmware/
[10:45] <nixternal> hardy har har
[10:45] <jayteeuk> Of course, mention the LP ID too.  I've just taken that verbatim if you don't mind.
[10:45] <ivoks> StevenHarperUK_: i guess everything else is GPL? :)
[10:45] <StevenHarperUK_> Oh yes
[10:46] <StevenHarperUK_> Im going to go find out about the firmware now
[10:46] <crimsun> jayteeuk: you likely want to mention the config option, too.
[10:47] <jayteeuk> A couple of things -- I think the patch defaults the timeout to 300 seconds, in which case the disconnection problem will still manifest itself.  Should I change the default to 0 instead to disable the problematic feature by default?  And should I update the man page etc.?
[10:48] <crimsun> yes, though if you do that, make sure you go back and use dpatch-edit-patch in the "edit patch" mode
[10:48] <ivoks> StevenHarperUK_: ok, send results on email; i'm of to bed now :/
[10:48] <StevenHarperUK_> I sent you a quick email already
[10:48] <crimsun> geser: are you available to help jayteeuk with the remainder of the SRU for #93413?  I need to run to a meeting.
[10:48] <StevenHarperUK_> ill send another
[10:48] <StevenHarperUK_> goodnight
[10:48] <ivoks> ok, 'night
[10:49] <jayteeuk> OK, thanks so much for your help crimsun, very much appreciated.
[10:49] <leonel> crimsun: do you know what's next with  this :  https://bugs.launchpad.net/ubuntu/+source/squirrelmail/+bug/113725  ??
[10:49] <ubotu> Launchpad bug 113725 in squirrelmail "Cross site scripting in HTML filter" [High,Confirmed]
[10:50] <jayteeuk> With a n00b like me 15 minutes quickly becomes an hour. :)
[10:50] <geser> crimsun: sure
[10:50] <crimsun> geser: / jayteeuk: thanks
[10:50] <geser> where have you stopped?
[10:50] <jayteeuk> No, thank *you*!
[10:50] <jayteeuk> geser: I'm editing the changelog at the moment.
[10:51] <crimsun> geser: he needs to rerun dpatch-edit-patch in "edit patch" mode to change the man page to reflect an additional change he will make
[10:51] <jayteeuk> Last command was dch -v0.4.0-2ubuntu1.1 -Dfeisty-proposed
[10:51] <crimsun> leonel: I have about three minutes; let me look.
[10:52] <leonel> crimsun: it's not urgent  I'd like to know if there's anything I can do
[10:53] <geser> jayteeuk: are you done with editing the changelog?
[10:53] <jayteeuk> geser: I think so, yes.
[10:54] <crimsun> leonel: because the original source package does not use a patch management system, it is in our best interest to not add one (like dpatch).  In this context, please apply the patch directly to the source instead of using dpatch.  The diff will appear in the diff.gz anyhow.
[10:55] <leonel> so start over ?
[10:55] <leonel> crimsun: ?
[10:55] <crimsun> leonel: reroll the debdiff with the patch applied directly, yes.
[10:56] <leonel> crimsun: and all the info just  add it to the  bug info in launchpad ?
[10:56] <crimsun> leonel: (i.e., don't modify debian/{control,rules} to add dpatch)
[10:56] <leonel> ok
[10:56] <leonel> unpack
[10:56] <leonel> dpatch
[10:56] <leonel> and send the debdiff ?
[10:57] <jayteeuk> geser: OK, so just write that out and exit the editor?
[10:57] <geser> yes
[10:57] <jayteeuk> Done.
[10:57] <crimsun> leonel: just create a new debdiff, and attach it to the bug report.  The new debdiff should have the dpatch applied directly, and the source should not modify debian/control or debian/rules to add dpatch.
[10:57] <xxxxx1> night! bye all
[10:57] <crimsun> xxxxx1: bye
[10:57] <leonel> crimsun: OK  will do it  later    thank  you
[10:57] <geser> jayteeuk: as crimsun said you need to add the new option to the manpage
[10:57] <crimsun> leonel: sorry, but I'm nearly late for a meeting.
[10:58] <leonel> run crimsun  run  :)
[10:58] <leonel> thanks
[10:58] <jayteeuk> OK, so I'll be editing the 09 patch that I've just created.
[10:58] <jayteeuk> Using dpatch-edit-patch ?
[10:58] <geser> yes, dpatch-edit-patch patch 09_dpd_timer_disable will create you a working copy
[10:59] <geser> so you can simply edit files
[10:59] <geser> and at the edit collect your changes and update the patch
[10:59] <geser> *at the end collect*
[11:01] <jayteeuk> Oh, actually the man page doesn't list the options, it seems to leave that to vpnc --long-help
[11:01] <jayteeuk> Which I'm slightly glad about because I'd forgotten how strange the man page format is!
[11:01] <geser> than you don't need to change it
[11:02] <jayteeuk> No, just the default value for the option.
[11:02] <geser> it the new option included in --long-help?
[11:02] <jayteeuk> I won't know until I've built the package.
[11:03] <geser> than that's the next step (if I didn't forget something)
[11:03] <jayteeuk> But I've made the edit for the default value, so just exit 0 from the subshell to update the patch?
[11:03] <geser> yes
[11:03] <jayteeuk> OK, the patch is updated.
[11:04] <geser> I assume you don't have a pbuilder setup?
[11:04] <jayteeuk> I don't recognise the term, so I assume not too.
[11:04] <geser> pbuilder is a scipt which helps to build package in a clean chroot and cleans up after build
[11:04] <jayteeuk> I will most definitely be saving a transcript of this conversation. :)
[11:05] <jayteeuk> OK, I see.
[11:05] <geser> so you need to build the package in your normal environment
[11:05] <jayteeuk> Should I set one up, and if so how?
[11:05] <geser> or setup a pbuilder
[11:06] <jayteeuk> OK, that's how I built the package with my previous patch, just in my normal environment.
[11:07] <jayteeuk> So should I just go ahead and "debian/rules binary" in my normal environment?
[11:08] <geser> so you have already the necessary packages installed installed
[11:08] <jayteeuk> buildessential et al?
[11:08] <geser> no, use dpkg-buildpackage or debuild
[11:08] <geser> yes
[11:08] <geser> apt-get build-dep vpnc will install all the needed packages
[11:08] <jayteeuk> Ah, that's useful to know, thanks.
[11:09] <geser> btw: https://wiki.ubuntu.com/PbuilderHowto
[11:09] <jayteeuk> Brilliant, I'll have a read of that over the weekend!
[11:09] <jayteeuk> OK, all build dependencies are already installed.
[11:09] <geser> do you have fakeroot installed?
[11:10] <jayteeuk> Yes.
[11:11] <geser> than should "dpkg-buildpackage -rfakeroot" build the source and binary package
[11:11] <geser> if you had a pbuilder you would build only a source package (-S) and do pbuilder build the binary packages
[11:12] <jayteeuk> OK, I think that was successful.  Some warnings but I didn't notice any errors.
[11:13] <jayteeuk> It asked me for my GPG key passphrase twice, is that normal?
[11:13] <geser> yes, but you can ignore/abort it for now
[11:14] <geser> this is only needed if you want to upload the package
[11:14] <jayteeuk> Which I guess I can't anyway?
[11:14] <geser> no
[11:14] <jayteeuk> That's a whole other conversation. :)
[11:15] <geser> if you are in the ubuntu-contributors team you can upload to revu (to let others check your package)
[11:15] <geser> for upload to the archive you need to be a MOTU or core-dev
[11:16] <jayteeuk> I'll look into both options.
[11:16] <jayteeuk> Is joining ubuntu-contributors as simple as joining the team on LP?
[11:16] <geser> yes,
[11:16] <geser> !revu > jayteeuk
[11:17] <jayteeuk> Excellent, thanks.
[11:17] <jayteeuk> I'm learning a lot tonight.
[11:17] <geser> if everything went fine you should have a deb (which you can test)
[11:17] <geser> and a new .dsc/.diff.gz (the new source package)
[11:18] <jayteeuk> Indeed I do.
[11:18] <jayteeuk> And also a .changes
[11:19] <geser> that is needed for upload
[11:19] <jayteeuk> I thought as much, having checked the contents.
[11:19] <jayteeuk> OK, so I can just go ahead and install the new .deb and test it?
[11:19] <geser> (you sign the .changes file and the .dsc before uploading, therefore the question about your gpg passphrase)
[11:19] <geser> sure
[11:20] <jayteeuk> OK, it's installed... let's first check if the new option is listed in --long-help
[11:21] <jayteeuk> Yes it is.  That's good.
[11:21] <highvoltage> 9/win 12
[11:23] <jayteeuk> Well so far so good.
[11:24] <jayteeuk> At least with the default timeout set to zero.
[11:26] <jayteeuk> So now I'm testing it with the timeout set to 300, as was the hard-coded default before the patch.
[11:26] <jayteeuk> And it seems to have reverted to the old behaviour, as expected.
[11:27] <geser> good or bad, depends how one sees it :)
[11:28] <jayteeuk> Well, yes. :)
[11:28] <geser> the next step is to create a debdiff (a diff of all changes between two packages)
[11:28] <jayteeuk> OK.
[11:29] <geser> debdiff unmodified.dsc new.dsc
[11:29] <geser> you might want to redirect the output to a file as you need to attach it to the LP bug
[11:29] <jayteeuk> Should I do this from the scratch dir or does it matter?
[11:29] <geser> it doesn't matter
[11:30] <geser> debdiff takes the path to the old .dsc file and the new .dsc file
[11:30] <geser> it's like diff but for debian (source) packages
[11:31] <jayteeuk> OK, that's done.
[11:32] <jayteeuk> Eek, the 09_whatever patch file doesn't have my correct e-mail address but my username and hostname of my laptop.  Is that OK or should I change it?
[11:34] <geser> like you want
[11:34] <jayteeuk> And if it should contain my correct e-mail address, is there somewhere I can set that rather than it taking what it has as the default?
[11:35] <geser> dpatch-edit-patch takes it from DEBFULLNAME and DEBEMAIL environment variables (also used by other tools)
[11:36] <jayteeuk> Fantastic set of scripts. :)
[11:37] <geser> in this case you don't need to redo everything, simply edit the debdiff
[11:37] <geser> but don't introduce new linebreaks
[11:38] <jayteeuk> OK, well I made the change in the patch file and re-built, re-installed, re-debdiffed. :)
[11:38] <jayteeuk> Maybe the long way around, but never mind.
[11:39] <jayteeuk> So now I have my .diff -- is there a convention for naming debdiffs?
[11:39] <geser> no
[11:39] <jayteeuk> OK that's fine then.
[11:40] <geser> that's the normal way (which works always), what I mentioned was a shortcut
[11:41] <geser> I do it sometimes when I spot a spelling error (or something like that) when I look at my own debdiffs before submitting
[11:42] <jayteeuk> I have some reading to do. :)
[11:43] <jayteeuk> So how do we proceed?
[11:44] <geser> when you are happy with the debdiff attach it to the bug
[11:44] <jayteeuk> OK, that's easy enough.
[11:47] <jayteeuk> Done.
[11:49] <geser> As ubuntu-universe-sponsors is already subscribed to the bug nothing needs to be done.
[11:49] <jayteeuk> Excellent.
[11:50] <jayteeuk> Yes, I subscribed them earlier in the process after I'd attached a patch.
[11:52] <jayteeuk> So now the patch will be reviewed and, in a perfect world, accepted?  Or what?
[11:52] <geser> yes, I gave it a quick look and it looks good
[11:52] <bmm> Hi everybody. I've got a program I'd love to be entered into ubuntu. It's a simple configure;make;makeinstall program and I've written it myself.   I'm positively buzzing with excitement. :)
[11:53] <bmm> Would it be faster to package it an put it in Revu or ask somebody else to package it?
[11:55] <ScottK> bmm: Unless you know someone who knows how to package and is willing to do it, almost certainly faster if you put it on REVU.
[11:56] <ScottK> jayteeuk: Congratulations.
[11:56] <jayteeuk> Thanks. :)
[11:56] <bmm> ScottK: I don't know anybody, so then REVU is probably the best solution... well I'll be off packaging then.
[11:57] <jayteeuk> I'm not quite sure how I'm going to sleep now... but it's time for bed.
[11:57] <geser> jayteeuk: there is some unrelated change to vpnc-script in the dpatch
[11:58] <jayteeuk> geser: Ah, thanks for pointing that out.
[11:58] <geser> I try to understand why it does and talk to crimsun if it can stay or should be cut out (proably the later)
[11:58] <jayteeuk> OK, I'll take another look at that on Monday.
[11:58] <geser> and upload it then
[11:59] <geser> jayteeuk: thanks for creating the debdiff
[12:00] <jayteeuk> geser: No problem.  Thanks for all your help and patience. :)
[12:01] <jayteeuk> Darn, Gnome Terminal is sorely missing a "select all" option. :)
[12:02] <jayteeuk> OK, thanks all.
[12:03] <jayteeuk> And goodnight!


[02:02] <alefteris> hi everyone! how can I doublicate a selection with gimp?
[04:33] <alefteris> where can I find the background image that is used behind the wiki logo?
[04:34] <alefteris> without the ubuntu text and circle..
[04:34] <alefteris> so that i can add my own for the loco team


[15:08] <lotuspsychje> !info tmux
[15:35] <teward> lol whoops?
[15:40] <lotuspsychje> yeah seems like no dingo yet tomreyn :p
[15:43] <tomreyn> looks like the default release is set to disco here, which is fine on this channel, and that the backend is not up to date in terms of which distros there are / will be.
[15:43] <tomreyn> people.canonical.com was down earlier today, maybe this is related
[15:44] <lotuspsychje> it was never changed tomreyn
[15:45] <lotuspsychje> tryed a few dingo triggers already in the past
[15:45] <lotuspsychje> maybe something for Pici ?
[15:46] <teward> possibly.  I prodded -irc about it too
[15:47] <lotuspsychje> tnx
[16:43] <Pici> !info tmux
[16:43] <Pici> teward: fixed
[16:44] <teward> Pici: cool, thanks.  What about all the EOL versions still coded into the bot?
[16:44] <Pici> teward: most were removed.
[16:44] <teward> cool
[16:44] <Pici> !info tmux foo
[16:44] <teward> yep that looks nicer :P  thanks Pici
[16:44] <Pici> np


[06:08] <dglass> Question: I got a package (wakeup) accepted into the oneiric repositories through REVU. How can I get the ubuntu package updated to the most recent version I have made on launchpad?
[06:10] <micahg> dglass: file a bug w/a debdiff update and subscribe ubuntu-sponsors or a branch with a merge proposed into lp:ubuntu/wakeup
[06:11] <dglass> micahg: https://bugs.launchpad.net/ubuntu/+source/wakeup/+bug/876649. Is this correct?
[06:11] <micahg> dglass: I commented in that bug already about what you need to do
[06:12] <dglass> yes, you said to come here. I didn't understand your reply, sorry I'm new to this
[06:14] <micahg> dglass: right, so, you need to version your upstream release w/out ubuntuX in it, ubuntuX should be for updates in ubuntu that are not in the upstream .tar.gz
[06:15] <micahg> so you can go 1.0.1, 1.0.2, 1.0.3, or 1.1, 1.2, 1.3 depending on how you wish to version
[06:15] <dglass> micahg: So make a release on launchpad versioned 1.1-0ubuntu1
[06:15] <dglass> and upload a diff between .deb files to the bug page?
[06:15] <micahg> dglass: no, 1.1 is fine, then we'll take that and make a 1.1-0ubuntu1 release in Ubuntu
[06:16] <micahg> the Ubuntu version is X-YubuntuZ where X is the upstream version, Y is the Debian version and Z is the Ubuntu version
[06:16] <dglass> micahg: ok, thanks. I will do this. Do you mind if I ask you here again in a few minutes to check on it after I've done that?
[06:17] <dglass> yes, it's a little confusing for me because there is no debian version. I got it accepted through REVU, so it's ubuntu only
[06:17] <micahg> sure
[06:17] <micahg> well, we use 0 when we're ahead of Debian or they don't have the package yet
[06:17] <dglass> ok, thank you.
[07:05] <dglass> micahg: I believe I have done as you suggested. I released a version 1.1 on lp:wakeup and uploaded a debdiff to the bug page (https://bugs.launchpad.net/ubuntu/+source/wakeup/+bug/876649). Could you check on this please?
[07:07] <micahg> dglass: upstream release looks good, debdiff though should target precise and close the LP bug
[07:09] <dglass> micahg: again, sorry for not understanding. If I target precise, doesn't that mean I have to change the changelog in the upstream release? Also, does that mean it won't be available in oneiric?
[07:09] <micahg> dglass: no, upstream release has no debian dir
[07:09] <micahg> the update will not be, that's correct
[07:10] <dglass> so.... my updates will go unused until next april??
[07:10] <micahg> you can request a full backport if you like (https://help.ubuntu.com/community/UbuntuBackports), or you can cherry pick fixes for an SRU (https://wiki.ubuntu.com/StableReleaseUpdates)
[07:20] <dglass> micahg: in software sources, I believe, -backports is not enabled by default, correct? Unfortunately I think there are some bugs fixed in this recent version which make the older version work improperly in a  noticeable way. Do I need to create a separate bug for a backport?
[07:21] <micahg> dglass: it is in oneiric, but it's opt in, so they'd have to select the version from there
[07:22] <micahg> dglass: well, if you want the bug fixes to go to the widest number of users, you could SRU them if they have test cases, otherwise, for a backport, file a bug against the oneiric-backports project, requirements for a backport are that the package build/install/run
[07:22] <micahg> but regardless for either option, the fixes need to be in precise first
[07:23] <dglass> micahg: ok, so first I need to change the debdiff to precise, then file a separate bug in oneiric-backports. Backports don't get automatically updated into precise?
[07:24] <micahg> no, first the package hits precise, then we can backport to previous releases
[07:32] <dglass> micahg: I reuploaded the debdiff. Does this look good?
[07:33] <micahg> dglass: looks good, thanks, just reset the bug to confirmed now and it'll be in the queue for the sponsors
[07:34] <dglass> micahg: ok, thanks a lot. Now I need to wait for it to get accepted to precise before opening a bug with oneiric-backports?
[07:35] <micahg> dglass: right, since if you open it now, it'll just be marked incomplete
[07:35] <dglass> micahg: ok, great. thanks for all the help, I really appreciate it
[07:36] <micahg> dglass: you're welcome and thank you for contributing to Ubuntu development
[07:56] <dholbach> good morning
[07:57] <tumbleweed> morning
[07:58] <broder> does anybody have a config snippet i could steal to run sbuild under eatmydata?
[07:58] <tumbleweed> broder: command-prefix=eatmydata
[07:59] <broder> is that...an schroot option?
[07:59] <broder> ah, yes, it is
[08:00] <broder> ...is there a compelling reason i shouldn't set that on all of my chroots?
[08:01] <tumbleweed> not that I know of
[08:02] <tumbleweed> (of course you can only do it when eatmydata is installed in the chroot)
[08:02]  * broder goes and files a mk-sbuild bug to add an --eatmydata option :)
[08:02] <tumbleweed> well, obviously, only do it for throwaway chroots
[12:38] <tumbleweed> broder: I'm playing with using a normalised schema for the rdepends database. That will allow more interesting queries (like main-only, which reverse-build-depends could do)
[12:38] <tumbleweed> also, collapsing all binary archs into one. I don't see any point in keeping them separate
[12:40] <geser> tumbleweed: so you don't have any information anymore which are still has that reverse depends?
[12:41] <geser> wouldn't that cause confusion why a reverse depends is listed if one checks on the "wrong" arch?
[12:43] <tumbleweed> geser: for most purposes, you want to look at all rdepends, right?
[12:44] <tumbleweed> if they are only on one arch, maybe it should show that
[12:45] <Laney> nbs
[12:45] <tumbleweed> Laney: eh?
[12:49] <RainCT> tumbleweed: "not build from source"
[12:49] <tumbleweed> RainCT: yeah, I know what it means. I'm asking what he means
[12:50] <tumbleweed> is seeing nbs packages in rdepends a problem?
[12:50] <Laney> that is when you might have skew
[12:50] <Laney> gotta go teach
[12:50] <tumbleweed> sure, but a union of all archs rdepends
[12:50] <Laney> you might care which arch
[12:50] <Laney> really gotta go!
[12:51] <tumbleweed> ok, I'll move the aggregation to client-side
[13:05] <geser> tumbleweed: I'm not sure if it's a problem for the use-cases you intend? could it also be used for unmet deps?
[13:07] <geser> in case of archive skew, it might be helpful to know that a reverse dependency only exists on a specific arch
[13:08] <geser> (to avoid questions like is the script buggy because apt-cache doesn't show this dependency)
[13:10] <tumbleweed> geser: well, might as well make it as widely useful as possible
[15:29] <blair> micahg, debian responded to hdf5: http://lists.debian.org/debian-gis/2011/11/msg00002.html, what's your take on the response?
[16:01] <tumbleweed> blair: I don't know how hard hdf transitions usually are, but I'd suggest test building all the reverse dependencies against the new version, if it's something you want to persue
[16:04] <blair> tumbleweed, thanks, the pure 1.8.4 to 1.8.7 is just a recompile, but debian has redone their packages since, so there may be more work there
[16:05] <tumbleweed> blair: oh, right no ABI change
[16:05] <tumbleweed> (or is there?)
[16:05] <tumbleweed> ah, there is
[16:05] <tumbleweed> blair: my question is, will everything recompile?
[16:06] <blair> there are unintentional ABI changes, but the code is source compatible
[16:06] <blair> yes, it should just recompile
[16:06] <tumbleweed> right, but there are packaging changes
[16:07] <tumbleweed> so, it's still a question of how much work will this be. We wouldn't want to start it if we couldn't finish it
[16:07] <blair> right
[16:08] <blair> that's why i'm thinking at minimum, just take the existing 1.8.4 packages in ubuntu and update them to 1.8.7, ignoring the packaging changes
[16:26] <geser> blair: why would it be easier to upgrade the packages ourself instead of using the version from experimental?
[16:28] <blair> geser, i presumed from tumbleweed's question that they packages may not be fully completed yet and ready to be promoted to debian unstable
[16:28] <blair> geser, if they are in good shape, then yes, sync/merge them over
[16:28] <blair> does ubuntu ever take experimental packages?
[16:28] <geser> yes, if there are good reasons for them (just not by default)
[16:30] <geser> from the message you linked the DD are just waiting on a transition slot from the Debian release team (to avoid mixing several transitions into one big chunk which makes it hard for the packages to move into testing as all need to be ready at the same time)
[16:32] <blair> i'm not that familiar with debian/ubuntu release process, so does that imply that the packages are basically ready and in good enough shape?
[16:33] <blair> do you suggest waiting for them to make the transition to unstable before merging into ubuntu?
[16:39] <tumbleweed> blair: it means that they think they are ready
[16:39] <tumbleweed> the release team may not agree
[16:39] <tumbleweed> you can ask the release team what they think
[16:40] <blair> tumbleweed, where/how do i ask the release team?
[16:40] <tumbleweed> but presumably, if they think they are ready the packaging changes for all the reverse dependancies should be staged in VCS / experimental
[16:48] <micahg> blair: we can't upgrade the package as is due to the ABI break, so changes would be needed, also being out of sync with Debian WRT to the package names will make keeping in sync harder in the future and leave us with a diff we'd have to carry until the next LTS (14.04), so not a good idea for the most part
[16:51] <tumbleweed> Laney, geser: there: http://qa.ubuntuwire.org/rdepends/v1/precise/any/bash (see also s/any/source/ s/any/i386/ etc )
[16:51] <tumbleweed> of course my client needs updating now...
[16:52] <Laney> good stuff
[16:53] <Laney> are you using udd?
[16:53] <tumbleweed> no. That's a highly normalised sqlite db
[16:53] <tumbleweed> see lp:~stefanor/+junk/reverse-deps/
[16:53] <Laney> normalisation!?!?!?!?!?!?!
[16:54] <tumbleweed> turns out you can make useful queries when it's normalised :P
[16:55] <tumbleweed> it also got a lot smaller, but then people wanted more information, so it got back to about the same size it used to be before normalisation
[16:55] <Laney> someone should normalise udd and make compatibility views for the old stuff
[16:55] <tumbleweed> or just add extra normalisation tables
[16:56] <tumbleweed> this stuff tends to be quite hard to normalise, though. One has to cut corners
[16:56] <tumbleweed> bug relationships are already reasonably normalised in UDD, except that merged bugs still makes it a nightmare to query
[16:58] <tumbleweed> blair: sorry enever answered you. The debian release team hangs out in their channel on OFTC. Of course it's not their job to advise us about our transitions, though :P
[17:00] <blair> tumbleweed, there's multiple debian channels, is there one specific one where the release managers are in?
[17:00] <tumbleweed> #debian-release
[17:01] <tumbleweed> you can ask where it is in the queue, and if they've done any research into how hard it'll be
[17:01] <blair> ok, thanks
[17:10] <geser> blair: thanks for sticking to get it done (and chasing all needed information)
[18:51] <aboudreault> hi. with quilt... what's the proper way to edit a patch... it looks like dh_quilt_patch is too simple
[18:51] <broder> aboudreault: it's usually easiest to use quilt push/pop to get to the patch, then edit the files you want to change, then run quilt refresh
[18:52] <aboudreault> broder, but quilt is not aware of the debian directory
[18:52] <aboudreault> it tries to execute in the current dir
[18:52] <broder> aboudreault: echo QUILT_PATCHES=debian/patches >~/.quiltrc
[18:54] <aboudreault> broder, thanks, will try this way
[19:42] <EvilResistance> broder:  around?
[19:42] <broder> yes, what's up?
[19:42] <EvilResistance> re: backport of ZNC.  i noticed it was put into oneiric?
[19:43] <EvilResistance> no progress on natty, yet, i assume?
[19:43] <broder> i've uploaded the natty backport, but an archive admin still needs to accept it from the queue
[19:43] <broder> and process the swig backport
[19:44] <EvilResistance> i see.
[19:44] <EvilResistance> wasnt sure ;P
[19:44] <EvilResistance> i'll leave ya be then :P
[19:45] <broder> i try not to harass the archive admins too much, but i can start bugging people if it isn't handled by the end of the week. there are a few other pending backports as well that should be seen to
[19:46] <micahg> broder: it'll be blocked on Bug #888665 most likely
[19:46] <broder> oh, ugh. yeah, you're right
[19:46] <broder> i...was just looking at that bug but it slipped my mind :)
[19:50] <EvilResistance> heh
[19:52] <EvilResistance> perhaps the LP admins should *fix* that before the natty backport :/
[19:52] <EvilResistance> (in the mean time, the backports i did within my own PPA seem to be working :P)
[19:53] <broder> yes, ppas work differently from the actual backports pocket in that regard
[19:53] <EvilResistance> i'm curious... i take it that an already-built backport within a PPA cant be pulled into the standard ubuntu archive?
[19:53] <EvilResistance> or something similar
[19:54] <EvilResistance> because if its already been built elsewhere, shouldnt that in theory invalidate the need for the backported build-deP?
[19:54] <EvilResistance> build-dep *
[19:55] <broder> we do that for a couple of special cases - kernels and security updates in particular
[19:56] <broder> if asked, the archive admins could probably do that for backports, but i don't want to do that unless it looks like the launchpad issue just isn't going to get fixed in a reasonable amount of time
[19:56] <EvilResistance> ok
[19:57] <EvilResistance> but fwiw, define "reasonable amount of time"
[19:57] <EvilResistance> (since "reasonable" is relative)
[19:57] <EvilResistance> ;P
[19:59] <broder> not entirely sure. i'd at least like a few days to figure out what our plan is
[20:04] <EvilResistance> broder:  ok i'll leave you be then.  if all else fails though you all are free to pull the built binaries from my backports ppa.
[20:05] <micahg> EvilResistance: not really, we must build from source :)
[20:05] <EvilResistance> :P
[20:05] <EvilResistance> micahg:  then the bug needs fixing :P
[20:06]  * EvilResistance attends to his glitchy DNS server
[20:08] <EvilResistance> micahg:  the alternative is that i just tell all the Natty users who need the updated znc package to use my ppa :P
[20:09] <micahg> EvilResistance: heh, I appreciate you trying to DTRT, we'll try to get this sorted
[20:10] <broder> micahg: if it turns out that this will take a while for the lp team to sort out, i would support doing a copy from a properly-configured backporters PPA or something into the archive. we'd have to see if the archive admins would go for it, though
[20:10] <broder> but i don't think we're at that point of desperation yet
[20:10] <micahg> broder: I wouldn't
[20:11] <micahg> but then I'm super paranoid :), also that would only build on i386 and amd64
[20:11] <broder> hmm, that's true. but that's also something we could deal with
[20:15] <EvilResistance> As i was going to add to my statement before i got so rudely bumped from campus internet...
[20:15] <EvilResistance> ... which looks bad on ubuntu for not backporting when it was backported to oneiric (note that unlike you and I, linux newbies or those not sufficiently acquainted with linux-fu and packaging-fu won't understand there's a bug preventing the build)
[20:21] <broder> EvilResistance: right, and we'd rather do this using backports than have you handing out a PPA. just give us a little while to figure out what our options are - we're just now finding out about this
[20:25] <EvilResistance> okay, i'm going to slap my campus now... that's the 5th time today i've been bumped from that wireless AP
[20:26] <EvilResistance> broder:  indeed.  dont take what i said as rude (i was just making a statement is all... as well, my internet is glitchy today so sorry about the interruptions in the string of thoughts :P)
[20:27] <broder> EvilResistance: yeah, i understand, and i know it's frustrating (i've been on both sides of this process too)
[20:27] <EvilResistance> :P
[21:38] <lfaraone>  So package pithos is in sid, see <http://launchpad.net/debian/+source/pithos>. But running «syncpackage pithos» on my oneiric machine gives me "ubuntutools.lp.udtexceptions.PackageNotFoundException: The package 'pithos' does not exist in the Debian primary archive in 'sid'". Any idea what gives?
[21:42] <jtaylor> its probably only looking in testing
[21:42] <jtaylor> lfaraone: ^
[21:45] <lfaraone> yeah, but: $ rmadison -u qa pithos
[21:45] <lfaraone>  pithos | 0.3.11-1 | wheezy | source, all
[21:45] <lfaraone>  pithos | 0.3.13-1 | sid    | source, all
[21:46] <bdrung> lfaraone: that's what the latest version says: $ syncpackage pithos
[21:46] <bdrung> syncpackage: Error: Version in Debian 0.3.11-1 (testing) isn't newer than Ubuntu 0.3.11-1 (precise)
[21:48] <lfaraone> bdrung: ah, I'll use the version from trunk then with -d sid


[02:22] <TylerCardon> Hi!
[02:23] <zequence> TylerCardon: Hi
[02:23] <TylerCardon> I'm interested in developing
[02:23] <zequence> TylerCardon: Cool.
[02:24] <zequence> I'm the project lead. Not many people involved atm. Lots of room for lots of things
[02:24] <TylerCardon> Sweet
[02:24] <zequence> Mostly up to you
[02:25] <zequence> You want any information at all, you can always ask me. I'm not in 24/7, but my client is, so I might take some time to answer
[02:26] <zequence> client being a raspberry PI with a creen IRC client on it
[02:26] <TylerCardon> Do people choose from available fixes or projects or is it mostly delegated?
[02:27] <holstein> there can be delegation
[02:29] <holstein> but, right now, things are more like, "as needed"
[02:29] <holstein> should/could be developement meetings, etc..
[02:29] <TylerCardon> I use CentOS and Debian at work so I am new to Ubuntu, but am interested in multimedia applications or kernel
[02:29] <holstein> if the team developed..
[02:30] <zequence> TylerCardon: Most of what we have is directly imported from Debian
[02:30] <zequence> The kernel is specific to Ubuntu. We maintain linux-lowlatency, or at least the diff compared to linux-generic
[02:31] <zequence> Compared to Debian, there is some difference in kernel maintenance
[02:31] <holstein> we, being zequence
[02:31] <zequence> Well, we being the Ubuntu Studio Kernel Team, which for now, is me
[02:33] <holstein> well, its you and TylerCardon , looks like
[02:34] <zequence> TylerCardon: Anyway, you should know that any at all input or interest you have is more than welcome here.
[02:34] <zequence> There are things to learn, of course.
[02:34] <zequence> And, for that, there is the wiki, and us who are here, mainly me.
[02:34] <TylerCardon> Are there any introductory projects I could help with? I am downloading 14.04.2 and installing on a virtualbox
[02:35] <zequence> https://wiki.ubuntu.com/UbuntuStudio
[02:35] <zequence> TylerCardon: Testing is probably the most introductionary there is
[02:36] <zequence> We just finished testing beta1 for vivid
[02:37] <zequence> To try to explain the whole thing simply:
[02:38] <zequence> We decide on what packages end up on our ISO. The choice is mostly on covering workflows, not making sure everything ever ends up there
[02:39] <zequence> We have the opportunity to simplify the experience for users
[02:39] <zequence> ..and for that we are able to use all our creative freedom - coding, as well as packagin
[02:40] <zequence> We don't package software for Ubuntu, if it can not be packaged Debian
[02:40] <zequence> Most of the work is actually done in Debian
[02:40] <zequence> In particular, the Debian Multimedia Team
[02:40] <zequence> If you want to help with packagin, make sure to look that up, and become a member.
[02:41] <zequence> Any packagin work should be done in Debian first, if possible, so that all Debian based can make use of it
[02:41] <zequence> Makes sense, right?
[02:42] <zequence> We could make more updates to packages, as long as someone is willing to do the packagin work
[02:42] <zequence> Sorry for the missing g's. Not sure why they seem to fall out.
[02:42] <TylerCardon> Yeah that all makes sense
[02:44] <zequence> TylerCardon: Getting a bit late for me today, but hope to see you around. If you have any questions, you can write to me personally on irc, or email, or on this channel, or on mail lists, or whatever. All good
[02:44] <TylerCardon> Ok thanks for your time
[02:44] <zequence> no problem at all
[02:49] <zequence> TylerCardon: Oh, most of what is documented is here https://wiki.ubuntu.com/UbuntuStudio
[02:49] <zequence> It's not documented well, but it's what there is
[02:50] <zequence> Some of it outdated.
[02:50] <TylerCardon> Ok


[02:18] <ryanakca> kwwii: ping
[02:19] <ryanakca> kwwii: quick question, http://rkavanagh.homelinux.org/~ryan/kubuntu/1.png  , should I add two lines at the bottom next to the motto like I did at the top? or not?
[02:19] <ryanakca> don't worry, that's just the text part, I'll colorize and emboss and add the logo and all that good stuff :)
[02:20] <kwwii> ryanakca: yes
[02:20] <ryanakca> kk
[11:42] <ppd> hi
[12:34] <PingunZ> morning all
[12:42] <klepas> moin
[03:32] <Viper550> Our Usplash bug (that may have gotten rid of the ugly placeholder) got rejected!
[03:32] <Viper550> https://launchpad.net/bugs/64819
[03:32] <Ubugtu> Malone bug 64819 in usplash-theme-ubuntu "[Edgy]  Usplash should use black background" [Wishlist,Rejected]
[03:38] <Viper550> Our Usplash bug got rejected...
[03:47] <Viper550> anyone here?
[03:54] <troy_s> it is
[03:54] <troy_s> _your_ bug
[03:54] <troy_s> the placeholder was just that
[03:54] <troy_s> temp art
[03:54] <troy_s> deal with it.
[03:54] <Viper550> but still, even Breezy had feasable placeholders (just plain using Breezy's art)
[03:54] <Viper550> I mean Dapper
[03:55] <troy_s> IT DOESNT MATTER
[03:55] <troy_s> it was temp
[03:55] <troy_s> so bickering over it is a complete waste of time for yourself, the developers, and everyone who has to read the letters.
[03:55] <PingunZ> O_o
[03:55] <troy_s> there are far more important things to be exerting your energy on
[03:56] <troy_s> and always remember
[03:56] <troy_s> _everything_ in the world is relative
[03:56] <troy_s> if you don't believe me read something some fellow named einstein said about some general theory of something er other.
[03:56] <Viper550> I know, but this isn't the first time we've complained about temp artwork. Remember back in Dapper?
[03:56] <troy_s> which means terms like 'ugly' simply do not exist.
[03:56] <troy_s> who cares.
[03:56] <troy_s> its temp
[03:56] <troy_s> no one cares.
[03:56] <troy_s> get over it.
[03:56] <PingunZ> rof
[03:56] <PingunZ> *rofl
[03:57] <troy_s> it is purely an exercise in attention deficit disorder.
[03:57] <troy_s> In fact, let's put a poll up on the forums
[03:57] <troy_s> and decide what your handle should be
[03:57] <Viper550> But, people in the community are actually complaining about it!
[03:57] <troy_s> or how you should put an extra 0 on your name
[03:57] <troy_s> or change it to asp001
[03:58] <troy_s> so what
[03:58] <troy_s> SOME people might complain
[03:58] <troy_s> SOME people might love it
[03:58] <troy_s> it is all totally irrelevant
[03:58] <Viper550> http://www.ubuntuforums.org/showthread.php?t=275477&highlight=Usplash
[03:58] <troy_s> _who_ _cares_
[03:58] <Viper550> "The artwork for USplash in Dapper is excelent, while the in Edgy it is gawdy and annoying"
[03:58] <troy_s> yah great
[03:58] <troy_s> one person
[03:58] <troy_s> terrific
[03:58] <troy_s> no one cares
[03:59] <troy_s> and the more you cry wolf, the less chance _anyone_ will listen to you
[03:59] <troy_s> Your energy would be more well spent if you focused on attempting to communicate with your computer without using an interface such as a mouse or a keyboard.
[03:59] <troy_s> Brain waves perhaps.
[04:00] <troy_s> The bottom line -- it is _temp_ art.  Subsection 2.2a.32 -- No one cares.
[04:00] <Viper550> 10 people counted so far...
[04:00] <troy_s> So, put a poll up on the forums and see how many people like your handle.
[04:00] <troy_s> GREAT
[04:00] <troy_s> now divide that by six billion
[04:00] <troy_s> and see if you can count the decimal places
[04:01] <troy_s> It is completely, utterly, and irrovocably irrelevant.
[04:01] <PingunZ> troy_s, chill out m8
[04:01] <troy_s> But thanks for putting the profound "...(and is ugly)" my mailbox.
[04:01] <troy_s> I am quite chill actually. :)
[04:02] <PingunZ> Well, to be honest, I prefer the Edgy usplash to the dapper one
[04:02] <Viper550> (okay, I'll remove that part)
[04:02] <troy_s> NO
[04:02] <troy_s> Just sit on you hands.
[04:02] <troy_s> your hands
[04:02] <troy_s> Every time you change I get mail
[04:03] <PingunZ> Indeed
[04:03] <PingunZ> Viper550, You could let it go and try to focus on edgy+1 like me.
[04:03] <Viper550> I added artwork team to it because this is an art problem
[04:03] <troy_s> Travel the world and attempt to seek out change on the placeholder theme.
[04:03] <PingunZ> Edgy's art will be screwed anyway :)
[04:04] <troy_s> By the time you have conducted a poll on every one of the six billion
[04:04] <troy_s> Someone might listen.
[04:06] <Viper550> LjL just left a good argument...
[04:09] <Viper550> hello
[04:09] <LjL> hi
[04:10] <Viper550> Ljl just made a big comment on my bug, could you give us just the jist of it for troy s here?
[04:12] <LjL> well, i believe the boot-up splash screen should have a black background - the reasons are mainly 1) uncentered screens are quite evident with a colored background (and they're very common), not so with black 2) the boot process necessarily has stages during which the screen is blank, so having a black background makes everything much smoother
[04:14] <PingunZ> Goto go, installing arch linu
[04:14] <PingunZ> *linux
[04:15] <Viper550> cool, Arch Linux
[09:13] <ppd> hi
[10:51] <Viper550> I can't believe we had to "throw away" months of work!
[11:38] <Viper550> Everyone, I have one final plan for getting new art in Edgy
[11:48] <Viper550> anyone?
[11:49] <Viper550> troy_s?