[00:04] <coppro> okay, I need some assitance
[00:05] <coppro> how do I make dpkg-buildpackage find my .orig.gz file
[00:09] <coppro> I can't get it to generate a diff.gz no matter how hard I try
[00:09] <azeem> the .orig.gz has to be in the parent directory from where you're running dpkg-buildpackage from
[00:09] <azeem> well, orig.tar.g
[00:09] <azeem> z
[00:11] <coppro> right
[00:11] <coppro> but I still don't get a diff.gz generated
[00:12] <coppro> do I need the -1 prefix on the version?
[00:12] <coppro> also, how do I specify lintian overrides for the binary package correctly
[00:13] <coppro> like, what is the preferred file to put them in and what should I add to debian/rules?
[00:14] <cody-somerville> coppro, Yes otherwise it thinks you're building a native package.
[00:14] <cody-somerville> coppro, and what lintian overrides do you think your package qualifies for?
[00:15] <coppro> the source package includes lost of .DS_Store and ._whatever files
[00:15] <coppro> and lintian says that in a case like this, it's better to override then attempt to modify the whole source tree
[00:15] <coppro> still no diff.gz :(
[00:16] <azeem> what's your .dsc called, and what did you name the orig.tar.gz?
[00:16] <coppro> wait, I think I made a mistake
[00:16] <coppro> one more try
[00:21] <coppro> okay, so I'm not seeing it still
[00:21] <coppro> and I'm pretty sure I've got it right
[00:22] <coppro> here's my ls of the root directory after running a build
[00:22] <coppro> golly-1.3        golly_1.3-1_i386.changes  golly_1.3-1.orig.tar.gz
[00:22] <coppro> golly_1.3-1.dsc  golly_1.3-1_i386.deb      golly_1.3-1.tar.gz
[00:22] <coppro> aside from the fact that the directory has the wrong name
[00:22] <cody-somerville> What are you typing to build the source package?
[00:22] <coppro> dpkg-buildpackage -rfakeroot
[00:23] <cody-somerville> try: debuild -S -sa
[00:23] <crimsun> the directory seems to be named correctly if the upstream version is 1.3 (not that the name of the directory matters all that much)
[00:23] <ajmitch> golly_1.3-1.orig.tar.gz should be golly_1.3.orig.tar.gz
[00:23] <coppro> ok
[00:24] <coppro> thought I'd tried that already
[00:24] <cody-somerville> You need the -1 in your changelog
[00:25] <coppro> how do I install a symlink?
[00:25] <coppro> specifically, for a manpage
[00:25] <coppro> I get an error about that
[00:25] <cody-somerville> Don't you want to get your source package to build first? :P
[00:25] <coppro> yes
[00:25] <cody-somerville> Oh, it won't build the source package because of an error aobut a symlink?
[00:26] <cody-somerville> Why not show us the error?
[00:26] <coppro> yeah
[00:26] <coppro> something about irrepresentable changes
[00:26] <coppro> so I deleted the symlink
[00:26] <coppro> and I need to figure out how to specify it otherwise
[00:27] <coppro> I get a failure because it attempts to sign my files without knowing the comment I used on the key ID
[00:27] <coppro> as well
[00:28] <cody-somerville> Does your name and e-mail match what you have on your key?
[00:28] <coppro> yes
[00:28] <coppro> not the comment though
[00:29] <cody-somerville> Okay, so change your changelog or specify the key id manually.
[00:30] <coppro> ok, done
[00:31]  * cody-somerville goes for a shower.
[01:01] <RAOF> crimsun: You would be correct, sadly.  Our plugins package doesn't build the banshee plugin on the basis that it does bad things to Banshee's database (it can accidentally lock Banshee out of its own db, for example).
[01:04] <slomo> RAOF: what banshee plugin?
[01:04] <crimsun> RAOF: thanks for the clarification
[01:04] <RAOF> slomo: There is a banshee (0.13.x) plugin in the do-plugins source tarball.  It just reads banshee's DB directly, and as such tends to lock Banshee out.
[01:05] <slomo> RAOF: ah, that's bad ;)
[01:05] <RAOF> Someone (it may even be me) will write a banshee 1.x plugin soon using the new DBUS hotness.
[02:20] <bddebian> Heya gang
[02:21] <coppro> okay, so how do I put manpages for two programs symlinked to eachother? Simply symlinking in the debian folder gives me an error about an unrepresentable change.
[02:23] <ScottK> coppro: Probably you want dh_link
[02:24] <coppro> that would do it
[02:24] <coppro> do I just dh_link /usr/man/man1/prog.1 /usr/man/man1/other.1, or should I use some other method
[02:29] <ScottK> That seems generally correct.  See man dh_link to see that you got it right.
[02:30] <nxvl> ScottK: what's supposed to be done at this point of the release circle?
[02:30] <ScottK> nxvl: SRUs for Hardy and be thinking about specs for UDS.
[02:30] <nxvl> ScottK: :D
[02:31] <ScottK> nxvl: Also new package review on REVU can start, although, of course, nothing can be uploaded just now.
[02:31] <nxvl> ScottK: did you know when would be open the new repos? or where are it going to be announced?
[02:31] <TheMuso> When its open. The mailing list is up, but nothing yet.
[02:31] <ScottK> Usually it's two or three weeks after the release.
[02:31] <TheMuso> I'd say in the next two or so days, those who are responsible for it are not yet into their working week.
[02:31] <coppro> I heard it said about May 7 or 8 earlier
[02:31] <nxvl> that reminds me i need to package some packages
[02:31] <ScottK> It's done when it's done.
[02:32] <TheMuso> The first thing that has to happen though is the toolchain bits, anthing they want to change/update has to be done now.
[02:32] <ScottK> A lot of the when depends on a number of variables about how well things go.  If it's up and in place, they wan't hold back because it's not time yet.
[02:38] <coppro> wait... why isn't linda in hardy?
[02:42] <jdong> linda was removed
[02:42] <jdong> Debian decision
[02:43] <TheMuso> jdong: Thats weird. Surely StevenK would have campaigned against that.
[02:46] <coppro> ah, then you should probably take out all the packages that refer to it
[02:46] <soto> What dictates the suffix in shared object libraries? lib.so.6 versus lib.so.7, how do I change it?
[02:48] <TheMuso> soto: Are you an usptream developer of the software in question?
[02:48] <TheMuso> upstream even
[02:49] <soto> TheMuso: No, it's local
[02:50] <TheMuso> Its local?
[02:50] <soto> TheMuso: I have custom patches that I apply
[02:50] <TheMuso> soto: Right, unless those patches change the ABI/API of the library in question, the soname, i.e the number you mentioned does not need changing.
[02:50] <soto> Trying to build but the binaries are looking for the wrong library name
[02:51] <TheMuso> soto: And if they do, you will have to rebuild/modify all packages that build against that library.
[02:51] <soto> TheMuso: Yes, that's fine. How do I change it?
[02:51] <TheMuso> soto: I'm guessing you want to change it for the binaries that are building against it correct?
[02:52] <TheMuso> Building binaries against it should not matter, as long as you have a liblibrary.so symbolically linked to liblibraryname.so.number
[02:52] <TheMuso> soto: I suggest you find a guide about shared libraries, how they work etc.
[02:53] <soto> TheMuso: Okay, do you by any chance, know what specifically needs to be done. I think I'm just building it wrong.
[02:53] <TheMuso> soto: Without knowing what package, and how the package is built, I can't really say.
[02:53] <soto> The process varies between libraries?
[02:54] <coppro> ok, time for another stupid question
[02:54] <TheMuso> I don't know. Does it?
[02:54] <coppro> I have a manpage I wrote. How do I best compress it
[02:54] <coppro> I don't want to leave a compressed file in the source package, because it's a pain to edit
[02:54] <TheMuso> coppro: The manpages get compressed at package build time.
[02:55] <coppro> is there a rule for compression?
[02:55] <soto> Well seeing as how my inquiry pertained to how the naming was produced, I wouldn't know.
[02:55] <coppro> or should I just run gzip
[02:55] <TheMuso> coppro: If dh_compress is called in debian/rules, then the manpages will be compressed.
[02:55] <coppro> thanks
[02:56] <TheMuso> soto: What packages are you trying to modify, and are the patches you are using available anywhere for examination?
[02:59] <soto> TheMuso: Never mind, it's working now. Thanks.
[02:59] <TheMuso> soto: No problem.
[03:09] <coppro> where can I find a defined list of the doc-base sections? Lintian keeps complaining
[03:15] <coppro> and do I need to do anything about the new-package-should-close-itp-bug
[03:25] <ScottK> If you're packaging for Debian you should file an ITP bug and close it in the initial debian/changelog entry.  Otherwise, you can ignore it.
[03:26] <coppro> okeydokey
[03:26] <coppro> now why won't my manpage work
[03:29] <coppro> no matter what I do, lintian complains about something :(
[03:29] <coppro> and it's probably right
[03:29] <ScottK> If you run out of warnings, you can always run it with the -I flag.
[03:34] <coppro> no, that's not my problem
[03:34] <coppro> I get W: golly: binary-without-manpage usr/bin/golly
[03:34] <coppro> for some reason
[03:37] <coppro> any help to offer?
[04:15] <StevenK> TheMuso: It was my choice to have Linda removed.
[04:16] <TheMuso> StevenK: Oh ok.
[04:22] <lifeless> StevenK: linda died?
[04:23] <StevenK> I decided I didn't have that much drive to fix her any more.
[04:24] <coppro> can anyone help me install a manpage in my package? Give me step-by-step instructions, please. I've done it wrong every time so far.
[04:25] <coppro> I have a manpage written up already
[04:27] <TheMuso> coppro: Read the dh_installman manpage.
[04:28] <coppro> I have
[04:28] <coppro> multiple times
[06:23] <dholbach> good morning
[06:33] <ajmitch> hello dholbach
[07:26] <kahrytan> bug #223486
[07:26] <ubotu> Launchpad bug 223486 in ubuntu "X Crashes on Logout Applet activation." [Undecided,New] https://launchpad.net/bugs/223486
[07:48] <\sh> moins
[07:51] <emgent> heya \sh :)
[07:53] <\sh> moins emgent...
[10:05] <mrpouet> hi
[10:11] <cody-somerville> Hi mrpouet
[10:14] <mrpouet> cody-somerville, hi
[10:16] <mrpouet> i would like to help you, to pack new package in universe and multiverse branch, (i 've good knowledge in debian packagement with cdbs), where can i found request for new packages ?
[10:17] <mrpouet> all of new packages are "confirmed" ;)
[10:17] <cody-somerville> Confirmed, I believe, just means that it has been acknowledged - not that it has been packaged yet.
[10:23] <mrpouet> cody-somerville, oh, so good , i need to help other community contributor, oki i'll do that
[11:29] <rootbridge> hi all
[11:30] <rootbridge> I'm a Debian Developer and have been reviewing the ubuntu changes to my packages. I think that in a number of cases the Debian version should be synced (all Ubuntu changes were incorporated one way or another)
[11:30] <rootbridge> is this the right place to come?
[11:36] <tseliot> rootbridge: have you filed a bugreport about it?
[11:36] <laga> rootbridge: yes, that's the right place i guess :). to make your.. yeah, what tseliot said.
[11:36] <rootbridge> I didn't, anything special or just a bug report?
[11:39] <tseliot> rootbridge: I think that a bug report against your package in Ubuntu would be enough
[11:39] <rootbridge> great, I'll file those then
[11:51] <james_w> rootbridge: can I ask what the packages are?
[11:52] <rootbridge> james_w: apt-file phpmyadmin mailman mailping php-net-smtp
[11:52] <james_w> thanks
[11:53] <james_w> rootbridge: if they have been incorporated then the next time they are merged it should be turned in to a sync.
[11:54] <james_w> if the way it was incorporated is different or non-obvious then a bug report might help.
[11:54] <james_w> if you think the changes are wrong then that's obviously different.
[11:54] <rootbridge> james_w, ok. I've now filed the bug reports already
[11:55] <james_w> rootbridge: cool, thanks.
[12:12] <sistpoty|work> hi folks
[12:13] <iulian> Hey sistpoty|work
[12:13] <sistpoty|work> hi iulian
[12:16]  * siretart highfives sistpoty|work!
[12:16] <sistpoty|work> hi siretart
[12:19] <cbx33> hey guys
[12:19] <cbx33> I have someone building a set of packages for ubuntu
[12:19] <cbx33> they want a single binary file which uses two tar.gz files
[12:19] <cbx33> sorry
[12:19] <cbx33>  a single source file I should say
[12:19] <cbx33> this isn't really the done thing is it
[12:19] <cbx33> we'd create two pacakges and make one depend on the other
[12:20] <cbx33> right?
[12:20] <sistpoty|work> cbx33: I'm not too sure if I understand the scenario correctly...
[12:20] <cbx33> ok
[12:21] <james_w> cbx33: you can create a source package made of two .tar.gz. It's not pretty, but it is possible.
[12:21] <cbx33> james_w: really
[12:21] <cbx33> I may suggest to them that they put everything into one tar gz file
[12:21] <cbx33> that may work right?
[12:21] <james_w> rootbridge: thanks. I've subscribed the sponsors, so the syncs should happen once they have approved and the archive un-freezes.
[12:22] <james_w> cbx33: that would work. You can also tar the two files up inside another tar.gz, and then unpack them as part of the build.
[12:22] <cbx33> ahh yes
[12:22] <james_w> cbx33: as I said, it's not pretty, but it is possible.
[12:23] <cbx33> yes
[12:46] <soren> cbx33: It's not unheard of to have the orig.tar.gz simply contain the two tarballs. Not unpacked, but the tarballs themselves.
[12:47]  * ScottK plugs his ears to avoid hearing more of it.
[12:50] <soren> ScottK: glibc does it, for instance. evolution used to do it (AFAIR).
[13:12] <mok0> soren: does that mean you could tar up the debian/ dir in a tarball :-)
[13:13] <mok0> james_w: ^
[13:17] <mok0> Is the SRU team == MOTU release?
[13:18] <DktrKranz2> mok0: motu-sru
[13:18] <mok0> DktrKranz2: ok thx
[13:18] <DktrKranz2> and != from motu release
[13:19] <mok0> DktrKranz2: Ah, so you are one of the guys to befriend... :-)
[13:20] <DktrKranz2> heh
[13:20] <DktrKranz2> I'm mostly offline, though
[13:21] <DktrKranz2> my ISP decided to cut off my DSL without notice
[13:21] <mok0> DktrKranz2: Are you doing bad things to their net?
[13:22] <DktrKranz2> probably they use fedora :)
[13:22] <mok0> DktrKranz2: heh
[13:22] <DktrKranz2> and didn't want ubuntu stuff on their wire
[13:22] <mok0> wicked
[13:23] <DktrKranz2> so I use office connection, but I haven't any development tool here :(
[13:23] <mok0> DktrKranz2: ydrrrk
[13:28] <Creationist> Will there EVER be an advanced installer for Ubuntu that offers us the option on which packages to install?
[13:28] <RAOF> Creationist: Probably not.
[13:29] <jsgotangco> synaptic not works for you?
[13:29] <jsgotangco> ohh sorry
[13:29] <jsgotangco> :)
[13:29] <RAOF> I'm not sure I'll stake out 'never', though.  That's a long time :)
[13:29] <jsgotangco> my bad
[13:29] <james_w> what about the alternate installer in expert mode?
[13:29] <Creationist> RAOF: Do you know why?  I understand the need for simplicity for most new users, but it would certainly be nice for more advanced users to be able to quickly install a system tailored to our specs without having to make so many extra steps after the installation, you know?
[13:30] <Creationist> james_w: Yeah, that's what I would have thought would offer the options... but it isn't there.
[13:30] <james_w> There's "Select and install software" or something similar isn't there?
[13:31] <Creationist> james_w: Hmm... not that I saw.
[13:31] <Creationist> And according to RAOF, it doesn't exist yet, if ever.
[13:31] <\sh> Creationist, why not FAI ? or Kickstart? it will do what you want
[13:31] <Creationist> \sh: Not during installation, though.
[13:32] <\sh> Creationist, it helps you to install exactly what you want...and you don't need any cds anymore :)
[13:32] <Creationist> \sh: Hmm... maybe I don't know what it is lol
[13:32] <Creationist> I'll look it up.
[13:32] <\sh> Creationist, automatic installation methods
[13:32] <jsgotangco> yeah kickstart should work
[13:32] <jsgotangco> but i think he's looking something like what anaconda can do in d-i
[13:33] <\sh> anaconda is for hardware recognition, afaik
[13:33] <jsgotangco> i think that's kudzu
[13:33] <\sh> oh yes
[13:33] <\sh> anaconda, kudzu..all those redhat relicts
[13:34] <jsgotangco> :D
[13:34] <\sh> jsgotangco, but there is almost always the idea of preseeding the alternate installer
[13:35] <jsgotangco> yes preseeding should work
[13:37] <ogra> apt-get install system-config-kickstart
[13:37] <ogra> ;)
[13:37] <ogra> create preseed files for d-i wiht a gui
[13:42] <Creationist> Isn't there a DVD version of Ubuntu available somewhere?  I can't find it anywhere.
[13:42] <mok0> DktrKranz2: How do I get a SRU, file a bug?
[13:46] <Hobbsee> !dvd
[13:46] <ubotu> For playing DVD, see http://help.ubuntu.com/ubuntu/desktopguide/C/video.html - "libdvdcss2" can be found at !Medibuntu or (for Feisty and earlier) http://wiki.ubuntu.com/SeveasPackages - Try k9copy (available in !Universe) for backing up DVDs
[13:46] <Hobbsee> bah
[13:48] <DktrKranz2> mok0: if it's already open, you can reuse it
[13:48] <mok0> DktrKranz2: It's not.
[13:49] <DktrKranz2> keep in mind if it needs fixing for intrepid, consensus was to indicate how to address it once archives are open
[13:49] <DktrKranz2> so, feel free to open a new one
[13:49] <mok0> DktrKranz2: sure
[13:50] <DktrKranz2> subscribe motu-sru, provide a good test case and wait for an ACK
[13:51] <mok0> DktrKranz2: ... and then I just upload it?
[13:51] <mok0> DktrKranz2: (sorry for the stupid questions, but I am not familiar with the procedure!)
[13:52] <DktrKranz2> mok0: once a ACK has been granted, you can proceed with upload to $distro-proposed
[13:52] <mok0> DktrKranz2: Ah, so I need to put that in changelog
[13:53] <DktrKranz2> yes, used dch -D $distro-proposed
[13:53] <DktrKranz2> no $distro or $distro-updates
[13:53] <mok0> DktrKranz2: got it
[13:53] <DktrKranz2> be sure to include LP bug reference
[13:54] <DktrKranz2> or you will get a reject :)
[14:17] <DktrKranz2> mok0: is bug 223649 the one you were referring before?
[14:17] <ubotu> Launchpad bug 223649 in torque "torque-server init script fails during installation and removal" [Undecided,New] https://launchpad.net/bugs/223649
[14:20] <sebner> persia: for the new hacker group. Are testimonials a requirement or just a bonus point?
[14:20] <Kopfgeldjaeger> hi
[14:20] <Kopfgeldjaeger> could someone have a quick look at (there arent many changes to look at) my package for gtkhash? builds fine with hardy-ppa. i would like to see it in intrepid! http://nicolaispohrer.dyndns.org/packaging/
[14:21] <persia> sebner: A requirement.  Someone needs to be a sponsor for someone to be sponsored.
[14:22] <sebner> persia: kk. thx
[14:26] <mrpouet> re, filezilla-3.0.9.2 (new release is out )doesn't exist in hardy-proposed ? i didn't find it...
[14:26] <mok0> DktrKranz2: bug 223649
[14:26] <ubotu> Launchpad bug 223649 in torque "torque-server init script fails during installation and removal" [Undecided,New] https://launchpad.net/bugs/223649
[14:31] <DktrKranz2> mok0: I looked a bit at the debdiff, it ships several hypen fixes, they are minor issues not really SRU-worthy (even if barrier has been lowered recently). Also, changelog entry lacks LP: #223649 and target must be hardy-proposed
[14:32] <mok0> DktrKranz2: The hyphen fixes were asked for by persia when he uploaded the package just before new freeze
[14:33] <ScottK> mok0: Since we are post release, SRU changes should be the minimal fix to deal with the exact SRU worthy problem.
[14:33] <ScottK> mok0: Due the cleanups in Intrepid
[14:33] <ScottK> Due/Do
[14:33] <mok0> OK
[14:33] <persia> Which hyphen fixes?  (I've lost context).
[14:34] <DktrKranz2> Exactly, we can bring in -updates low impact bug fixes, but cosmetic changes are usually ignored
[14:34] <mok0> persia: ah, when you uploaded the torque package for me a few months ago, you made me promise that I would fix a number of hyphen/minus issues in the manpages
[14:35] <ScottK> Man page formatting changes should definitely just be done in Intrepid.
[14:35] <persia> mok0: Ah.  Right.  Yes.  As indicated above, those are things that ought be done in a dev release, as they aren't SRU-worthy.  Please do fix the hyphens for intrepid, and drop them from a hardy patch.
[14:35] <mok0> persia: sure
[14:36] <Kopfgeldjaeger> nobody here to look at my package?
[14:37] <DktrKranz2> mok0: just include changes which affect package direcly (e.g. broken installation fix is definitely worth it)
[14:38] <DktrKranz2> ah, version should be 0ubuntu1.1, to avoid potential conflicts with a future upload in intrepid
[14:41] <mok0> DktrKranz2: I will upload another debdiff shortly
[14:41] <DktrKranz2> great. ping me once ready :)
[14:48] <ScottK> slangasek: Today is your archive admin day, right?
[14:57] <mok0> DktrKranz2: Pinnnngggg....
[15:02] <DktrKranz2> mok0: are these errors you receive? http://paste.ubuntu.com/8506/
[15:02] <mok0> DktrKranz2: yes
[15:02] <mok0> DktrKranz2: those dirs are now a part of the package
[15:03] <DktrKranz2> ok, is linda change relly required'?
[15:03] <mok0> DktrKranz2: no
[15:03] <mok0> DktrKranz2: I can get rid of it
[15:04] <DktrKranz2> yes, please
[15:04] <mok0> will do
[15:05] <mok0> DktrKranz2: ... and you'll have difficulty removing the package again
[15:05] <DktrKranz2> without linda override?
[15:05] <mok0> DktrKranz2: no, no
[15:05] <mok0> the linda override is just cosmetics
[15:06] <mok0> DktrKranz2: you installed the package on your machine, right? Try removing it
[15:07] <DktrKranz2> mok0: I tried on a pbuilder, during apt-get phase I didn't receive any errors, but I guess I will on a real box
[15:08] <mok0> DktrKranz2: yes you would
[15:08] <DktrKranz2> I can't directly test it, but it sounds sane and you tested it
[15:08] <mok0> DktrKranz2: you need to see the debdiff w/o the linda override?
[15:09] <DktrKranz2> It's not required, if you will upload it without that
[15:10] <mok0> DktrKranz2: I discovered it yesterday when I needed the package :-(
[15:10] <DktrKranz2> but if you want to produce bugmail, I won't complain :P
[15:10] <mok0> DktrKranz2: that's what I am trying to avoid...
[15:12] <DktrKranz2> mok0: I'll ACK the bug asking to upload to hardy-proposed without linda override in. Just one second
[15:15] <DktrKranz2> mok0: done. Go ahead and enjoy uploading in unapproved queue :)
[15:16] <mok0> DktrKranz2: heh, thanks
[15:17] <DktrKranz2> don't forget to add TEST CASE in bug description to speed up verification phase by sru-verfication :)
[15:17] <mok0> DktrKranz2: you mean, how to test it?
[15:18] <DktrKranz2> yes
[15:18] <mok0> DktrKranz2: good point, I'll remember that next time
[15:18] <DktrKranz2> how to reproduce and how to test if fix is good
[15:18] <DktrKranz2> this one is trivial
[15:18] <mok0> indeed
[15:18] <DktrKranz2> but sometimes it's not
[15:19] <mok0> DktrKranz2: I should have discovered it earlier...
[15:19]  * mok0 kicks himself
[15:20] <DktrKranz2> I remember a beautiful SRU with a long road to test if everything was good
[15:20] <DktrKranz2> and TEST CASE saved my day
[15:20]  * DktrKranz2 loved plr SRUs :P
[15:21] <mok0> plr?
[15:21] <DktrKranz2> https://launchpad.net/ubuntu/+source/plr
[15:23]  * mok0 tries to locate the SRU DktrKranz2 is talking about...
[15:24] <mok0> Ah
[15:25] <mok0> nice
[15:27] <mok0> gotta run CU later...
[15:29] <DktrKranz2> 1
[15:30] <jpatrick> http://www.seqfault.de/files/hardy-thankyou.png \o/
[15:30] <Kopfgeldjaeger> is there anything special to take care of when porting packages from debian?
[15:32] <ScottK> As long as the package correctly specifies dependencies and versions, it should just be a rebuild.  If it builds/installs/ it's generally fine.
[15:32] <DktrKranz2> jpatrick: awesome :)
[15:33] <ScottK> It took a while to find it, but I'm in there, which is totally cool.
[15:34] <jpatrick> ScottK: I think they got the names from the ubuntu-members team
[15:35] <jpatrick> but yeah, it is cool
[15:35]  * ScottK was guessing from hardy-changes.
[15:35] <exodos_> hi there, whats the correct way to create /var/log/myproject directory is my deb package? should I use postins script or just include create this dir under debian/tmp ?
[15:39] <persia> exodos_: Either create in postint, or check & create in init.d
[15:40] <james_w> persia: /var/log isn't tmpfs is it?
[15:40] <persia> james_w: Not by default, no.
[15:40] <james_w> so shipping it in the package would be better, no?
[15:41] <persia> On the other hand, if the user mistakenly deletes the entire directory when cleaning up log files, having the directory recreated is more robust than failing to write to the log (or failing to start).
[15:42] <persia> I don't like to ship anything under /var in the package, if it can be avoided, but that's a personal opinion.  I think packages should be fine with /usr and /etc (with perhaps some limited exceptions for /bin or /lib).
[15:42] <james_w> true, and moving everything to init scripts would make it easier to switch to tmpfs or similar for other things
[15:43] <Kopfgeldjaeger> when will the hardy repos be opened?
[15:43] <Kopfgeldjaeger> eeer intrepid
[15:43] <ScottK> Never
[15:43] <ScottK> Soonish.
[15:43] <persia> Well, I can't imagine any use case where use tmpfs for /var/log would be correct, but maybe.
[15:43] <ScottK> It's usually  1 - 3 weeks after the release
[15:43] <Kopfgeldjaeger> k
[15:44] <ScottK> Depends on how long it takes them to get the toolchain in place.  They'll be working on it now.
[15:44] <jpatrick> Kopfgeldjaeger: it's open, just needs toolchain
[15:46] <persia> Well, it's currently frozen (although it exists).
[15:58] <ScottK> Interesting read: http://contentconsumer.wordpress.com/2008/04/27/is-ubuntu-useable-enough-for-my-girlfriend/
[16:03] <Hobbsee> ScottK: no.  i'ts not.  girls can't use ubuntu, and don't exist on hte intarweb.
[16:03] <ScottK> Hobbsee: OK.  The title and some of the underlying assumptions about gender are poor.
[16:03]  * Hobbsee hasn't read it yet
[16:03] <mbt> Hobbsee: Both of my girlfriends use Ubuntu... :)
[16:04] <ScottK> Just mentally substitute my 73 year old father for girlfriend and it'll work out.  He wouldn't do as well as she did I don't think.
[16:05] <ScottK> Although for a person of his age, he's pretty computer literate.
[16:05] <persia> underlying assumption about gender?  I don't see anything that would prevent the article being "Is Ubuntu useable enough for my boyfreind?", except that one might s/Erin/Aaron/
[16:06] <sistpoty|work> well, my gf knows ubuntu (or rather gnome) better than I do actually *g*
[16:08]  * Hobbsee also has a non-technical friend working her way thru ubuntu, who does'nt appear to have problems.
[16:09] <ScottK> Cool.
[16:09] <\sh> ubuntu is linux for human beings...what is a non-technical friend then? ;)
[16:09] <\sh> are technical people non humans?
[16:09] <ScottK> The one in there that I think really ought to (and can) be managed much better is Firefox jumping to the Adobe web site to offer a Flash download.
[16:09] <mbt> Well, us "mere mortals" have to be able to use something... :)
[16:10] <ScottK> Surely we could manage to point that at one of the repository flash packages.
[16:10] <persia> I'd argue that having applications be usefully aware of resolution and DPI is another reasonable target.
[16:10]  * \sh can't use windows actually...really...I have problems with the installation in general
[16:10] <persia> (especially the resolution control tool)
[16:10] <sistpoty|work> \sh: you're not alone there ;)
[16:11] <\sh> persia, did you read the thread on wine-devel ml about "wine and 400 DPI" ? ,-)
[16:11] <persia> \sh: No, I don't follow wine.  Link?
[16:11] <\sh> persia, moment...I just have it on my imap
[16:12] <\sh> persia, http://www.winehq.org/pipermail/wine-devel/2008-April/065213.html and following
[16:12] <ScottK> YokoZar: I was wondering if you've looked at the wineconfig program included in kde-guidance and if you think it's a useful thing to have?
[16:16] <persia> \sh: Looks like a repeat of the standard discussion.  Unfortunately, the current libraries tend to make assumptions about the physical size of a pixel, and so most developers end up with distances measured in pixels, which look really bad on alternate hardware.  For GNOME, the current decision is that all screens are 96DPI, regardless of the actual physical characteristics.
[16:17] <persia> This is of course different from the resolution control tool not knowing that it only has 400 vertical pixels, and appropriately adjusting the interface.
[16:25] <slangasek> ScottK: nominally yes, but I'm off today and moving house
[16:26] <ScottK> slangasek: OK.  Good luck with the move then.
[16:29] <slangasek> thanks, need it :)
[16:32] <sistpoty|work> DktrKran12: what's the next step for SRUs, once it's uploaded to -proposed? Is there still a time limit when it may enter -updates (as StableReleaseUpdates on the wiki doesn't seem to contain one)
[16:33] <jdong> sistpoty|work: 2-3 ACKs from unique users
[16:33] <persia> I've seen the archive admins pull them after a few months.
[16:33] <jdong> sistpoty|work: if that's not achieved within a reasonable amount of time, archive admins will pull the update
[16:34] <sistpoty|work> jdong: ah, thanks... so does bug #208666 qualify to be ready for -updates yet? and if so, is it copied by archive admins or do I need to upload it to -updates?
[16:34] <ubotu> Launchpad bug 208666 in xmms-crossfade "audacious crashed with SIGSEGV in g_type_check_instance_cast()" [Medium,Fix committed] https://launchpad.net/bugs/208666
[16:35] <jdong> sistpoty|work: that looks like it's been ACKed adequately...
[16:35] <sistpoty|work> (strange, but LP doesn't show me who set verification-done... or I'm blind again *g*)
[16:35] <jdong> interesting
[16:36] <jdong> sistpoty|work: yeah it's marked correctly
[16:36] <jdong> the archive admins should copy it to -updates
[16:36] <jdong> soon. ish.
[16:36] <sistpoty|work> jdong: ok, thanks!
[16:40] <ScottK> sistpoty|work: Archive admins copy directly from -proposed to -updates now.  No need to re-upload.
[16:40] <sistpoty|work> ScottK: thanks, I've just asked on -devel :)
[16:51] <DktrKran12> sistpoty|work: basically someone from sru-verification needs to check if fix is good (for universe/multiverse, it'susually me), but sometimes two/three "thumbs up" are enough for a-a to move to -updates
[16:53] <DktrKran12> sistpoty|work: crossfade will be published to -updates after sevend days elapsed
[16:53] <DktrKran12> minimum waiting period is preserved to avoid last-minute regressions
[16:53] <sistpoty|work> DktrKran12: ah, so there still is a delay? maybe the wiki should be updated then?
[16:54] <DktrKran12> I think there's already
[16:55] <DktrKran12> at least, there was
[16:57] <DktrKran12> https://wiki.ubuntu.com/StableReleaseUpdates?action=recall&rev=82 named "and passed a minimum aging period of 7 days", newer versions no longer name it...
[16:58] <sistpoty|work> yeah... that's why I was asking
[16:59] <DktrKran12> so, it's better asking. I usually leave packages in -proposed at least seven days before attempting to check them, perhaps recent SRU change turned off this requisite
[17:00] <sistpoty|work> well, I don't mind for xmms-crossfade too much :)
[17:01] <DktrKran12> probably people from that 32 dupes do :)
[17:01] <sistpoty|work> heh... and there should really be no regression, since there are no code changes :)=
[17:01] <Kopfgeldjaeger> hm. how to tell dch how my email address is?
[17:02] <sistpoty|work> Kopfgeldjaeger: export DEBEMAIL (e.g. DEBEMAIL=Stefan Potyra <sistpoty@ubuntu.com>)
[17:02] <DktrKran12> it's hard to break something fully broken already, sounds good :)
[17:02] <persia> Kopfgeldjaeger: EXPORT DEBEMAIL="Appelation Surname <account@provider.tld>"
[17:02] <Kopfgeldjaeger> thanks. already tried it, but without the name :)
[17:04] <ScottK> Who in the world decided puiparts was a good first topic for open week?
[17:05] <DktrKran12> ScottK: our desire to have at least one run for universe in Intrepid development cycle :)
[17:06] <ScottK> Well I think having it first when the people in the chat channel are asking about stuff like "How do I make a .deb" wasn't such a great plan.  It's a rather advanced topic.
[17:06] <RainCT> hi
[17:06] <sistpoty|work> hi RainCT
[17:06] <ScottK> Hello RainCT
[17:07] <DktrKranz2> persia: we are trying to have some machines to run some QA tests, let's cross our fingers :)
[17:07] <Kopfgeldjaeger> hi RainCT
[17:08] <persia> DktrKranz2: I've every confidence :)
[17:08] <DktrKranz2> I haven't, but I really want to run them at least once
[17:09] <DktrKranz2> both piuparts and AutoUpgradeTools (or equivalent)
 ﻿QUESTION: Will ﻿piuparts be run against all uploads to REVU?
[17:11] <Amaranth> Anyone know? :)
[17:11] <Kopfgeldjaeger> hmpf. now i've made 3 packages (1 new, 2 from sid) and didnt need much time. i think it would be really cool to have them in intrepid :)
[17:13] <DktrKranz2> Amaranth: piuparts requires binary packages, REVU only has sources, IIRC
[17:13] <sistpoty|work> yep
[17:15] <persia> REVU is unlikely to develop package building characteristics, unless lots more hardware is thrown at it.
[17:17] <DktrKranz2> what about having debian-style binary uploads?
[17:17] <sistpoty|work> persia: actually spooky should be fast enough to handle building, but there's a lack of revu devs rather ;
[17:17] <sistpoty|work> +)
[17:17] <Amaranth> I never thought that was a good idea
[17:17] <Amaranth> Except maybe for bootstrapping a new arch
[17:17] <Amaranth> binary uploads, i mean
[17:17] <DktrKranz2> REVU won't become a build farm and some additional lintian checks will be showed
[17:17] <persia> For REVU?  That's a possibility.  Of course, REVU runs on a Sparc, so to run piuparts, people would need to submit sparc binary uploads...
[17:17] <\sh> Amaranth, bootstraping should be done by buildd admins even for revu
[17:18] <persia> sistpoty|work: Does spooky have the disk space to run a buildd & associated infrastructure?
[17:18] <\sh> persia, actually it would be possible if we would find sponsors for hardware and ip traffic
[17:18] <persia> \sh: In that case, I'd rather see a REVU buildd than binary uploads.
[17:19] <\sh> persia, we need a fundraiser...
[17:19] <\sh> amd + a good colo housing company
[17:19] <sistpoty|work> persia: it has 72Gb reserved for package uploads, and an 18 Gb root partition, so it cannot rebuild the archives in total
[17:19] <Hobbsee> or just abuse ppa for the purpose
[17:19] <persia> Hobbsee: PPA doesn't do sparc.
[17:19] <\sh> and no hppa
[17:19] <Hobbsee> oh, bah.
[17:20] <\sh> well, having a hppa or sparc buildd wouldn't make sense, because most people don't have sparc hw or hppa hw at home
[17:20] <\sh> so building a source doesn't mean it runs as expected
[17:20] <StevenK> \sh: I have both
[17:20] <\sh> StevenK, well, there are exceptions :)
[17:20]  * StevenK grins
[17:20] <Hobbsee> StevenK: are you normal?  :)
[17:20] <persia> \sh: It would be useful for running piuparts on spooky though :)
[17:21] <StevenK> Hobbsee: Doubtful
[17:21] <sistpoty|work> well, I don't mind using spooky as a developer box too much (e.g. for pbuildering), as long as uwsa take responsibility ;)
[17:22] <DktrKranz2> debian has community boxes, it's a shame we don't (or on a limited basis)
[17:22] <persia> Depends on spooky's speed.  I remember sparky having resource contention issues between developer use and REVU.
[17:23] <sistpoty|work> persia: spooky is fast... and has lots of ram :)
[17:24] <persia> OK.  Depends on UWSA, but even just for hunting down FTBFS, it might be useful (as we're not all as equipped as StevenK)
[17:26] <\sh> DktrKranz2, debian has a lot sponsors for hardware and ip connectivity
[17:26] <DktrKranz2> \sh, yeah :(
[17:27] <ScottK> If someone wants to do a great service for hppa, what it needs is someone who cares to figure out getting that java infrastructure working.  As it is, any package with a java anything (AFAICT) will FTBFS on hppa.
[17:33]  * sistpoty|work is off home now... cya
[17:42] <ScottK> DktrKranz2: Are you still ack'ing SRU's?
[17:42] <DktrKranz2> ScottK: office time ran out, if you have a quick one, sure
[17:42] <ScottK> DktrKranz2: http://launchpadlibrarian.net/13954003/pyslide_0.4-10ubuntu2.1.debdiff and the last few comments in Bug #199014
[17:44] <DktrKranz2> ScottK: fine for me, remember to fix it in intrepid somehow
[17:44] <ScottK> Will do.
[17:45] <DktrKranz2> thanks
[17:45] <ScottK> IIRC the version in Debian doesn't actually need it anymore, but I'll get it taken care of.  Did you mark it in the bug?
[17:46] <DktrKranz2> ScottK: right now
[17:47] <ScottK> Thanks.
[17:47]  * ScottK is getting a lot of LP timeouts right now, so can't tell.
[17:48] <jdong> *sigh* I give up on Launchpad for the day
[17:48] <ScottK> I'm sure we're just not using it right.
[17:55]  * DktrKranz2 off
[18:07] <davromaniak> hi
[18:09] <davromaniak> I have a little question about the tshirt with all the names written on it, what was the condition to have his name on the shirt, because it's kind of strange that my name isn't on it, so if there was a quota of work done for hardy, I understand it.
[18:10] <persia> davromaniak: Was your name on a changelog for hardy?
[18:11] <davromaniak> ah, no, I only did bug reports
[18:12] <persia> Are you an ubuntumember?
[18:12] <davromaniak> yes, since september
[18:12] <persia> That's likely it then.
[18:12] <davromaniak> ok
[18:13] <persia> And don't discount bugwork.  Bugs are a major way in which Ubuntu is improved.
[18:14] <jdong> persia: big +1
[18:14] <jdong> bug QA'ers are my heroes here.
[18:15] <davromaniak> ok thanks persia I will ask nemphis about this
[18:16] <jdong> what is this t-shirt that people keep referring to?
[18:16]  * jdong feels lost
[18:16] <nxvl> what t-shirt with names on it?
[18:16]  * nxvl wants
[18:16]  * nixternal too
[18:17] <nxvl> davromaniak: what t-shirt are we talking about?
[18:18] <asomething> I'd imagine it's this: http://www.seqfault.de/blog/index.php?/archives/87-Einfach-mal-Danke-sagen.html
[18:18] <persia> http://www.seqfault.de/files/hardy-thankyou.png ?
[18:18] <asomething> I didn't know it was made into a t-shirt though
[18:18]  * ScottK is curious where to get this shirt.
[18:19] <persia> Well, it's an image.  Making a shirt is a matter of handing the image to your local silkscreener.
[18:19] <ScottK> Right.
[18:19] <persia> Ought cost ~5 euros for decent quality shirts in bulk.  Maybe 10 for an individual order.  Cheap shirts are about 3 (in bulk).
[18:19]  * ScottK was hoping for more of a point/click/hand over a credit card number solution.
[18:20]  * ScottK senses an entreprenurial opportunity for someone.
[18:20] <persia> Ah.  Hmm..  That takes a couple weeks to set up...
[18:20] <jdong> ScottK: likewise :D
[18:20] <persia> Anyone have a merchant account and a relationship with a silkscreener?
[18:20] <jdong> I would certainly buy one
[18:20] <ScottK> Not /me (which is why I ask).
[18:21] <nxvl> where can i can i buy one?
[18:21] <persia> jdong: If I send you contact info for a reputable silkscreener in Needham, can you organise some?
[18:21] <jdong> persia: -ENOTIME :(
[18:22] <persia> heh.  Unfortunately, the only silkscreener I've worked with is in Needham, and I'm not sure anyone else is close enough for that to matter.
[18:22] <ScottK> jdong: You belong to a loco that needs some fund raising perhaps?
[18:22] <persia> True.  Anyone in that loco ought be able to get there.
[18:23]  * persia notes that it likely also needs someone to secure the rights to the image...
[18:24] <persia> (personal use is likely fine, but fundraising / sales is likely to require paperwork, even if everyone is amenable to no charge solutions)
[18:24]  * nxvl blogs
[18:26] <sebner> I also should consider making a t-shirt. I'm also on the list ^^ xD
[18:28]  * asomething was pleasantly surprised to see his name
[18:35] <asomething> Any one have experience with registering the new x-content mime type used by the nautilus media tab? I'm trying to add ;x-content/audio-cdda;x-content/audio-player; to Exaile but it doesn't seem to show up in nautilus after installing the the package. adding a dh_desktop call didn't seem to help. Is there any thing special about this? Bug #191475
[18:35] <ubotu> Launchpad bug 191475 in amarok "[hardy] media tab in file management preferences missing applications" [Low,Confirmed] https://launchpad.net/bugs/191475
[18:38] <davromaniak> I sent an email to nemphis to know if there's a "selection"
[18:40] <coppro> is there any way to make Firefox use KDE MIME associations? If not, it might make a good package
[18:54] <mahmoud3> Hello .. May a MOTU repackage grsync from debian sid ,  this fixes LP bug #148272
[18:54] <ubotu> Launchpad bug 148272 in grsync "grsync crashes on save session" [Medium,Confirmed] https://launchpad.net/bugs/148272
[18:55] <james_w> mahmoud3: that will happen automatically once this archives open for intrepid.
[18:55] <zul> \sh: ping
[18:57]  * asomething slaps forehead when he realizes that he's just not calling dh_desktop in the right place
[18:59] <Festor> Is it possible to make a control file translatable?
[18:59] <Festor> 	
[18:59] <Festor> I refer to appear in several languages depending on the system where you install the package
[19:03] <Festor> Is it possible to make a control file translatable?
[19:03] <Festor> I refer to appear in several languages depending on the system where you install the package
[19:03] <laga> Festor: no need to repeat your question. if someone knows, they'll answer
[19:03] <persia> Festor: I don't believe the translations belong in debian/control directly (and no need to repeat yourself).  Take a look at http://www.debian.org/intl/l10n/ddtp for some pointers that might lead to you a solution.
[19:03] <Festor> sorry
[19:04] <Festor> thanks persia :D
[19:27] <Kopfgeldjaeger> if i need someone to upload some packages i made (not only now, but also later | mostly merges from debian), would it make sense to look for a mentor?
[19:29] <sebner> Kopfgeldjaeger: a mentor is not forced to upload for merges. The archives for intrepid are still so wait some days and subscribe u-u-s then
[19:29] <sebner> hey jono :D
[19:31] <sebner> argh. still closed
[19:35] <Kopfgeldjaeger> yeah, i know that a mentor isnt really for uploading. thanks.
[19:35] <ScottK> Kopfgeldjaeger: There's a sponsorship process.  I suggest following it.  People getting impatient about sponsorship is a good way to end up getting ignored.
[19:36] <Kopfgeldjaeger> (just fto be sure: the thanks was for the tip with u-u-s and not sarcastic in any way :) )
[19:36] <Kopfgeldjaeger> ok
[19:42] <Kopfgeldjaeger> So, for every package I made, create or change a bug report, set it to confirmed, upload a debdiff (?) there and subscribe u-u-s ?
[19:43] <jdong> Kopfgeldjaeger: that's correct
[19:43] <Kopfgeldjaeger> ok, thanks.
[19:44] <sebner> Kopfgeldjaeger: if the debdiff is for universe packages, yes
[19:47] <jdong> ScottK: why isn't bug 223789 valid for Ubuntu Mercurial?
[19:47] <jdong> it seems to be a wishlist/update bug
[19:48] <ubotu> Launchpad bug 223789 in mercurial "[needs-packaging] mercurial 1.0" [Undecided,Invalid] https://launchpad.net/bugs/223789
[19:48] <ScottK> jdong: It'll be auto sync'ed from Debian.  Dunno what the bug would be for.
[19:48] <sebner> Always wanted to do a FFe for it but debian never had this 1.0 version ^^
[19:48] <jdong> ScottK: ah, I was unaware the version desired was already in Debian
[19:49] <ScottK> http://ftp.debian.org/debian/pool/main/m/mercurial/mercurial_1.0-4.dsc
[20:18] <\sh> uhm? the archives are open?
[20:18] <sebner> \sh: what?
[20:19] <sebner> intrepid?
[20:19] <sebner> wth?
[20:19] <\sh> regarding intrepid-changes ...
[20:19] <\sh> or is it only the time to get the toolchain up2date?
[20:19] <sebner> damn it
[20:19] <sebner> I want to become a ubuntu member first ^^
[20:20] <ScottK> \sh: Toolchain.
[20:21] <\sh> grmpf
[20:24] <\sh> ScottK, so it's still time to relax and watchings things to come closer to a workable state...
[20:25] <sebner> ScottK: on LP intrepid is now "frozen" :) but edgy should be removed ...
[20:26] <ScottK> sebner: Give them a few days on Edgy.  It just went eol over the weekend.
[20:26] <sebner> kk. np
[20:26] <\sh> sebner, actually it should say: deprecated, please upgrade to feisty or gutsy or hardy
[20:26] <ScottK> \sh: SRUs
[20:27] <\sh> ScottK, na...-security and new crack for me :)
[20:27] <\sh> claws-mail testing :) wine on lpia
[20:27] <ScottK> leonel: I could really do with some clamav debdiffs for Feisty/Gusty ...
[20:27] <\sh> and wireshark on dapper :(
[20:27] <ScottK> speaking of security.
[20:30] <sebner> \sh: also want to add a testimonial? ^^ https://wiki.ubuntu.com/StefanEbner
[20:31] <RainCT> Do you believe? sebner impersonates MOTUs and writes bad stuff about himself -.- (https://wiki.ubuntu.com/StefanEbner, https://wiki.ubuntu.com/StefanEbner?action=info).. lol
[20:32] <sebner> RainCT: damn you ^^ wait some seconds and I have a second testimonial :D
[20:33] <\sh> hmm...
[20:33] <leonel> ScottK: sorry for the delay ,  I can do it today
[20:33] <ScottK> OK.  Great.
[20:33] <leonel> ScottK:  what happened to  bug 213500
[20:33] <ubotu> Launchpad bug 213500 in clamav "heap corruption before 0.92.1" [Medium,Confirmed] https://launchpad.net/bugs/213500
[20:33] <ScottK> leonel: I should have the Debian clamav 0.93 package today.
[20:33] <ScottK> leonel: Nothing AFAIK.
[20:34] <\sh> sebner, why did you change your nick from hellboy to sebner?
[20:34] <ScottK> I'd combine those changes with the new ones in one debdiff.
[20:34] <leonel> ScottK:  so shuld I cancel tha
[20:34] <leonel> ScottK:  ok
[20:34] <sebner> \sh: ah now you recognise me ^^
[20:34] <sebner> \sh: because it was stupid and for potential copyright issues
[20:34] <\sh> sebner, na...I knew it already...but I never had the time to ask :)
[20:35] <sebner> ah. kk
[20:35] <\sh> sebner, you mean the marvel comic and movie "Hellboy"?
[20:35] <\sh> sebner, this second class C movie? ;)
[20:35] <sebner> yeah ^^. late in 2005 I was looking for a nickname and I was young *gg*
[20:36] <leonel> ScottK: so hardy and dapper are  updated  just gutsy and feisty need patches ??
[20:36] <\sh> sebner, this guy with red skin and some horns ?
[20:36] <sebner> \sh: It's not that bad though I'm not a fan of it ^^
[20:36] <sebner> \sh: yep
[20:36] <ScottK> leonel: Hardy is fine.  Dapper is fixed in backports and I hope to convince and archive admin to copy that to updates.
[20:36] <ScottK> So please concentrate on Gutsy/Feisty.
[20:37] <\sh> sebner, well, I think I have to decline your application, because what we really need, is a red skinned devil, drinking whisky and smoking cigars and always ready to draw a really big gun ;)
[20:37] <RainCT> xDDD
[20:37] <sebner> \sh: ohh sad but I understand xD
[20:37] <RainCT> apachelogger: lol
[20:38] <leonel> ScottK:  OK
[20:38] <sebner> hrhr
[20:38] <\sh> sebner, no, IO
[20:38] <sebner> \sh: ^^. please read second testimonial
[20:38] <ScottK> sebner: Fancy looking into Bug 222486?
[20:38] <ubotu> Launchpad bug 222486 in klamav "KlamAV does not work if scanning ARJ files is enabled" [Undecided,New] https://launchpad.net/bugs/222486
[20:38]  * ScottK runs off to the bank.
[20:38]  * sebner hides xD
[20:38] <apachelogger> RainCT: \sh did it!
[20:39] <RainCT> apachelogger: with your name? o_O
[20:39] <apachelogger> ah, right, he is a whitish hat, bad excuse I guess -.-
[20:39] <sebner> ScottK: maybe on weekend. doesn't look like it now but I have to work for school ^^
[20:39] <sebner> ScottK: also want to add something?
[20:39] <ScottK> sebner: Figure the fix for that one and I'll get over my hurt feelings about not being asked.
[20:40] <sebner> ^^
[20:40]  * apachelogger gives ScottK a cookie
[20:41] <sebner> I think with that testimonial I should replace mark xD xD xD
[20:41] <RainCT> sebner: bah and you don't even apologize to ScottK. you *are* evil!
[20:41] <RainCT> *g*
[20:42] <sebner> My passion, my pleasure :)
[20:42] <\sh> apachelogger, what did I do?
[20:43] <\sh> sebner, hope it helps...and always look on the bright side of life :)
[20:44] <sebner> \sh: omg. great. xD xD xD
[20:44] <\sh> apachelogger, my testimonial is longer then yours ;)
[20:45] <\sh> it's really the time to open the archives...and not writing strange things on wiki pages ;)
[20:45] <\sh> sebner, I'm looking forward to welcome you to the inner circle of hard work and old farts, aka MOTU :)
[20:45] <sebner> \sh: hrhr
[20:46] <apachelogger> \sh: hard work? Oo
[20:46] <apachelogger> omg
[20:46] <sebner> \sh: well. this testimonial is just for the new universe contributors page ;)
[20:46] <apachelogger> none told me -.-
[20:46] <sebner> apachelogger: hrhr
[20:46] <rzr> hi guys
[20:46] <rzr> are you all running hardy ?
[20:46] <sebner> \sh: page = group
[20:46] <apachelogger> \sh: btw, it's not always the length that matters :P
[20:46] <\sh> apachelogger, well, look in the mirror, I can't even count your wrinkles anymore ;)
[20:47] <apachelogger> good point
[20:47]  * rzr thought about upgrading on n+1
[20:47] <sebner> lol
[20:47] <\sh> apachelogger, right, but I'm using sbuild, so I know the technique very well too...regarding my age and my...oh damn, I should go to bed ;)
[20:47]  * apachelogger is wondering when 8.10 development starts
[20:47] <sebner> apachelogger: some days
[20:47] <\sh> apachelogger, it already begun ;)
[20:47]  * apachelogger doesn't see it
[20:48] <apachelogger> it is hiding, that isn't a good sign IMO
[20:48] <\sh> apachelogger, don't you read hardy-plus-one-changes?
[20:48] <rzr> \sh: any url so suggest ?
[20:48] <sebner> \sh: motu candidature will come in 2-3 months but I hope I can keep your comment for it ^^
[20:48] <\sh> apachelogger, matthias and adam are already pushing the toolchain
[20:48] <apachelogger> \sh: no... that said, I should be reading maths
[20:48] <apachelogger> hoooray
[20:49] <apachelogger> oh, hold on, I will only join intrepid development in july
[20:49] <sebner> apachelogger: school doesn't matter ;) not for me and it shouldn't for you :P
[20:50] <\sh> apachelogger, hmmm...but for linuxtag you have time, right? I don't want to sleep  next to a german ,->
[20:50] <apachelogger> lol
[20:50] <apachelogger> I have a talk @ LT
[20:50] <\sh> apachelogger, ok...I think it's time to make a secret public...
[20:51] <sebner> apachelogger: about? kde, amarok?
[20:51] <apachelogger> sebner: I dunno
[20:51] <sebner> xD
[20:51] <apachelogger> Nightrose: is doing the talks I am responsible for the jokes
[20:51] <Nightrose> oO
[20:51] <Nightrose> you didn't tell me that yet honey :P
[20:51]  * apachelogger is afraid which secrets \sh might make public
[20:51] <sebner> lol
[20:52] <sebner> \sh: we hear :P
[20:52] <apachelogger> Nightrose: now you know :P
[20:52] <Nightrose> apachelogger: thx for telling me
[20:52] <Nightrose> :P
[20:52]  * \sh likes apachelogger , me fell in love with an austrian ,->
[20:52]  * apachelogger blushes
[20:53] <sebner> \sh and apachelogger sitting on a tree and kissing ... xD
[20:55] <\sh> sebner, not really...no...
[20:55] <sebner> ^^
[20:56] <apachelogger> hm
[20:56] <apachelogger> I have acrophobia or whatever the correct spelling is
[20:56] <\sh> arachnophobia?
[20:56] <laga> agoraphobie?
[20:56] <sebner> \sh = spider? hmm xD
[20:56] <laga> s/ie/ia/
[20:57]  * \sh is just afraid of stinking feet
[20:57] <\sh> ok...time to stop being funny.../me needs to fix some things on a server
[20:57] <apachelogger> http://en.wikipedia.org/wiki/Acrophobia
[20:58] <afflux> sebner: evening :)
[20:59] <sebner> afflux: aloha ;)
[20:59] <afflux> sebner: will you appear at linuxtag in berlin?
[20:59] <sebner> afflux: unfortunately not. Too far away and no time :(
[20:59] <apachelogger> pfft
[20:59] <afflux> ah, pity :(
[20:59] <apachelogger> lame excuse
[20:59] <leonel> ScottK: been thinking  about clamav  and can  we  keep the lattest  clamav for  the  current ubuntu versions  and add a dialog or alert box to the clamav package that use the backports  or  keep it on ppa  ?
[20:59] <sebner> apachelogger: yes?
[20:59] <\sh> sebner, try to get a ride with apachelogger
[20:59] <apachelogger> if I can, sebner can as well
[20:59] <afflux> hehe
[20:59] <apachelogger> \sh: I am flying most probably
[20:59] <\sh> apachelogger, bah....moneytrader you
[21:00] <apachelogger> well
[21:00] <sebner> \sh: better would be to get rid *of* apachelogger ;)
[21:00] <apachelogger> I don't know who is paying yet
[21:00] <sebner> apachelogger: amarok :P
[21:00] <apachelogger> I guess canonical could buy my for the kubuntu booth
[21:00] <apachelogger> or KDE
[21:00] <afflux> hope we'll meet at the ubuntu area then :P
[21:00] <apachelogger> otherwise I will have to work @amarok
[21:00] <afflux> juliux asked me to come and I got a suspension at school
[21:01] <\sh> apachelogger, I think we can mix it up this year :) I'll come around and show off amarok how it should supposed to be working ,)
[21:01] <apachelogger> uhh, then I can do nerdtalk @ the kubuntu booth :D
[21:02] <apachelogger> afflux: LT is great fun
[21:02] <\sh> afflux, you are suspended from school, because julius asked you to visit the linuxtag?
[21:02] <\sh> oh dear, I'm sorry..
[21:02] <afflux> apachelogger: LT?
[21:03] <\sh> afflux, LT == LinuxTag
[21:03] <afflux> ah right
[21:03] <apachelogger> there we have the nerdtalk again
[21:03] <\sh> afflux, if you would like to come to LT, please join the kubuntu-de booth, there we can have beer...not at the ubuntu-de booth, there it's forbidden to drink beer in the evening ;)
[21:04] <afflux> awawaw. apachelogger fights against me in 5-a-day, I *WONT* :P
[21:04] <afflux> well, fight is the wrong expression. He beats ubuntu-de-loco :)
[21:05]  * apachelogger doesn't even 5-a-day half his bugs :P
[21:05] <apachelogger> far too lazy
[21:05] <afflux> that's why I have this nice applet
[21:05] <apachelogger> doesn't help
[21:07] <Syntux> guys, I read in Ubuntu Newsletter that you have mentoring space now
[21:08] <RainCT> Syntux: it says just the opposite, iirc
[21:08] <laga> no mentoring available? sad
[21:09] <RainCT> btw, I'm thinking about mentoring someone.. feel free to convince me (but not now, I should be studying since hours)
[21:09]  * laga sends RainCT to studying
[21:10] <\sh> RainCT, mentor me :)
[21:11] <crimsun> cool, then \sh can mentor me :)
[21:11] <ajmitch> then crimsun can mentor me
[21:12]  * sebner is off for today. doing some work for school :(.  gn8 @ all
[21:12] <crimsun> woo!
[21:12] <afflux> sebner: good night
[21:12] <RainCT> and then ajmitch can mentor me and we get a nice loop :)
[21:12] <RainCT> gn8 sebner
[21:12] <sebner> :)
[21:13] <RainCT> well, I'm closing irssi as else I won't do anything lol
[21:13] <RainCT> good night
[21:13]  * \sh too...time to say good night :)
[22:02] <jdong> who runs the ubuntu QA blog?
[22:02] <jdong> I am a bit disappoitned the latest post to Planet from that account seems to undertone "Hardy's released, let's stop caring about it and work on the next release"
[22:02] <jdong> :-/
[22:02] <jdong> I think mentioning the point release schedule and encouraging work on SRUs wouldv'e been better
[22:10] <ScottK> leonel: No.  I want to work within the process for update to the official repository.  This would be easier if the upstream were more sane.
[22:17] <YokoZar> ScottK: I'm aware of wineconfig and it's author idles in #ubuntu-wine with me.  There's some upstream work being done on Wine (at my request) to allow configuration from the command line so we can replace wineconfig with some more generic configuration tools (eg, being able to remove Wine apps from Gnome-App-Install)
[22:18] <ScottK> YokoZar: The reason I ask is that large chunks of kde-guidance are likely to get dropped in Intrepid due to kde4 transition.  I'm trying to figure out what we want to keep around.
[22:33] <leonel> ScottK:  I agree  we need to make security patches  but can we  just recommend to use  a newer backported  clamav ?
[22:33] <jdong> leonel: I thought we were doing exactly that in hardy-backports?
[22:33] <jdong> leonel: but if they keep changing the API/ABI and needing us to rebuild our reverse deps it makes it a pain to backport
[22:33] <ScottK> leonel: My hope is to convince the archive admins to copy 0.92.1 into dapper/feisty/gutsy updates.
[22:35] <leonel> jdong:  what I mean is just  to make more clear to clamav users that it's better  if they don't get hit by a api change  to use backports
[22:35] <leonel> ScottK: lets keep pushing ..
[22:47] <Kopfgeldjaeger> n8