[12:17] <Kmos> zer: really don't know
[01:02] <eolo999> Hi ScottK 
[01:10] <zul> is there anyone not traveling to uds today
[01:12] <gouki> zul, me, unfortunately
[01:12] <eolo999> me, too
[01:13] <imbrandon> heya zul 
[01:13] <zul> hey imbrandon 
[01:18] <crimsun> zul: me four.
[01:38] <TheMuso> ScottK: You there?
[01:38] <TheMuso> ScottK: Has anybody uploaded your fix yet?
[01:39] <ScottK> TheMuso: Just got here.
[01:39] <ScottK> Not as far as I know.
[01:40] <TheMuso> Ok.
[01:40] <ScottK> Hi elmargol
[01:40] <ScottK> Oops
[01:40] <ScottK> Hi eolo999
[01:40] <eolo999> here you are
[01:40] <ScottK> TheMuso: No one mentioned on IRC they updloaded it.
[01:40] <ScottK> eolo999: Yes, here I am.
[01:41] <eolo999> lot of people waiting for you ScottK 
[01:41] <TheMuso> ScottK: Ok, I'll grab your updated diff and have a look.
[01:41] <ScottK> TheMuso: THanks
[01:41] <ScottK> eolo999: Yes.  I was out.
[01:42] <eolo999> so you had some ideas about my next class
[01:42] <ScottK> Or at least that we could look together.
[01:42] <eolo999> i was watching http://tinyurl.com/2us2se
[01:43] <eolo999> aka https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=datecreated&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Needs+Info&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Fix+Committed&assignee_option=any&field.assignee=&field.owner=&field.component=4&field.component=3&field.component-empty-marker=1&field.status_upstream=&field.status_upstream-empty-marker=1&f
[01:43] <eolo999> ield.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=bitesize&field.has_no_package.used=
[01:43] <eolo999> oops, sorry
[01:44] <ScottK> eolo999: Maybe see if you can reproduce this one (may be another 64 bit only problem) Bug #112140
[01:44] <ubotu> Launchpad bug 112140 in pythoncad "pythoncad fails to exit when all windows are closed" [Undecided,Unconfirmed]  https://launchpad.net/bugs/112140
[01:45] <eolo999> ok, i'll try to reproduce that...
[01:46] <ScottK> If you can reproduce it, I think it's worth fixing.
[01:46] <ScottK> eolo999: Make sure you use the package in the feisty-proposed repository.
[01:46] <eolo999> ?
[01:47] <ScottK> Add an entry in your sources.list for feisty-proposed and then install just that package from it and then comment it back out.
[01:47] <TheMuso> ScottK: Ok looks good. Running through pbuilder now.
[01:47] <ScottK> TheMuso: Thanks.
[01:48] <ScottK> eolo999: That's where stuff that might be released to feisty, but needs some testing sits.
[01:48] <ScottK> So you don't want to install all the stuff from that repository, just the one package.
[01:49] <eolo999> i've pythoncad Version: 0.1.33-2 in my normal sources...
[01:49] <ScottK> eolo999: The version in feisty-proposed fixes Bug #108612
[01:49] <ubotu> Launchpad bug 108612 in pythoncad "[apport]  pythoncad crashed with ExpatError in parse()" [Medium,Fix committed]  https://launchpad.net/bugs/108612
[01:49] <ScottK> You want 0.1.33-2ubuntu0.1~proposed1
[01:50] <eolo999> ok, .....
[01:50] <ScottK> If you want, just look  on your sources.list and on the line for feisty universe, change feisty to feisty-proposed, update and it should be there.
[01:51] <TheMuso> gah stupid me. Forgot to enable univese in the pbuilder chroot. :)
[01:51] <TheMuso> universe even
[01:51] <eolo999>  deb http://archive.ubuntu.com/ubuntu feisty-proposed main restricted universe multiverse
[01:52] <ScottK> Looks right to me.
[01:53] <ScottK> Just remember, install the one package you want, not all the updates.
[01:55] <ScottK> eolo999: If you can reproduce it and want to fetch the source, you'll need an equivalent deb-src line in sources.list
[01:55] <eolo999> did it...installing
[01:55] <eolo999> and sourcing
[01:57] <eolo999> working on it
[01:58] <eolo999> confirmed process permanence after closing all win
[02:00] <ScottK> eolo999: Cool.
[02:00] <eolo999> ehm, cannot test gutsy
[02:00] <ScottK> No problem.  We are fixing Feisty right now.
[02:00] <ScottK> New upstream version in Gutsy.
[02:01] <ScottK> Once you figure out the problem, look in the source in the version in Gutsy to see if the code's the same.
[02:01] <ScottK> Gotta run. Be back later.
[02:01] <eolo999> ok.
[02:02] <ScottK> Back sooner than I thought.  Might have to run on short notice.
[02:09] <TheMuso> ScottK: Uploaded.
[02:09] <ScottK> TheMuso: Thanks.  Now to go bug pitti to remember not to reject it again...
[02:09] <TheMuso> heh
[02:14] <ScottK> He's not around.  I guess I'll have to bug him later....
[02:21] <StevenK> He's probably not around because it's 2:20am in Sevilla...
[02:41] <ScottK> StevenK: That would do it.
[02:49] <ScottK> Good night all.  I think I'm calling an early night of it tonight.
[02:49] <jdong> rest up, ScottK 
[02:50] <nixternal> ScottK: you must be ill, it isn't even 9 there yet
[02:50] <nixternal> carry on shipmate
[02:50] <ScottK> Not sick, just had a REALLY bad day.
[02:50] <jdong> aww
[02:51] <nixternal> and guess what, it is here!@!#@
[02:51] <nixternal> back in a bit
[02:57] <crimsun> imbrandon: ping, would it be feasible to host a git tree on ubuntuwire for me, please?
[03:02] <eolo999> ScottK, are you there? I've good news.
[03:02] <ScottK> Yes.  Still wrapping a few things up.
[03:03] <eolo999> seems it was easy
[03:03] <ScottK> Cool.
[03:03] <eolo999> do you want me to send you the diff?
[03:03] <ScottK> Please.  I'll look at it in the morning.  I'll be here most of the day tomorrow and we can package it up.
[03:03] <ScottK> Just email it.
[03:04] <eolo999> ok , i email the diff (one word!)
[03:06] <jdong> pidgin is on alioth....
[03:14] <eolo999> sent diff and marked bug as 'in progress'.
[03:16] <ScottK> eolo999: Looks reasonable.  I'll test it and we'll package it tomorrow.
[03:17] <eolo999> our time zones are quiet different...
[03:17] <eolo999> tomorrow, when?
[03:19] <eolo999> in that function self is always an Interface instance and never an Image so the the program never entered the if block that lead to gtk.main_quit
[03:20] <eolo999> hey guys congrats me, my second bug!
[03:21] <eolo999> ScottK, What I ask my self is how could the developer miss that?
[03:21] <ScottK> Stuff happens.  The save fix I already did was just as simple.
[03:22] <ScottK> eolo999: Next step is pull the Gutsy source and see if it has the same problem.  If it does, look in the upstream svn and see if it's still there.
[03:23] <eolo999> but Ctrl-C every time you run 'your' app is quite visible...
[03:24] <eolo999> sorry the question and the lazyness. How do I get the gutsy source?
[03:28] <ScottK> eolo999: Change the deb-src line in your sources.list from feisty to gutsy, update, apt-get source pythoncad.
[03:29] <eolo999> no way to not always change apt sources?
[03:29] <ScottK> Yes.
[03:29] <eolo999> i did it from ubuntu packages and then dpkg-source -x .......
[03:29] <ScottK> That works too.
[03:30] <eolo999> ok, so i did it
[03:30] <ScottK> There is also dget too.
[03:30] <eolo999> in gutsy it's corrected the same way i did it
[03:31] <ScottK> OK.  Then that's as far as you have to look.
[03:31] <eolo999> no sorry
[03:31] <eolo999> it was my version file in the editor
[03:31] <jdong> stupid uninstallable libnss's
[03:31] <ScottK> We've all done that.
[03:31] <eolo999> it's same as in feisty
[03:31] <eolo999> the
[03:32] <ScottK> Then we'll fix it there too.  Yeah.  You get to package two fixes.
[03:32] <ScottK> More learning...
[03:33] <eolo999> i try to install and see... if it is true
[03:33] <ScottK> OK
[03:33] <ScottK> If it is, the pythoncad source is available (IIRC) from svn at their web site.  I'd check that too.
[03:34] <eolo999> confirmed bug in gutsy too
[03:35] <ScottK> Cool.
[03:35] <ScottK> Head off to the svn now.
[03:35] <eolo999> ok
[03:37] <jdong> HA! got pbuilder-satisfydeps to work on pidgin!
[03:37] <jdong> SUCK ON THAT PBUILDER!!!
[03:37] <jdong> ScottK: weren't you sleeping?
[03:37] <ScottK> In theory.
[03:37] <jdong> lol
[03:38] <jdong> I've had a few cases where I apparently had a 2 hour IM conversation with a peer about code, but don't remember it
[03:38] <jdong> "Yeah man, thanks for the ideas, I didn't know you are online at 4AM"
[03:38] <jdong> "Umm.... I'm.... not?"
[03:38] <ScottK> The key question is were you correct.
[03:38] <jdong> apparently the ideas were quite sound and inspirational
[03:38] <eolo999> downloaded svn, but i'll check it tomorrow (event today 3.40 am)...
[03:38] <eolo999> thanks ScottK 
[03:41] <ScottK> When I was in the Navy I had a job where they'd have to wake me up to make decisions in the middle of the night.  I could usually remember I'd been called, but not what the problem was or what I'd decided.  Usually, I'd just quietly go in and review the watch logs to see what I decided.
[03:42] <eolo999> seems code from svn keeps that line ?! Perhaps I AM wrong!
[03:43] <ScottK> I'll look into it tomorrow.  Now at least we know how many bug reports you have to file after you get done fixing.
[03:43] <eolo999> ok, I go to bed, thanks again
[03:43] <ScottK> Good night.
[03:51] <jellyfish2002> hi motu
[03:51] <jdong> GAAH
[03:51] <jdong> the build failed at the LAST step
[03:51] <jdong> because of a few HTML files being in the wrong spod
[03:52] <ScottK> Of course.  The one it fails on is always the last step.
[03:52] <jdong> :)
[03:52] <jdong> I'm convinced
[03:52] <jdong> well I exported MAKEOPTS=-j3
[03:52] <jdong> hopefully this makes pass 2 faster :D
[03:52] <jdong> if not, I'm just gonna screw the -dev pacakges
[03:52] <jdong> fortunately nobody has to know about my hacked up pidgin :)
[03:52] <jdong> eew that didn't sound good
[04:00] <DarkMageZ> lol
[04:07] <jdong> whoa, pidgin doesn't replace gaim
[04:09] <jdong> argh, it didn't pick up SSL?
[04:11] <jdong> wonder if just b-d on libgnutls-dev works
[04:13] <bddebian> Heya gang
[04:14] <jdong> looks like pidgin might actually be backportable
[04:14] <jdong> it doesn't seem to fight with existing gaim
[04:14] <jdong> though both installed is kind of awkward
[04:15] <Fujitsu> Backported from where? It's not in unstable, nor in Gutsy that I can see.
[04:18] <jdong> Fujitsu: I know, I'm predicting. It's in alioth SVN
[04:19] <Fujitsu> beta7 is in Debian NEW, but doesn't look like final is yet.
[04:19] <Fujitsu> Oh, it is now too.
[04:21] <imbrandon> final is in NEW also
[04:21] <imbrandon> jdong: its in svn ?
[04:22] <jdong> I got it from http://svn.debian.org/wsvn/pkg-gnome/packages/unstable/pidgin/?rev=0&sc=1
[04:22] <imbrandon> does it make clean packages
[04:22] <jdong> the svn version ftbfs'ed me initially
[04:22] <jdong> due to nss3-dev -> nss-dev
[04:22] <jdong> and then it ftbfs'ed me building documentation.
[04:22] <imbrandon> ahh care to share your 3 files ?
[04:22] <jdong> so I err... hacked off that bit
[04:22] <imbrandon> e.g orig dsc and diff ?
[04:23] <jdong> imbrandon: still working on getting SSL/TLS support....
[04:23] <jdong> imbrandon: but those were the only two changes I made to the SVN stuff
[04:23] <jdong> nss3->nss in control
[04:23] <jdong> removed the last line in debian/rules (cp *.html whatnot debian/....)
[04:23] <jdong> didn't bother investigating why that step failed. stupid me.
[04:24] <jdong> I'll see if it'll spit back a DSC
[04:24] <jdong> if it does then I'll do it
[04:24] <jdong> I kind of hackishly got the tarball so I'm not sure if dpkg-source will see it properly?
[04:25] <imbrandon> ness3 seems to work fine in gutsy gaim
[04:25] <imbrandon> hrm
[04:26] <jdong> bleh, it clobbered the tarball together with the diff
[04:26] <jdong> probably an underline.
[04:27] <jdong> imbrandon: nss3 results in uninstallable in feisty pbuilder; ebook was apparently linked against firefox's nss
[04:28] <jdong> imbrandon: http://pastebin.ca/471710
[04:28] <jdong> pastebin; diff of my debian/ from the svn URL I posted
[04:28] <jdong> svn://svn.debian.org/pkg-gnome/packages/unstable/pidgin/trunk/debian
[04:28] <imbrandon> that svn looks empty
[04:28] <imbrandon> i hate websvn
[04:28] <imbrandon> grr
[04:28] <jdong> lol
[04:28] <jdong> :)
[04:29] <jdong> kinda silly the webviewer can't proxy
[04:29] <ScottK> jdong: I think what I'm doing to pyspf to get it to build in sarge would remind you of your bad old days of unofficial backports ;-)
[04:29] <ScottK> Good night all (really this time).
[04:30] <bddebian> Gnight ScottK
[04:30] <jdong> imbrandon: aha, debian/rules, --enable-gnutls=no -> yes
[04:30] <jdong> :)
[04:31] <imbrandon> should be something like : --enable-perl --disable-silc --with-zephyr=/usr --enable-dbus --enable-gnutls=no
[04:31] <imbrandon> --enable-nss=yes --enable-cyrus-sasl
[04:31] <imbrandon> right ?
[04:32] <imbrandon> i think your straying a bit too far , i built it fine earlier with the gaim debain/
[04:32] <jdong> imbrandon: I want --enable-gnutls=yes
[04:33] <jdong> else my gaim can't ocnnect to googletalk jabber
[04:33] <imbrandon> sure it can with nss=yes
[04:33] <jdong> hmm
[04:33] <jdong> nss didn't work for me then :(
[04:34] <imbrandon> SSL Library/Libraries......... : Mozilla NSS
[04:34] <imbrandon> ^^ my ./configure
[04:34] <jdong> how the....
[04:35] <imbrandon> :)
[04:35] <jdong> I hate you.. in the loving way :)
[04:37] <jdong> SSL Library/Libraries......... : GnuTLS
[04:37] <jdong> good enough.
[04:37] <jdong> lol
[04:37] <imbrandon> well not good enough for the repos if we want to stay close to debian ;)
[04:37] <jdong> it doesn't look happy with libnss-dev providing libnss3-dev
[04:37] <jdong> imbrandon: good enough for my own computer :D
[04:39] <imbrandon> jdong: http://rafb.net/p/WU0isf59.html
[04:40] <jdong> imbrandon: you used nss3 or nss?
[04:40] <jdong> (pbuilder?)
[04:40] <RAOF> Oh, cool.  There's a mono plugin engine for pidgin?
[04:40] <jdong> RAOF: yeah, haven't figured out what is required to enable it
[04:41] <jdong> mono's going on its world domination campaign :)
[04:41] <RAOF> :)
[04:41] <jdong> I do have to say DLR/Silverlight really looks/sounds cool
[04:41] <imbrandon> http://rafb.net/p/GTtX3l49.html
[04:42] <imbrandon> jdong: adobes version is better and semi opensource
[04:42] <jdong> imbrandon: those pastes are photoshopped. I reject your reality and substitute my own.
[04:42] <imbrandon> jdong: want me to just package it for you ? lol
[04:42] <crimsun> that's a dangerous road
[04:42] <jdong> imbrandon: lol, please :). this on feisty?
[04:43] <crimsun> you'll end up maintaining them, too.
[04:43] <imbrandon> yea fiesty
[04:43] <jdong> ok cool
[04:43] <jdong> that does a lot of blame-shifting too
[04:43] <jdong> I'm happy
[04:43] <imbrandon> crimsun: thats what i was afraid of, a gnome app :)
[04:43] <crimsun> don't be afraid of gnome.  Just its users.
[04:43] <imbrandon> hehe
[04:44] <imbrandon> ok give me ~20 minutes to see how this works
[04:44] <imbrandon> i should have something you can test
[04:46] <jdong> YAY MY PIDGIN FLIES
[04:46] <jdong> YAY!!!
[04:50] <jellyfish2002> hi bddebian
[04:50] <bddebian> Heya jellyfish2002
[04:50] <jellyfish2002> any more things i can learn from u?
[04:50] <jellyfish2002> regarding the usage of linda & lintian
[04:50] <jellyfish2002> i not really sure of it
[04:50] <bddebian> How much time do you have?
[04:52] <jdong> bug 112511
[04:52] <ubotu> Launchpad bug 112511 in feisty-backports "Backport Pidgin 2.0.0 Final to Fiesty" [Undecided,Rejected]  https://launchpad.net/bugs/112511
[04:52] <jdong> bug 112513
[04:52] <ubotu> Launchpad bug 112513 in feisty-backports "Backport Thunderbird 2.0.0.0 to Feisty" [Undecided,Unconfirmed]  https://launchpad.net/bugs/112513
[04:53] <jellyfish2002> will you be around abt 2 hrs later?
[04:53] <jellyfish2002> coz i going for my lesson now
[04:54] <bddebian> jellyfish2002: It's possible, its 11pm atm :-)
[04:54] <jellyfish2002> okie i try to rush back cya later bddebian
[04:54] <bddebian> Later
[04:56] <jdong> "Tracker works without severe bugs (nothing like the beagle indexer),"
[04:56] <jdong> haha
[04:56] <jdong> I'm sure bhale would love to hear that
[05:09] <eck> can someone explain do me how i can create a new patch for a package using dpatch? the wiki page isn't clear to me
[05:10] <DarkMageZ> differences between gaim & pidgin besides the name change?
[05:11] <jdong> DarkMageZ: some new icons, a few minor UI changes
[05:11] <jdong> I am not impressed
[05:11] <jdong> I have reverted to feisty gaim for now
[05:12] <DarkMageZ> i've stoped using gaim altogether and switched to emesene
[05:12] <plugwash> yes, the dropping of protocol from the status icons has created quite a stir
[05:13] <bddebian> eck: Does it already use dpatch?
[05:13] <eck> bddebian: yes
[05:14] <persia> eck: Take a look at the xterm package.  You need to have rules like prepare: patch: and unpatch:.
[05:14] <persia> eck: Or listen to bddebian, who knows well
[05:14] <bddebian> eck: dpatch-edit-patch  make changes  exit
[05:15] <bddebian> Then you'll need to add the newly created patch file to 00list
[05:18] <eck> it appears that it does not use dpatch, since there is no 00list file in debian/patches -- is there something i should be looking for in the rules file (or elsewhere) to determine which patch system the package uses?
[05:18] <imbrandon> cdbs?
[05:20] <bddebian> Heya gpocentek
[05:21] <gpocentek> hello bddebian 
[05:21] <bddebian> eck: Yes, in debian/rules is there a patch: target?  Or as imbrandon says, does it use simple-patch-sys or any such thing?
[05:22] <plugwash> eck is it a traditional rules file or a CDBS one?
[05:22] <eck> i'm not sure -- the package is coreutils
[05:23] <plugwash> post debian/rules up on a pastebin, i really don't fancy downloaing a package that big to take a loo
[05:23] <plugwash> *look
[05:23] <eck> sure, give me a sec
[05:23] <persia> OOh!  DBS.
[05:24] <eck> http://paste.ubuntu-nl.org/19201/
[05:25] <persia> eck: Use dbs-edit-patch to generate your patch
[05:34] <imbrandon> jdong: ok package cleaned up a bit, patches fixed
[05:34] <eck> neat, it worked
[05:34] <imbrandon> and building
[05:34] <eck> thanks everyone
[05:35] <jdong> cool
[05:35] <jdong> pidgin didn't really fly with me too well
[05:35] <imbrandon> will let you test/guinypig when its done
[05:35] <jdong> I'd want my plugins to work
[05:35] <jdong> :)
[05:35] <jdong> without a massive rebuild
[05:35] <jdong> wow am I picky...
[05:35] <imbrandon> what plugins ?
[05:35] <eck> do i need to assign the patch a number prefix, or should i just submit the patch on LP and let the maintainer take care of it?
[05:35] <jdong> libnotify, otr
[05:35] <imbrandon> eck: just submit the patch
[05:39] <imbrandon> jdong: you know you takin cycles away from my kde4 compile :) heheh
[05:40] <jdong> lol sorry :)
[05:40] <jdong> you don't have to let me have your package :)
[05:40] <imbrandon> lol
[05:42] <TheMuso> Greetings all.
[05:42] <imbrandon> heya TheMuso 
[05:42] <bddebian> Heya TheMuso
[06:44] <nixternal> how do I go about getting bug 107552 into feisty-proposed?
[06:44] <ubotu> Launchpad bug 107552 in krename "krename crash if i want rename files again." [Low,Fix committed]  https://launchpad.net/bugs/107552
[06:51] <ranf> hi
[06:53] <minghua> nixternal: https://wiki.ubuntu.com/StableReleaseUpdates and https://wiki.ubuntu.com/MOTU/SRU
[06:55] <nixternal> minghua: thanks for that, the "When" section is exactly what I needed to see there. No need to get that one SRUd then, I am testing the Gutsy package now and will put it on revu shortly for someone to upload
[06:55] <nixternal> err, not revu, but will put in for a merge rather
[06:56] <minghua> nixternal: also ask around when other people are here - I've never done an SRU so wiki links are all I can help :-)
[06:57] <nixternal> ya, I have done a couple, but for some reason brainfarted on the idea of it for some reason
[06:57] <ranf> hmm, my dput upload doesn't show up. I guess I upped both binary and source *.changes. Any admin hanging around?
[06:57] <persia> nixternal: When you get a working feisty fix, attach a debdiff to a bug in launchpad, and advocate that the bug be applied to feisty.  Once someone uploads to -proposed, the archive admins will review and release (or not).
[06:58] <nixternal> ya, I have already done that, but I don't think it is a big enough issue to warrant an SRU since it isn't sever
[07:07] <nixternal> and if there is a MOTU around, can you please look into bug 112528
[07:07] <ubotu> Launchpad bug 112528 in krename "[Gutsy Merge]  krename_3.0.14-0ubuntu1" [Undecided,Unconfirmed]  https://launchpad.net/bugs/112528
[07:13] <StevenK> nixternal: Looking.
[07:13] <nixternal> rock on StevenK, thanks
[07:24] <StevenK> Closes: #xxxx is a Debian-ism
[07:25] <persia> StevenK: Is there a document somewhere that indicates that we are supposed to use (LP: xxxxxx)?
[07:25] <nixternal> heh, something I have been using and am used to
[07:25] <nixternal> I have never been told to use LP: and nobody has every said other words in the past year about (Closes: #xxxxx)
[07:26] <nixternal> seeing as it has 0ubuntu1 in the version
[07:27] <StevenK> persia: There's a spec about it, does that help?
[07:27] <persia> StevenK: Sure.  Which?
[07:27] <StevenK> That's a hard question.
[07:28] <persia> StevenK: I've looked a couple times since I first heard about LP: last week, and didn't find anything.
[07:29] <StevenK> nixternal: Do you have an .orig for .14?
[07:29] <nixternal> yup
[07:29] <nixternal> you want me to dput this?
[07:29] <nixternal> err
[07:29] <StevenK> dput it where? :-)
[07:29] <nixternal> actually I made the debdiff against .13
[07:29] <nixternal> sorry
[07:30] <StevenK> Yes, you did.
[07:30] <StevenK> You debdiff gave me pause to think when it needed patch -p4, too
[07:30] <StevenK> s/You/Your/
[07:32] <nixternal> hiya Hobbsee 
[07:32] <persia> nixternal: When managing a new upstream vesion to fix something, I recommend putting the new package in REVU, and submitting diff -urN of the debian/ directories and a link to REVU on LP (or at least that's what I did for feisty).
[07:32] <nixternal> persia: I am doing it the way I have been for the last year, and the way I have been shown, but if your way is the correct way, then I can do that
[07:33] <nixternal> minghua: I agree
[07:33] <nixternal> minghua: but everytime I dput revu a new upstream release I never hear the end of it :)
[07:33] <persia> nixternal: For new upstreams?  the way you've done it is typical for new revisions, but hard to look at for new versions.
[07:33] <minghua> persia: no, I believe uploading new upstream releases of packages that already exists in archive is actually discouraged
[07:33] <persia> minghua: Very much so.
[07:34] <nixternal> minghua: and that is exactly what I have been harped at about :)
[07:34] <minghua> argh
[07:34] <nixternal> I used to dput revu everything at first, hehe
[07:34] <minghua> I meant "uploading  to REVU new upstream releases of packages"
[07:34] <Hobbsee> hi nixternal!
[07:34] <persia> nixternal: Can you fix the bug without a new upstream?  If so, backport the fix patch to the old upstream, and only make a new revision.
[07:35] <nixternal> persia: already have for feisty, but seeing as this is for Gutsy, to me that is rather rediculous, seeing it is just the beginning stages, the latest version fits nicely
[07:37] <minghua> I wouldn't do -0ubuntu1 merges at this early time of a development cycle, but that's just me
[07:37] <StevenK> minghua: If he wants to, it's his dime.
[07:38] <persia> StevenK: but merging is difficult with -0ubuntu1, if Debian picks up the package.
[07:38] <minghua> StevenK: sure, I am just lazy (to avoid asking for sync later) :-P
[07:38] <StevenK> persia: Yup.
[07:38] <nixternal> I am doing all that I can so I can finally go MOTU this dev cycle, and before I get drug off for doc work and KDE 4 work
[07:40] <minghua> last maintainer-upload at 2005-12-05
[07:40] <Hobbsee> yay, krename
[07:41] <StevenK> 'qmv -f do' ftw
[07:42] <StevenK> It drops you into $EDITOR, and you can edit the filenames directly. As long as you don't change the order of the lines or delete lines, it deals.
[07:42] <StevenK> nixternal: You could always upload krename to Debian.
[07:43] <nixternal> StevenK: ya, I need to do that seeing as they are 5 releases behind
[07:44] <StevenK> nixternal: Who's the Debian maintainer?
[07:44] <nixternal> dunno, would have to look
[07:44] <minghua> I don't think many will object if nixternal hijacks the package
[07:44] <minghua> Maintainer for source package krename is Roman Kreisel <roman.kreisel@web.de>.
[07:44] <persia> nixternal: I take back everything I've said about it.  Please upload -0ubuntu1 (as you've done the last two versions).  It will be a good thing :)
[07:44] <nixternal> I hijacked it last year I think :)
[07:44] <StevenK> nixternal: If you want to maintain it in Debian, I suspect either myself or white will be happy to sponsor you.
[07:45] <nixternal> rock on StevenK, I will look it over here and get my Debian pbuilder/chroot rockin'
[07:46] <minghua> nixternal: I think it's still polite to mail the maintainer and debian-devel list before hijacking, though
[07:46] <StevenK> Yes.
[07:46] <StevenK> I won't upload it if nixternal hasn't done stuff by the book.
[07:47] <nixternal> oh ya, I definitely wouldn't try and hijack it
[07:47] <nixternal> I will definitely contact the original maintainer
[07:51] <persia> Could someone strong in CVS-fu pleaes suggest how I would extract each of the patches applied to a specific directory in a CVS repository?
[07:51] <StevenK> By careful reading of cvs log
[07:52] <persia> StevenK: Great.  Thanks!
[07:53] <nixternal> haha
[07:53] <StevenK> persia: It isn't really helpful, I suspect. :-)
[07:54] <minghua> especially not helpful if there are many files in the directory, I think
[07:54] <StevenK> Yeah, but that's CVS being brain-dead.
[07:54] <minghua> using date is probably the safest bet?
[07:54] <StevenK> Using revision numbers is safer.
[07:54] <persia> StevenK: Actually, in my specific case, it is very helpful.  I'm not very familiar with CVS, and I am trying to determine the set of patches that my upstream applied to some embedded library source to determine if I can safely use the system library source, so I actually need to read *all* the changes to the embedded source directory.
[07:55] <StevenK> persia: cvs annonate might also help you.
[07:55] <StevenK> persia: Followed by cvs di -r<> -r<> <file>
[07:57] <persia> StevenK: Thanks.  The output of cvs log looks easier at first glance, but I'll look at cvs annotate as well.
[07:58] <StevenK> persia: cvs annonate gives you the file with usernames and revision numbers, so might help you piece stuff together.
[07:58] <ranf> anybody of you guys knows what gets used for VOIP at UDS Sevilla? 
[08:06] <nixternal> alrighty, I contacted Roman about krename in Debian
[08:07] <StevenK> What's his last name?
[08:08] <nixternal> I took a glance through wnpp and didn't see it listed and he hasn't uploaded or maintained it in about a year and a half now
[08:08] <nixternal> Roman Kreisel
[08:08] <StevenK> Ah, don't know him.
[08:16] <StevenK> nixternal: You might want to update the bug report, if you're going to try for the Debian route.
[08:16] <nixternal> roger
[08:18] <nixternal> updated
[08:50] <afflux> If I'm not wrong, I'd need a sponsor for bug 112449... Anyone here who could have a look at it or at least tell me if I can go on merging the other libapache-mod- packages mentiond on DaD?
[08:50] <ubotu> Launchpad bug 112449 in libapache-mod-random "please sponsor merge libapache-mod-random 1.4-10 from debian" [Undecided,Unconfirmed]  https://launchpad.net/bugs/112449
[08:50] <lionel> afflux: no need to merge them
[08:51] <Fujitsu> I expect that apache will be removed in the near future.
[08:51] <afflux> ah alright :)
[08:51] <afflux> I'll take another one for learing :D
[08:51] <lionel> Debian have done the necessary on his side (changing shell from /bin/sh to /bin/bash)
[08:52] <afflux> I saw the entry in the changelog but I actually saw now fix... seems I've been looking in the wrong directory. grr
[08:53] <afflux> s/now/no/
[10:00] <gpocentek> Nafallo: do you plan to update wave-look for gutsy on REVU?
[10:26] <_filippo_> !seen Lamego
[10:26] <ubotu> Sorry, I don't know anything about seen lamego - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[10:27] <_filippo_> seen Lamego
[10:27] <crimsun> who?
[10:27] <RAOF> _filippo_: I don't think ubotu keeps activity logs
[10:27] <_filippo_> crimsun: how does it work?
[10:27] <_filippo_> RAOF: well ok
[10:27] <crimsun> 11:50 -!- Lamego [n=lamego@a83-132-143-105.cpe.netcabo.pt]  has quit [Remote closed the connection] 
[10:27] <_filippo_> thanks
[10:28] <_filippo_> crimsun: thanks
[10:32] <persia> Does it matter if Ubuntu packages don't support BSD kernels?
[10:34] <crimsun> not really, but it is best if we deviate as little as possible from Debian source packages if the latter support them.
[10:35] <persia> crimsun: OK.  I'm just getting complaints from /usr/share/cdbs/1/rules/simple-patchsys.mk about patches to config{sub,guess}, and would prefer to avoid a possible future FTBFS.  I'll leave it alone for now (just a warning: the patches apply).
[10:38] <jussi01> hiya all!!
[10:40] <gpocentek> morning
[10:41] <jussi01> morns gpocentek
[10:41] <gpocentek> congrats jussi01 :)
[10:41] <jussi01> thanks :D
[10:42] <jussi01> its the first one... so its a big thing for me ::D
[10:43] <gpocentek> hehe, I know that feeling ;)
[10:44] <DktrKranz> any u-u-s around to review a couple of merges?
[10:45] <gpocentek> DktrKranz: I've just uploaded rsh-redone 
[10:45] <Nafallo> gpocentek: I guess I should. kind of low on my TODO list though.
[10:46] <gpocentek> Nafallo: np, I just try to clean REVU a little
[10:47] <Nafallo> gpocentek: kewl! :-)
[10:48] <gpocentek> I wonder if I shouldn't archive all the upload done before february...
[10:48] <gpocentek> the list of package would be less scary
[10:48] <gpocentek> packages*
[11:14] <Nafallo> Adri2000: ping DaD, is there a way we could filter out packages that has it's own packagesystem in Ubuntu. gajim being one of those :-).
[11:15] <ranf> hi
[11:17] <ranf> My latest dput upload doesn't show up on REVU. I think because of a binary upload I did earlier today?
[11:20] <crimsun> yes, you'll need the previous upload removed so that you can reupload source only.
[11:21] <ranf> crimsun, I need an admin's help, right?
[11:22] <crimsun> yes, and AFAIK, gpocentek is active.
[11:23] <davromaniak> Seveas, are you here ??
[11:23] <Seveas> davromaniak, yes
[11:23] <davromaniak> you are the developer of falcon ??
[11:23] <Seveas> yes
[11:24] <ranf> he is not listed on https://wiki.ubuntu.com/MOTU/Packages/REVU . gpocentek: help please 
[11:24] <davromaniak> with the new version (1.5.4-0ubuntu2), I have an error
[11:24] <Seveas> davromaniak, on feisty?
[11:24] <davromaniak> no, edgy
[11:24] <Seveas> pm me the error then :)
[11:24] <davromaniak> http://wklej.org/id/14e30601de
[11:24] <davromaniak> oops
[11:25] <Seveas> davromaniak, ls -la /usr/bin/python
[11:26] <Seveas> what does that say?
[11:28] <\sh> Nafallo, did you pushed gajim to bazaar somewhere?
[11:28] <Nafallo> \sh: indeed I did. let me find the URL for you.
[11:29] <gpocentek> DktrKranz: postgresql-8.1 8.1.9-1.1 (source) in Ubuntu
[11:29] <gpocentek> DktrKranz: looks like your merge is not needed
[11:29] <davromaniak> slomo, did you took a look at youtranslate ??
[11:30] <Nafallo> \sh: sftp://bazaar.launchpad.net/%7Eubuntu-dev/gajim/ubuntu/
[11:30] <DktrKranz> gpocentek, see 8.1.8-1ubuntu3 changelog entry
[11:31] <\sh> Nafallo, which team I need to be in to push modifcations to the branch? ;)
[11:31] <Nafallo> \sh: ubuntu-dev
[11:31] <\sh> Nafallo, ah the usual :)
[11:33] <gpocentek> DktrKranz: the package built fine on the buildds
[11:33] <ranf> gpocentek, are you an admin?
[11:33] <gpocentek> ranf: no
[11:33] <DktrKranz> even with python2.5?
[11:33] <DktrKranz> if so, we can manage a sync
[11:34] <gpocentek> DktrKranz: the sync has already be done from what I see
[11:34] <DktrKranz> whoops, didn't notice
[11:34] <gpocentek> https://bugs.launchpad.net/ubuntu/+source/postgresql-8.1/8.1.9-1.1
[11:34] <DktrKranz> I see
[11:34] <DktrKranz> I'm going to close my bug, then
[11:34] <ranf> \sh, could you please my remove my binary upload for "wtmptail"?
[11:35] <DktrKranz> thanks
[11:35] <jekil> hello
[11:35] <gpocentek> DktrKranz: thank _you_ ;)
[11:36] <\sh> ranf, I don't have any revu powers anymore...
[11:37] <ranf> \sh, oops, what a pity.
[11:37] <ranf> \sh, while i'm at it should I wipe you from the Wiki page?
[11:38] <\sh> ranf, whatever :)
[11:39] <persia> crimsun: Could I trouble you about audacity again?
[11:50] <_filippo_> Lamego: ping?
[11:50] <Lamego> pong
[11:51] <Lamego> i am working on pidgin 2.0 right now :P
[11:51] <_filippo_> Lamego: i've just sent you an email? did you receive it?
[11:51] <Lamego> then i will read your email :)
[11:51] <Lamego> yup
[11:51] <_filippo_> Lamego: ah ok thanks ;P
[11:51] <ranf> ajmitch, could you please remove my binary upload for "wtmptail"? 
[11:51] <_filippo_> Lamego: i've posted a bug on launchpad about gaim-pidgin
[11:51] <\sh> Adri2000, ping DaD : package destar and dolphin are totally broken (changelogs not  merged correctly) 
[11:51] <Lamego> a bug on the final :P ?
[11:52] <_filippo_> Lamego: no on upstream gaim
[11:52] <_filippo_> Lamego: it depends on nautilus-sendto and i think this is wrong
[11:53] <_filippo_> Lamego: i've installed pidgin but i cannot remove gaim without losing sendto features
[11:53] <_filippo_> (like sendo to evolutio and sendto bluetooth)
[11:53] <_filippo_> https://bugs.launchpad.net/bugs/112316
[11:53] <ubotu> Launchpad bug 112316 in gaim "Removing gaim causes nautilus-sendto removal" [Undecided,Unconfirmed]  
[11:54] <Lamego> are you sure you build with the proper dependencies ? Piding has some tones of compile options :P
[11:54] <_filippo_> Lamego: it's not a pidgin but a gaim problem
[11:54] <_filippo_> Lamego: i want to remove it but i can't
[11:54] <Lamego> ah ok, that bug description seems better
[11:54] <Nafallo> why work on pidgin? :-)
[11:55] <Lamego> Nafallo, to make it available for users in general
[11:55] <Nafallo> there is always packages in the wild...
[11:55] <Nafallo> Debian NEW has it, and seb128 is working on it AFAIK.
[11:56] <Lamego> Nafallo, if you could point me to the .diff for it, it would be helpfull
[11:56] <Nafallo> I would bet jdong will put it in feisty-backports when it's NEWed in Ubuntu
[11:56] <Lamego> anyway I couldn't find a .deb for it :)
[11:57] <Nafallo> I'll ask Philip5 about URL next time I see him.
[11:57] <Lamego> until then its packaged :P
[11:57] <Lamego> thanks anyway :)
[11:57] <Nafallo> feel free to duplicate work then ;-)
[11:58] <Nafallo> i just can't see a point in doing that :-)
[11:58] <Kmos> learn how to package better :)
[11:58] <Kmos> lol
[11:58] <Lamego> Nafallo, hundreds of users see the point in it
[11:59] <Lamego> can you point them, to a pidgin 2.0 package right now :) ?
[11:59] <Nafallo> Lamego: hundreds of users should learn the meaning of "waiting" then :-)
[11:59] <Lamego> Nafallo, I like that approach "easy, you just need to wait six months"
[12:00] <Nafallo> Lamego: a couple of weeks before there is an official backport at most... ;-)
[12:00] <Kmos> Lamego: not so long, it will be available for feisty in backports as Nafallo says
[12:00] <Nafallo> something tells me it's on jdongs radar already :-)
[12:00] <Lamego> it will be available this weekend ?
[12:01] <Lamego> if not, than, is too old :)
[12:01] <Nafallo> I said a couple of weeks. people are traveling to Seville atm.
[12:01] <Nafallo> Lamego: you see, that's exactly why I don't like users...
[12:02] <Lamego> so, so its not work duplication, they are travelling, I am building :)
[12:02] <Lamego> unless they are doing it on their laptop :P
[12:03] <Nafallo> hmm. I wonder if it might be in Ubuntu NEW...
[12:03] <Lamego> Nafallo, that exactly what I like as an user, to be able to install the latest version as soon it gets available :)
[12:03] <_filippo_> Nafallo: gaim stressed users with thousands of betas.. i think users aren't wrong wanting to try the final release soon
[12:03] <Lamego> not because its new, but usually it fixes some bugs I am experiencing or provides some features which I need :)
[12:03] <Nafallo> Lamego: because the version number incremented rather than the package provides features you need surely? :-)
[12:03] <Lamego> Nafallo, read my comment :)
[12:04] <Lamego> Nafallo, I do usually read the changelogs :)
[12:04] <Nafallo> Lamego: you, I wrote my thing before ;-)
[12:04] <Nafallo> Lamego: but new code == bugs, so not matter how many bugs they fixed there should be new ones ;-)
[12:04] <Lamego> and you can be sure, most of people which spend time trying to compile a new version, do it because they need, not because they like to compile :)
[12:05] <Lamego> Nafallo, sure, but in general, a new release, specially when final, releases a bugs from a series of testing more often than it introduces new bugs
[12:05] <Lamego> i mean, includes bug fixes
[12:06] <Lamego> that is way you have testing before releases :)
[12:06] <Lamego> according to your theory, we should also not upgrade to a newer distro version, it resolves bugs, and introduces new ones :)
[12:06] <Nafallo> sure, but I would still use what we have in the repos except I have a chance of actually getting the changes uploading. call me conservative but... ;-)
[12:07] <Nafallo> no, I run gutsy right now. I do this because I try to find bugs and get them fixed before we release.
[12:07] <Lamego> Nafallo, sure, same as me, unless i trust the package builders :)
[12:07] <Lamego> the same way you seem to trust on the backports :)
[12:07] <Nafallo> but upgrading from 6.06.1 just for the sake of it on a ordinary user... no, I wouldn't :-)
[12:08] <Nafallo> I don't use backports myself...
[12:09] <Nafallo> hmm
[12:09] <Nafallo> or rather, backports comes from the distro I help developing :-P
[12:10] <Nafallo> anyway. shower and stuff.
[12:10] <Nafallo> *poff*
[12:10] <Lamego> :P
[12:27] <Adri2000> \sh: indeed, for dolphin it's because the ubuntu package is not based on any debian version (only 0ubuntuX versions in the changelog) and thus DaD doesn't find the "base version" and cannot create the patches correctly. for destar it is actually based on a debian version, but for some reason it didn't download it, I'll look at the log when redoing all the merges on the new server
[12:28] <Adri2000> \sh: for the first problem (only 0ubuntuX versions in the changelog), we may try to handle that better in the future
[12:28] <\sh> Adri2000, hmm..we should consider to mark them as "initial release to ubuntu, before debian...please be careful)
[12:30] <geser> Adri2000: can you make the dir listings on DaD a little bit wider?
[12:31] <geser> I use to look at the ubuntu patches when reviewing syncs/merges
[12:31] <geser> but currently I have to check the url to find the patch as it gets cut off
[12:32] <Adri2000> Nafallo: if you mean packages with only 0ubuntuX versions in the changelog (ie. no debian base version), it's the problem mentioned above. but in the case of gajim, it is based on a debian version (old yes, was during dapper cycle, but still).
[12:33] <Adri2000> geser: yes I can, just need to find the right option of apache :)
[12:35] <Nafallo> Adri2000: based and based... I think \sh dropped Debians packaging there already :-)
[12:35] <Nafallo> Adri2000: anyway. is it possible to filter it? :-)
[12:36] <\sh> Adri2000, gajim was special and is still...we are not matching with debians package...
[12:37] <\sh> Adri2000, so all patches will be a mess for someone who has no clue about the package diffs between ubuntu and debian...
[12:38] <Nafallo> the last time someone other than me, slomo or \sh touched it all our patches was gone :-P
[12:39] <Adri2000> Nafallo: there are still debian changelog entries in debian/changelog, that's why DaD thinks it's "based" on the debian package
[12:40] <Adri2000> Nafallo: and filter... add a comment "Don't merge" would be a good start
[12:40] <\sh> Adri2000, http://httpd.apache.org/docs/2.0/mod/mod_autoindex.html#indexoptions 
[12:40] <\sh> Admiral_Chicago, NameWidth=[n  | *] 
[12:40] <\sh>     The NameWidth keyword allows you to specify the width of the filename column in bytes.
[12:40] <\sh>     -NameWidth (or unset) allows mod_autoindex to calculate the best width.
[12:40] <\sh>     NameWidth=n fixes the column width to n bytes wide.
[12:40] <\sh>     NameWidth=* grows the column to the necessary width.
[12:40] <\sh> ;)
[12:41] <Adri2000> thanks \sh :)
[12:41] <\sh> Adri2000, np
[12:42] <\sh> added now "DONT TOUCH IT"
[12:43] <Adri2000> Nafallo: we could add support for an "ignore" file with all the packages we don't want to merge in it, but that's not yet written
[12:43] <\sh> Admiral_Chicago, where can we find the source...I think we can help :)
[12:43] <Nafallo> Adri2000: nice :-)
[12:43] <\sh> Nafallo, added your comment
[12:44] <Nafallo> \sh: ? :-)
[12:44] <Nafallo> ah
[12:44] <Nafallo> right
[12:45] <Adri2000> \sh: in a bzr branch on LP, as soon as we have finished everything and moved to the new server (that should be done today, I hope)
[12:46] <Adri2000> geser: done :)
[12:46] <\sh> Nafallo, what do you think about a ubuntu gajim splashscreen ? ;) 
[12:46] <Nafallo> \sh: naah. starts fast enough to do without :-)
[12:46] <\sh> Nafallo, lol
[12:53] <geser> Adri2000: thanks
[12:55] <Kmos> who update the canonical commercial repo ?
[12:55] <Kmos> bug 105859
[12:55] <ubotu> Launchpad bug 105859 in app-install-data-commercial "Opera 9.2 is out with many bug fixes" [Undecided,Confirmed]  https://launchpad.net/bugs/105859
[12:57] <\sh> Kmos, canonical itself
[12:57] <\sh> but don't expect people working on a weekend..
[01:00] <Fujitsu> Nor during UDS, probably.
[01:00] <\sh> no, not during developer summits...too much beer and other hot stuff ;)
[01:00] <Kmos> hehe
[01:01] <Kmos> \sh: the hot you don't mean girls surely :)
[01:01] <Kmos> lol
[01:01] <Nafallo> chili? :-)
[01:02] <\sh> Kmos, no..but hard drinks (I remember different whisky during UBZ)
[01:03] <Kmos> http://www.getdeb.net/download.php?release=817&fpos=0
[01:03] <Kmos> \sh: u're german? =
[01:03] <Kmos> =)
[01:03] <Kmos> hehe
[01:05] <\sh> Kmos, you don't know...I'm german and most of the blogging time anti-american -,)
[01:05] <Nafallo> hmm
[01:05] <Nafallo> nice title on this song.
[01:05] <Nafallo> Imperfect breed of humanity :-)
[01:06] <Kmos> \sh: nice, i was born in germany, but live since 6 months of life in Portugal
[01:06] <Kmos> USA will destroy everything
[01:06] <\sh> Kmos, cool...:) I visited portugal one time, Lagos...
[01:07] <Nafallo> I want to move :-)
[01:07] <Kmos> I hope one day I can visit germany
[01:07] <Kmos> :)
[01:07] <Kmos> lagos, hmm.. i think that's around Lisbon (Capital)
[01:07] <Nafallo> maybe down to dead c0de :-P
[01:07] <Kmos> Lamego is also Portuguese :)
[01:07] <Kmos> the owner of getdeb.net
[01:08] <\sh> Kmos, no...it's south...
[01:08] <\sh> near the most west point of europe ;)
[01:08] <Kmos> algarve :)
[01:08] <\sh> yeah
[01:08] <Kmos> where everyone goes in vacances
[01:08] <Kmos> lol
[01:09] <Kmos> I live near Viseu =) in the north
[01:09] <Kmos> 8/9 hours of car from algarve
[01:09] <Kmos> if next year the UDS be in Portugal it would be great, there are a lot of ubuntu users here
[01:19] <\sh> I don't think so, that the next Developers Summit is in Europe...
[01:19] <\sh> It will be somewhere else...
[01:25] <Nafallo> after Seville will be US
[01:27] <\sh> hey ivoks 
[01:28] <\sh> so again Mr. Bush Junior country...why oh god why..why not ZA or Japan..japan has a great marketshare of linux regarding the LPI courses
[01:29] <\sh> or cameroon is also ok
[01:29] <\sh> or turkey
[01:29] <\sh> india is also nice
[01:30] <Nafallo> bandwidth?
[01:31] <\sh> well, this is a problem but nothing what couldn't be solved...
[01:31] <persia> Everything but Cameroon above has locations with decent bandwidth.
[01:31] <\sh> yepp
[01:31] <DktrKranz> italy, so I can get there :P
[01:32] <Nafallo> persia: even za?
[01:32] <persia> Nafallo: I thought I heard something about networking there, although I haven't been following the fixed line news as much recently as in the past.
[01:32] <Nafallo> according to the mirroradmin only the place with his mirror has decent bw :-P
[01:35] <ivoks> hi all
[01:36] <\sh> DktrKranz, you are from Italy?
[01:36] <DktrKranz> yep
[01:36] <ivoks> what's the topic of conversation? :)
[01:36] <Nafallo> ivoks: Italy, it seems :-)
[01:37] <ivoks> oh :)
[01:37] <\sh> DktrKranz, well it's not far away from germany :)
[01:37] <DktrKranz> or "the place where you get the greatest pasta or lasagna"
[01:37] <ivoks> what about it?
[01:37] <\sh> ivoks, decision for Ubuntu Developer Summits != US
[01:37] <ivoks> ou!
[01:37] <DktrKranz> \sh, it's only five hours in a car :)
[01:37] <ivoks> italy would be nice - very close :)
[01:38] <\sh> DktrKranz, Sdtirol? ,-)
[01:38] <ivoks> (read: cheaper to get there; i might even show up :)
[01:38] <Nafallo> \sh: you won't be making that decision anyway :-P
[01:38] <\sh> Nafallo, that's right :) 
[01:38] <DktrKranz> north Italy, but not sudtirol :)
[01:38] <Nafallo> so why bother? :-)
[01:38] <\sh> Nafallo, but I could give hints, why US is not the right place
[01:39] <ivoks> well, i agree with \sh about US
[01:39] <ivoks> its not that it
[01:39] <\sh> DktrKranz, so area is around firence ;)
[01:39] <ivoks> is far away, but these procedures...
[01:39] <DktrKranz> just in the middle, near boulogne
[01:40] <\sh> ivoks, thx ... that is one of the problems...
[01:40] <Nafallo> Nordic countries would be cool :-)
[01:40] <ivoks> :)
[01:40] <Nafallo> like... Sweden ;-)
[01:40] <ivoks> Nafallo: yes, in winter time, so i can bring my snowboard :)
[01:40] <Nafallo> ivoks: you won't have time for snowboarding :-)
[01:40] <ivoks> there's always time for snowboarding :D
[01:40] <Nafallo> hehe
[01:40] <\sh> ivoks, the other thing is, US is not against Linux...but other countries need to be touched by our linux love... 
[01:41] <Kmos> \sh: Portugal is one of that countries..
[01:41] <\sh> and they should leave Iraque
[01:41] <ivoks> let's not turn this into politics
[01:41] <Kmos> the public administration uses more windows that we like
[01:41] <\sh> yeah
[01:41] <\sh> do some merges people ;)
[01:41] <DktrKranz> yep!
[01:42] <afflux> don't really want to disturb you since I think \sh is right but wasn't there a rule on freenode or the ubuntu channels that we shouldn't talk about politics?
[01:42] <ivoks> oh, gutsy... :)
[01:43] <afflux> grr, i'm definetly too slow...
[01:43] <ivoks> afflux: er... i wouldn't like that rule where we 'shouldn't do something'
[01:43] <ivoks> it just mather of being polite
[01:43] <\sh> afflux, if freenode or ubuntu are not allowing me to talk about politics, I would stop uploading packages or using this service...really
[01:43] <ivoks> not everybody agrees with everybody
[01:44] <\sh> afflux, nobody will stop my pushing towards democracy and free speech
[01:44] <afflux> well, i think i at least read somewhere that we shouldn't to this in theese channels..
[01:45] <afflux> (I perfectly agree with you two ;))
[01:45] <\sh> is it written in the CoC ? as I said, I stop directly
[01:46] <\sh> but as everyone know..I'm something between mad and a a**hole
[01:46] <afflux> hehe
[01:46] <ivoks> i'll start working on gutsy, as soon as my lectures on faculty are over
[01:46] <DktrKranz> no politics in CoC, \sh will be still around :)
[01:47] <ivoks> bbl
[01:48] <persia> When using autotools, when there are embedded library sources, how is ./configure called for the embedded sources?
[01:48] <afflux> Oh, it could be that I missunderstood a sentence from the freenode policy ("Unlawful activities and their related support activities are considered off-topic, as are inappropriate advertising, heavy media file trading, gaming and proprietary game software modding, warez, hax0r activity, porn and various forms of antisocial behavior, including (but not limited to) political, racial, ethnic, religious or gender-related invective. Off-topic activity may result i
[01:48] <afflux> It's the only thing I can find where "politics" are mentioned ,)
[01:49] <persia> afflux: The critical word is invective.  Note that discussion of freenode policies is no more on-topic here than politics.
[01:49] <\sh> afflux, damn..I'm antisocial ;) that's why I'm working on free software...
[01:49] <afflux> \sh: :D
[01:49] <DktrKranz> :D
[01:49] <Kmos> \sh: hehe
[01:49] <afflux> yes, persia, thats why I say i missunderstood it ;)
[01:50] <afflux> ah, found something else: http://freenode.net/channel_guidelines.shtml (search for "Avoid advocacy debates.")
[01:50] <afflux> anyway.. it's time for lunch
[01:51] <DktrKranz> three lines for describing flames ;)
[01:55] <\sh> let's end with this discussion and do some important work...merges#
[01:56] <persia> \sh: Would your interest in merges extend to sponsoring?
[01:57] <\sh> persia, sure..please send me your debdiffs to sh@sourcecode.de
[01:59] <\sh> hmmm I need more beer...need to go to the supermarket
[02:00] <\sh> Adri2000, please fix the \ problem ( \ becomes \\ etc.)
[02:00] <\sh> Adri2000, (web app)
[02:02] <\sh> persia, is it against latest debian or from ubuntu gutsies repos?
[02:02] <persia> \sh: Latest Debian
[02:12] <\sh> persia, uploaded
[02:13] <persia> \sh: Thank you.
[02:19] <Adri2000> \sh: done
[02:33] <afflux> \sh: bug 112547
[02:33] <ubotu> Launchpad bug 112547 in reportbug "merge reportbug 3.37 from Debian unstable" [Undecided,Unconfirmed]  https://launchpad.net/bugs/112547
[02:34] <afflux> \sh: against latest debian too
[02:36] <Kmos> kmos@bash:~/packages/gnu-smalltalk/smalltalk-2.3.3/debian$ dch -v 2.3.3-0ubuntu1
[02:36] <Kmos> dch: fatal error at line 470:
[02:36] <Kmos> what's the problem with this?
[02:36] <Kmos> Found debian/changelog for package gnu-smalltalk in the directory /home/kmos/packages/gnu-smalltalk/smalltalk-2.3.3
[02:36] <Kmos> but this directory name does not match the package name according to the
[02:36] <Kmos> regex  PACKAGE(-.*)?.
[02:37] <man-di> Kmos: gnu-smalltalk != smalltalk
[02:37] <man-di> the dir need to be named gnu-smalltalk-2.3.3
[02:40] <Kmos> right
[02:40] <Kmos> :)
[02:40] <Kmos> i really don't see it
[02:40] <Kmos> lol
[02:42] <_filippo_> Lamego: thanks!! i'm downloading it right now! could i host a copy on project page? also thanks for pidgin i'm already using you package ;)
[02:42] <Lamego> _filippo_, sure :)
[02:42] <_filippo_> Lamego: thanks! you're great!
[02:42] <Lamego> i am rebuilding pidgin with libinotify
[02:43] <Lamego> hum
[02:44] <_filippo_> Lamego: how does pidgin use libinotify?
[02:44] <Lamego> forget it, it's a plugin
[02:44] <Lamego> I had the wrong idea it was builtin
[02:45] <_filippo_> ah ok
[02:45] <_filippo_> forgotten :P
[02:48] <\sh> Kmos, gnu-smalltalk is a sync...I requested already
[02:50] <\sh> afflux, checking it
[02:55] <Kmos> \sh: but it need to be packaged manually, right ?
[02:57] <\sh> Kmos, gnu-smalltalk?
[02:57] <Kmos> yes
[02:57] <Kmos> i'm newbie in packagement :P
[02:57] <\sh> Kmos, no..it's in debian, and the fixes in ubuntu packages are just rebuilds when I read the changelog correctly
[02:58] <\sh> Kmos, so it's just a sync
[02:58] <\sh> from debian
[02:58] <\sh> no upload necessary
[02:58] <Kmos> the ubuntu system will do the sync automatically ?
[02:58] <\sh> but as man-di said correctly, smalltalk != gnu-smalltalk
[02:58] <Kmos> yeah
[02:58] <\sh> Kmos, not when there are ubuntu changes inside, then we need to request them
[02:58] <\sh> (motus do the request, or approving the syncs)
[02:59] <Kmos> \sh: u're not a motu ? so you reported the bug
[03:00] <\sh> Kmos, I'm a motu and core-dev :) so I requested the sync  via bug report 
[03:00] <\sh> Kmos, it will be synced anytime when the archive maintainers have time
[03:00] <\sh> Kmos, https://launchpad.net/~shermann
[03:01] <Kmos> i like to help, but if that will be some type of auto process
[03:01] <Kmos> you need to change your avatar :)
[03:03] <\sh> Kmos, you have to check the merges pages and check if it's a merge or if we can sync it from debian directly
[03:06] <\sh> afflux, uploaded
[03:15] <afflux> \sh: thanks
[03:16] <\sh> how do I remove a wrong tag?
[03:17] <\sh> Kmos, neither gnu-smalltalk nor gps... needs-packaging
[03:17] <persia> \sh: Edit the description, and remove the tag from the space delimited list.
[03:17] <\sh> yeah just found it
[03:34] <persia> Would anyone with an i386 of ppc gutsy environment be willing to test a candidate version of audacity?  I am particularly interested in whether it supports JACK properly.
[03:39] <DktrKranz> persia, I can try later, if you want
[03:41] <persia> DktrKranz: That'd be great.  I've put a debdiff against Debian sources at https://bugs.launchpad.net/bugs/112606, but want to make sure my architecture conditional stuff works properly before it is uploaded.
[03:41] <ubotu> Launchpad bug 112606 in audacity "Please merge audacity 1.3.2-2 from Debian unstable" [Undecided,Unconfirmed]  
[03:41] <DktrKranz> is it a merge?
[03:42] <DktrKranz> yeah, it is :)
[03:43] <DktrKranz> persia, I'll pass you pbuilder log, so you can see compilation process
[03:44] <persia> DktrKranz: I'm really interested in the runtime behaviour.  I have a i386 vmware instance, but I don't have a working jackd there, so I cannot determine if the JACK support is working.
[03:45] <DktrKranz> I've got a VM, but I think I can manage to get it working
[03:46] <persia> DktrKranz: Does your VM sound work with JACK?
[03:46] <DktrKranz> I can try to verify it
[03:46] <persia> DktrKranz: Thanks.
[03:46] <DktrKranz> actually I shut down sound
[03:47] <DktrKranz> but it's not a matter enable them
[03:50] <DktrKranz> I'll be back in a couple of hours
[03:50] <DktrKranz> see you :)
[03:53] <ScottK> Good morning everyone.
[03:53] <ScottK> eolo999: Are you there?
[03:54] <persia> ScottK: good morning.
[03:54] <ScottK> Hello persia
[04:01] <eolo999> ScottK, I'm there in 5 minuts
[04:01] <ScottK> OK
[04:05] <eolo999> Here a I am
[04:05] <eolo999> Have you tested pythoncad?
[04:07] <persia> eolo999: Do you have a fix already?  Please put your patch in a comment to the bug: I (the submitter) would also like to test.
[04:07] <Kmos> eolo999: it's working very well
[04:07] <eolo999> do you mean the diff file I sent ypu ScottK ?
[04:07] <ScottK> eolo999: I think that's the one persia wants.
[04:08] <ScottK> Kmos: persia is fixing another pythoncad bug than the one you tested.
[04:08] <Kmos> hmm.. nice
[04:08] <persia> ScottK: Ummm..  eolo999 is fixing a different pythoncad bug (that I submitted).
[04:09] <ScottK> Just a sec.  Let me do this with bug numbers...
[04:09] <Kmos> there isn't a better software opensource for CAD ? pythoncad is too limited..
[04:10] <persia> Kmos: blender?
[04:10] <Kmos> persia: it does cad ? like autocad
[04:10] <Kmos> ?
[04:10] <ScottK> Bug #108612 is fixed and there is an SRU pending that I've asked people to test.  persia tested it and, in the process found Bug #112140.  That is what eolo999 has a fix for.
[04:10] <eolo999> i put the diff in LaunchPad Bug #112140
[04:10] <ubotu> Launchpad bug 108612 in pythoncad "[apport]  pythoncad crashed with ExpatError in parse()" [Medium,Fix committed]  https://launchpad.net/bugs/108612
[04:10] <ubotu> Launchpad bug 112140 in pythoncad "pythoncad fails to exit when all windows are closed" [Medium,In progress]  https://launchpad.net/bugs/112140
[04:10] <ubotu> Launchpad bug 112140 in pythoncad "pythoncad fails to exit when all windows are closed" [Medium,In progress]  https://launchpad.net/bugs/112140
[04:11] <persia> eolo999: Thanks.
[04:11] <ScottK> Kmos: I'm a Python guy trying to help out and get Python bugs fixed.  I've got no opinion on the utility of the package.
[04:11] <Kmos> :)
[04:11] <persia> Kmos: I haven't used blender much, and not AutoCAD in years.  At least blender can define shapes, and render them.
[04:11] <eolo999> so we have two patches to join in the new ubuntu package?
[04:11] <ScottK> eolo999: Have you used pbuilder before?
[04:12] <eolo999> no... except some MOTU readings I never used pbuilder.
[04:12] <Amaranth> whee
[04:12] <Amaranth> finally got wifi in my room
[04:12] <LaserJock> Amaranth: are you in Seville?
[04:12] <ScottK> eolo999: We are going to first fix 112140 in Gutsy.  The other bug doesn't apply to that.
[04:13] <eolo999> i'm opening 'Ubuntu packaging Guide'...
[04:13] <Amaranth> LaserJock: yep
[04:13] <Amaranth> just got done eating and got the username/password to the wifi
[04:13] <Amaranth> you can smoke _everywhere_ here :)
[04:13] <ScottK> eolo999: Go to http://revu.tauware.de/~laserjock/ and download the script called pbuilder-feisty.
[04:14] <ScottK> That'll simplify a lot of stuff with getting pbuilder running.
[04:14] <eolo999> i have the script
[04:14] <ScottK> eolo999: I'm having you do this step first becuase it takes a while to create the pbuilder.  You might as well get it started.
[04:14] <ScottK> OK
[04:15] <ScottK> sh pbuilder-feisty create
[04:15] <persia> eolo999: That works great for me.  Thanks.
[04:15] <ScottK> It'll ask you for your password
[04:15] <eolo999> great persia 
[04:15] <LaserJock> Amaranth: lol, I know. it's not great for me. I have somewhat of an intolerance for smoke
[04:15] <Amaranth> LaserJock: Are you here?
[04:16] <eolo999> in package folder ScottK?
[04:16] <LaserJock> Amaranth: yep, room 3172 I think
[04:16] <Amaranth> dude
[04:16] <Amaranth> that's right next door
[04:16] <ScottK> eolo999: In the folder you downloaded the script to.  This has nothing to do with a specific package yet.
[04:16] <Amaranth> 3173
[04:16] <ScottK> LaserJock: Got a minute for an opinion on an SRU?
[04:18] <eolo999> I'm running the script, but I already set up pbuilder for feisty..
[04:18] <LaserJock> ScottK: not exactly. I actually need to run down and try to grab some food
[04:18] <ScottK> NP
[04:19] <ScottK> If any MOTUs (particularly one from motu-sru) is watching, I'd like an opionion on a pending SRU...  There is a pythoncad update in feisty proposed that fixes Bug #108612.  We now have a fix for Bug #112140.  By itself, it wouldn't be SRU worthy, but does it make sense to add it to the existing feisty-proposed package (it's a one liner) or just let it go?
[04:19] <ubotu> Launchpad bug 108612 in pythoncad "[apport]  pythoncad crashed with ExpatError in parse()" [Medium,Fix committed]  https://launchpad.net/bugs/108612
[04:19] <ubotu> Launchpad bug 112140 in pythoncad "pythoncad fails to exit when all windows are closed" [Medium,In progress]  https://launchpad.net/bugs/112140
[04:19] <ScottK> eolo999: Is it running?
[04:20] <eolo999> ScottK, Yes it is running but I already set up pbuilder for feisty following ubu packaging guide
[04:20] <ScottK> Oh
[04:21] <eolo999> now i don't know... i have double.
[04:22] <ScottK> Where is the one you made from the packaging guide?
[04:23] <eolo999> don't remember :S
[04:23] <persia> Does anyone know how to submit a bug for a package that has never compiled in any Ubuntu release (recently attempted sync from Debian)?
[04:23] <pochu> slomo: can you review 112384?
[04:24] <ScottK> persia: Is it in the Ubuntu repositories?
[04:24] <eolo999> /var/cache/pbuilder/
[04:24] <ScottK> OK.  Good.
[04:24] <persia> ScottK: The source is in gutsy, but there aren't any binaries (it FTBFS)
[04:24] <ScottK> Laserjock's script puts it in ~/pbuilder
[04:24] <illovae> howdy'all
[04:24] <ScottK> persia: Then shouldn't you just file the bug against packagename as normal?
[04:25] <persia> ScottK: LP doesn't have a +source/ page for it yet :)
[04:25] <ScottK> Hmmmm
[04:25] <ScottK> Dunno then.
[04:27] <eolo999> can I cancel the creation of the new pbuilder env?
[04:29] <ScottK> eolo999: We are going to upgrade this one to gutsy, so just let it run.
[04:30] <eolo999> i downloaded pbuilder-FEISTY
[04:30] <ScottK> Yes.
[04:30] <ScottK> Last I checked, you can't make a Gutsy pbuilder directly.
[04:30] <ScottK> You make a Feisty pbuilder and then upgrade it to Gutsy.
[04:30] <eolo999> ok, perfect
[04:31] <eolo999> so i'll have pbuilder envs for both...
[04:31] <Kmos> ScottK: just need to edit one file
[04:31] <Kmos> kmos@bash:~$ cat ~/.pbuilderrc 
[04:31] <Kmos> ## Overrides /etc/pbuilderrc
[04:31] <Kmos> # Default distribution
[04:31] <Kmos> DISTRIBUTION=gutsy
[04:31] <Kmos> and it will build for gutsy
[04:32] <Kmos> sudo pbuilder build *.dsc
[04:32] <Kmos> :)
[04:33] <ScottK> eolo999: I'm getting the gutsy source now.
[04:34] <ScottK> eolo999: Open debian/rules in your favorite text editor
[04:35] <eolo999> ScottK, ok (vim)
[04:35] <ScottK> You can see in line 8 that this package is set up to use dpatch.
[04:36] <eolo999> yes
[04:36] <ScottK> That tells us how we are going to package the fix.
[04:36] <eolo999> ok
[04:36] <ScottK> eolo999: Have you read https://wiki.ubuntu.com/MOTU/School/PatchingSources
[04:37] <eolo999> yes but now i have to follow it step by step.
[04:37] <ScottK> It's really very easy.
[04:37] <ScottK> First, is your Gutsy source pristine or have you modified it for the fix already?
[04:39] <eolo999> dpatch-edit-patch 
[04:39] <ScottK> Did you do that already or is that what you are proposing?
[04:39] <ScottK> That is how we'll make the patch if you haven't.
[04:40] <eolo999> proposing
[04:40] <ScottK> OK. 
[04:40] <ScottK> That's the correct (easiest/less likely to make a mistake) answer
[04:40] <eolo999> tell me ill follow you...
[04:40] <eolo999> *i'll
[04:40] <ScottK> You haven't answered my question though...  Is your current Gutsy source modified already or not?
[04:40] <ScottK> OK I will
[04:41] <eolo999> the script is still running
[04:41] <eolo999> so i have not modified yet
[04:42] <ScottK> ok.  We can do this while the pbuilder is still making
[04:42] <eolo999> ready
[04:42] <ScottK> The pbuilder is for building a binary.  We need to get a good source package first.
[04:43] <ScottK> First, just have a quick look at man dpatch-edit-patch so you know where the documentation is.  It looks harder than it is, but I want you to at least look at it.
[04:43] <eolo999> i have to source packages, the one i modified and one i didn't touched
[04:43] <eolo999> two
[04:44] <ScottK> OK
[04:44] <ScottK> We will be working in the one you haven't touched.
[04:44] <ScottK> That BTW, is a good practice.
[04:44] <\sh> bbl
[04:45] <ScottK> eolo999: Look in debian/patches and you'll see that there's already a patch there.
[04:45] <eolo999> ok
[04:46] <ScottK> We want to apply your patch AFTER that patch, so we invoke dpatch-edit-patch like this (gimme a sec to try it first and make sure):
[04:48] <ScottK> eolo999: From within the source tree..  dpatch-edit-patch 05_clean_exit 02_remove_unused_bindump
[04:49] <eolo999> did it
[04:50] <ScottK> OK.  Now you are in an environment where you can make your change.
[04:50] <ScottK> use vim to open the correct file, edit it as necessary, and save your changes.
[04:52] <ScottK> Note you don't actually need to comment in the source about the bug number.  We'll do that in the changelog
[04:52] <ScottK> eolo999: ^^
[04:52] <eolo999> i'm working...
[04:53] <eolo999> ok, i'll not write that comment line
[04:53] <nixternal> good mornin'
[04:53] <ScottK> Good morning nixternal
[04:53] <eolo999> edited source file...
[04:53] <ScottK> Saved it?
[04:53] <ScottK> exited vim?
[04:53] <eolo999> now i suppose we have to go on with debian/*
[04:53] <eolo999> yes
[04:53] <ScottK> no
[04:53] <ScottK> Not yet
[04:54] <ScottK> we are still in dpatch-edit-patch
[04:54] <eolo999> yes
[04:54] <ScottK> Now that all of the upstream source changes are made, we exit dpatch-edit-patch
[04:54] <ScottK> just type "exit"
[04:54] <eolo999> exit 230?
[04:55] <ScottK> No
[04:55] <eolo999> no no no: only 'exit'
[04:55] <ScottK> exit 230 is an error.  That gets you out without making the patch
[04:55] <ScottK> exit only is a clean exit and it knows to make the patch.
[04:55] <eolo999>  Warning: debian/patches/00template not exist, using hardcoded default.
[04:55] <ScottK> No problem
[04:56] <eolo999> ready.
[04:56] <ScottK> now look in debian/patches and your patch should be there
[04:56] <eolo999> yes
[04:56] <eolo999> ScottK, should we open a pvt not to bore other guys?
[04:57] <ScottK> open the patch in vim and have a look
[04:57] <ScottK> eolo999: I'd say not.  Others may be watching and learning and the channel is quiet today.
[04:57] <eolo999> ok the patch is nice
[04:57] <ScottK> Look at the e-mail address in line 2.  If it's not correct, fix it.
[04:58] <eolo999> done
[04:58] <ScottK> OK.  Now open 00list
[04:58] <ScottK> Add your patch to it after the 02 patch
[04:59] <eolo999> done
[04:59] <ScottK> OK.
[05:00] <ScottK> Now we do the changelog
[05:00] <DarkSun88> Hi all
[05:00] <eolo999> ok
[05:00] <ScottK> Type dch -i
[05:00] <ScottK> That'll bring you up in your editor with a new changelog entry.
[05:00] <eolo999> in debian folder
[05:00] <ScottK> anywhere within the source tree.
[05:01] <ScottK> or in debian
[05:01] <eolo999> ok
[05:01] <ScottK> doesn't matter
[05:01] <eolo999> ready
[05:01] <ScottK> First line where it says feisty, change it to gutsy
[05:02] <ScottK> Then edit line 5 to have your correct name and e-mail address if it doesn't
[05:03] <eolo999> ok
[05:05] <eolo999> Clean exit (Closes: LP Bug#112140)
[05:05] <eolo999> it's ok?
[05:05] <ScottK> Then In the line that starts with * you describe your change.  Something like Add 05_clean_exit patch (LP: #112140)
[05:06] <ScottK> (Closes: #somebug) is Debian.  We do it a little different.
[05:06] <eolo999> did as you wrote
[05:07] <eolo999> * Add 05_clean_exit patch (LP: #112140)
[05:07] <ScottK> pastebin me your changelog entry and at least one line of the old entry so I can see.
[05:07] <ScottK> Changelogs get automatically parsed, so they are picky about formatting.
[05:08] <eolo999> http://paste.ubuntu-nl.org/19285/
[05:10] <ScottK> Format is good, but we have a little problem here...  pythoncad (0.1.33-2) is the Feisty version, not the Gutsy version.
[05:10] <eolo999> gutsy version is 1.35 or similar
[05:10] <ScottK> Yes
[05:10] <ScottK> So you were making your changes to Feisty source, not Gutsy source
[05:11] <eolo999> oh oh
[05:11] <ScottK> So.  Not a big deal.
[05:11] <ScottK> Just do the same again for the correct package.
[05:11] <ScottK> It's good practice anyway.
[05:11] <eolo999> I can do everything in a while, sorry, i didn't understood...
[05:12] <ScottK> It's hard to communicate everything clearly over IRC.  I probably wasn't clear.
[05:12] <ScottK> eolo999: I'll be here another 4-5 hours today.  Let me know when you have it done up to here and will pick up.
[05:13] <eolo999> ok 5 minutes...
[05:13] <ScottK> eolo999: But we can go ahead and upgrade your new pbuilder to Gutsy.
[05:13] <ScottK> OK
[05:20] <eolo999> ScottK, http://paste.ubuntu-nl.org/19289/
[05:20] <ScottK> err looks
[05:21] <ScottK> Looks good.
[05:21] <ScottK> Let's upgrade your pbuilder now.  It'll take a bit and it can run while we make the source package
[05:21] <eolo999> ready
[05:21] <eolo999> a question ScottK 
[05:22] <ScottK> Shoot
[05:22] <eolo999> What if we had more changes to apply to the source code?
[05:22] <eolo999> now it was easy, just one file, one word
[05:22] <ScottK> Either make a bigger patch or if it's different problems, make multiple patches.
[05:22] <ScottK> The packaging process is the same.
[05:23] <eolo999> i mean when i edited the file from within dpatch
[05:23] <ScottK> Right, but dpatch-edit-patch will keep track of all the changes and will make a multiple file patch if needed.
[05:23] <eolo999> ok
[05:24] <ScottK> dpatch-edit-patch is a lifesaver.
[05:24] <eolo999> ok
[05:24] <eolo999> ahead..
[05:24] <ScottK> Right
[05:24] <ScottK> From the dir where you downloaded the pbuilder script...
[05:24] <ScottK> sh pbuilder-feisty login --save-after-login
[05:25] <eolo999> W: /home/eolo/.pbuilderrc does not exist
[05:25] <ScottK> Is OK
[05:26] <eolo999> File extracted to: /var/cache/pbuilder/build//24144
[05:26] <eolo999> why double slash
[05:26] <ScottK> This puts you inside another virtual environment
[05:26] <ScottK> Dunno.  
[05:26] <ScottK> Don't think it's a problem
[05:26] <ScottK> There are simpler ways to do this, but I am telling you what worked for me
[05:27] <eolo999> ok
[05:27] <ScottK> Use vim to edit /etc/apt/sources.list and change all occurrences of feisty to gutsy
[05:28] <eolo999> did
[05:28] <eolo999> one line is commented out...
[05:28] <eolo999> #deb-src http://archive.ubuntu.com/ubuntu gutsy main
[05:29] <ScottK> We are only working on universe packages here, so that's fine
[05:30] <eolo999> ok
[05:30] <ScottK> Once you have that done, exit vim, sudo apt-get update
[05:30] <ScottK> sudo apt-get dist-upgrade
[05:30] <eolo999> why sudo?
[05:31] <eolo999> it seems that i'm root of this particular env
[05:31] <ScottK> Are you root?
[05:31] <ScottK> Ah
[05:31] <ScottK> Then skip the sudo
[05:31] <ScottK> It was a while ago I did this....
[05:32] <eolo999> it's quite slow.
[05:32] <eolo999> in downloadingf
[05:32] <ScottK> OK
[05:32] <ScottK> Let's leave that and go back to your package.
[05:32] <ScottK> The next step is to build your source package.
[05:33] <eolo999> i'm there
[05:33] <ScottK> Have you installed build-essential and fakeroot already?
[05:33] <eolo999> yes
[05:33] <ScottK> OK
[05:33] <ScottK> then: debuild -S -us should build an unsigned source package.
[05:33] <ScottK> oo
[05:33] <ScottK> OOP
[05:34] <ScottK> Argh
[05:34] <ScottK> debuild -S -uc
[05:34] <ScottK> eolo999: ^^
[05:34] <eolo999> tell me
[05:34] <ScottK> debuild -S -uc
[05:35] <ScottK> Since all we will upload is a debdiff, there is no need to sign the source package.
[05:35] <ScottK> If you were uploading a new package to REVU, you would do it debuild -S -sa to get signed source.
[05:35] <eolo999> got a lintian error
[05:35] <eolo999> E: pythoncad_0.1.35-1ubuntu1_source.changes: bad-distribution-in-changes-file gutsy
[05:35] <eolo999> and two warnings
[05:35] <ScottK> About NMU, right?
[05:35] <ScottK> These are normal.
[05:35] <eolo999> yes
[05:35] <eolo999> E: pythoncad_0.1.35-1ubuntu1_source.changes: bad-distribution-in-changes-file gutsy
[05:35] <ScottK> Sorry.  I just remembered one other thing we have to do...
[05:36] <ScottK> Not a problem.
[05:36] <eolo999> what
[05:36] <ScottK> Since this is now an Ubuntu unique package we need to change the maintainer.
[05:36] <ScottK> https://wiki.ubuntu.com/DebianMaintainerField explains.  This also needs to be noted in the changelog.
[05:37] <eolo999> so what?
[05:38] <ScottK> eolo999: Bottom line is in debian/control, maintainer needs to be set to Ubuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com> and the current maintainer needs to be in XSBC-Original-Maintainer
[05:38] <ScottK> eolo999: Make those changes and then pastebin the control file.
[05:38] <ScottK> Sorry about having to go back on this...
[05:40] <ScottK> eolo999: All this gets easy once you've done a few.
[05:40] <eolo999> i'm pasting it...
[05:42] <soulrider> hello
[05:42] <ScottK> Hello
[05:42] <soulrider> im here ebcause i wanna know if there are any projects based on KDe similar to AptOnCD
[05:42] <soulrider> if not i was hoping to get some people and start one
[05:42] <soulrider> its something that is much needed in some countried
[05:42] <soulrider> countries*
[05:43] <eolo999> http://paste.ubuntu-nl.org/19293/
[05:43] <ScottK> soulrider: You might have better luck in #kubuntu-devel, but not right now as most devs are en route to the developer sprint.
[05:43] <soulrider> oh
[05:44] <ScottK> eolo999: Looks good.  Now make your source package again.
[05:44] <eolo999> W: pythoncad source: changelog-should-mention-nmu
[05:44] <eolo999> W: pythoncad source: source-nmu-has-incorrect-version-number 0.1.35-1ubuntu1
[05:45] <eolo999> E: pythoncad_0.1.35-1ubuntu1_source.changes: bad-distribution-in-changes-file gutsy
[05:45] <eolo999> ok
[05:45] <ScottK> eolo999: These are to be expected.
[05:45] <eolo999> ok
[05:45] <ScottK> Is your pbuilder done upgrading yet?
[05:46] <eolo999> strange 0 upgraded
[05:47] <eolo999> apt-get dist-upgrade
[05:47] <ScottK> You did do an update before you upgraded, right?
[05:47] <eolo999> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[05:47] <eolo999> right
[05:47] <eolo999> this was while updating: E: Some index files failed to download, they have been ignored, or old ones used instead.
[05:48] <eolo999> Failed to fetch http://archive.ubuntu.com/ubuntu/dists/gutsy/main/binary-i386/Packages.bz2  MD5Sum mismatch
[05:48] <ScottK> Hmmm
[05:48] <ScottK> That would explain it I think.
[05:48] <eolo999> try again to update
[05:48] <eolo999> ing
[05:48] <ScottK> OK.
[05:48] <afflux> fast-user-switch-applet can be synced (bug #112636)
[05:48] <ubotu> Launchpad bug 112636 in fast-user-switch-applet "sync fast-user-switch-applet 2.18.0-1 (universe) from debian unstable (main)" [Undecided,Unconfirmed]  https://launchpad.net/bugs/112636
[05:49] <eolo999> I smoke a cigarette in the meanwhile...
[05:50] <ScottK> OK.  Ping me when you get back.
[05:52] <eolo999> ScottK, dist-upgrading
[05:52] <ScottK> OK.
[05:52] <eolo999> 19 minutes!!
[05:52] <ScottK> Sounds like it worked this time.
[05:52] <eolo999> 34 K
[05:52] <ScottK> Back to your source package.
[05:52] <eolo999> ok
[05:53] <ScottK> if you look in the dir above the source, you should see .dsc files for both the old and new versions of the gutsy pythoncad.
[05:53] <ScottK> Got that?
[05:53] <eolo999> ok two dsc files
[05:53] <ScottK> Next we make the debiff.  
[05:54] <eolo999> ready
[05:54] <ScottK> debdiff packagename-{old version}.dsc packagename-{new version}.dsc > descriptive-filename.debdiff
[05:55] <eolo999> descriptive-filename = clean_exit ?
[05:55] <eolo999> .debdiff
[05:55] <ScottK> I'd do pythoncad-clean-exit.debdiff
[05:56] <eolo999> ok
[05:56] <eolo999> did it
[05:56] <ScottK> Once that's done, pastebin the debdiff (it should be short enough) - If it's big, then we did something wrong
[05:57] <ScottK> How's it look?
[05:57] <eolo999> short
[05:57] <ScottK> Good
[05:57] <ScottK> Let me have a look
[05:58] <eolo999> http://paste.ubuntu-nl.org/19297/
[05:58] <soulrider_> ScottK: is there any way i can flag a package out of date? its even outdated int he debian repos i think
[05:58] <ScottK> soulrider_: Just a minute
[05:59] <ScottK> eolo999: Looks good to me.
[05:59] <ScottK> eolo999: Let me know when your pbuilder is done upgrading.
[05:59] <ScottK> soulrider_: What package?
[05:59] <eolo999> 7 minutes
[06:00] <ScottK> OK
[06:00] <soulrider_> ScottK: filelight
[06:00] <ScottK> What's the current upstream release?
[06:01] <ScottK> soulrider_: ?  What's upstream release?
[06:01] <soulrider_> uhm
[06:01] <soulrider_> not sure
[06:01] <soulrider_> im not on kubuntu right now, hold on a sec
[06:02] <ScottK> soulrider_: We have the same version as Debian.
[06:02] <soulrider_> yeah, but its old
[06:02] <soulrider_> its like 0.9 or something like that ?
[06:03] <soulrider_> as far as i can remember, it crashes every time you exit the program
[06:03] <soulrider_> version 1.0 is bug free
[06:03] <ScottK> You have two options:
[06:05] <ScottK> 1.  File a bug against the Debian package asking for an update.  If the Debian maintainer updates it, then we get it automatically.
[06:05] <ScottK> 2.  File an Ubuntu bug in LP or package it yourself for Ubuntu.
[06:06] <eolo999> 1'39''
[06:06] <soulrider_> ScottK: if i package it myself, how do i submit it ?
[06:06] <ScottK> soulrider_: It has been years since the Debian maintainer touched the package, so the most likely path to success is package it.
[06:06] <ScottK> !revu
[06:06] <ubotu> REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU
[06:06] <ScottK> soulrider_: ^^
[06:07] <nixternal> what I did (with krename) per StevenK is I contacted the current maintainer who hasn't touched the package in about a year and a half about taking over maintainer rights, or at least helping him maintain it
[06:07] <soulrider_> im gonna chack it out
[06:07] <eolo999> 10 secs
[06:08] <soulrider_> im gonna have to go a a PC with kubuntu though to do it right? or is there any other way to create a deb package ?
[06:08] <ScottK> nixternal: I think that works for someone who knows what they are doing.
[06:08] <eolo999> upgraded!
[06:08] <nixternal> ScottK: I don't know what I am doing :)
[06:08] <nixternal> I just play a "MOTU wannabe" :p
[06:08] <ScottK> For someone with now packaging experience, I think it's better to learn here and then go to the Debian guy with a good package.
[06:08] <ScottK> nixternal: You and me both.
[06:09] <nixternal> hehe
[06:09] <ScottK> eolo999: Great
[06:09] <ScottK> eolo999: Now you should be able to just exit the pbuilder and it'll save the new config.
[06:10] <soulrider_> ScottK: i really cant compile anything by myself :P besides, im not running ubuntu at th emoment
[06:10] <alterlaszlo> ScottK, it's me (lost connection and got second name)
[06:11] <alterlaszlo> ScottK, exited pbuilder and saved
[06:11] <ScottK> soulrider_: Do you plan to run Ubuntu?
[06:11] <ScottK> alterlaszlo: Excellent.
[06:11] <alterlaszlo> ok
[06:11] <soulrider_> ScottK: uhm not anytime soon
[06:11] <alterlaszlo> and now
[06:11] <dothebart> hy... im looking for some feedback on my citadel.org debs...
[06:12] <soulrider_> installation is fast and everything but i just dont ahve the time to do it, and im hapyp with how my pc is now
[06:12] <ScottK> alterlaszlo: Now copy the pbuilder script.  cp pbuilder-feisty pbuilder-gutsy
[06:12] <dothebart> they're available at ubuntu.citadel.org/ubuntu/
[06:12] <ScottK> soulrider_: I'm a little confused why you were asking for Ubuntu to get a new version then?
[06:12] <soulrider_> ScottK: i used ubuntu for a long time and my friends use it
[06:12] <alterlaszlo> then?
[06:13] <ScottK> dothebart: Are you trying to get your packages into Ubuntu?
[06:13] <soulrider_> and its a great distro with great community, im allways int he kubuntu channel helping people
[06:13] <dothebart> if somebody is willing to do that with me, yes.
[06:14] <ScottK> alterlaszlo: Then sh pbuilder-gutsy build {full path to file}/{pacakgename-and-version}.dsc
[06:14] <ScottK> dothebart: That's what we do here.
[06:14] <ScottK> soulrider_: OK.  What do you run?
[06:14] <dothebart> :] 
[06:14] <soulrider_> ScottK: Archlinux
[06:15] <ScottK> soulrider_: Is that an Ubuntu derivative?  Where does it derive from?
[06:15] <dothebart> ScottK: what would be the next steps to take?
[06:15] <soulrider_> ScottK: Crux i believe
[06:15] <ScottK> dothebart: You want to put your packages up on REVU.
[06:15] <ScottK> !revu | dothebart
[06:15] <ubotu> dothebart: REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU
[06:16] <alterlaszlo> E: File /home/eolo/pbuilder/gutsy-base.tgz does not exist ScottK !!!
[06:16] <dothebart> *reads*
[06:16] <ScottK> soulrider_: Then maybe one of your friends would be interested in packaging it for Ubuntu
[06:16] <ScottK> alterlaszlo: Sorry.  Forgot a step.
[06:16] <alterlaszlo> ok
[06:16] <soulrider_> ScottK: my dads pc has kubuntu so its not really a problem
[06:17] <ScottK> Rename /home/eolo/pbuilder/feisty-base.tgz to /home/eolo/pbuilder/gutsy-base.tgz
[06:17] <ScottK> Then do it again.
[06:17] <ScottK> soulrider_: Great.  
[06:18] <soulrider_> ScottK: if i go there, could you help me package it ?
[06:18] <alterlaszlo> now seem better
[06:18] <ScottK> I can help some.  I've about expended my time for today.
[06:18] <ScottK> soulrider_: There are lots of people here (although the next week or so will be rough because of the developer sprint) who will help you. 
[06:18] <ScottK> soulrider_: Very open to new people here.
[06:19] <soulrider_> ok, in about 10 minutes im gonna go downstairs and try to package it
[06:19] <alterlaszlo> done!
[06:19] <ScottK> soulrider_: Most of the information you need is in the Ubuntu packaging guide and on wiki.ubuntu.com
[06:20] <ScottK> alterlaszlo: Now look in ~/pbuilder and you should see the .debs
[06:20] <soulrider_> ScottK: i ahve done some packages before
[06:20] <soulrider_> actually
[06:21] <soulrider_> now that i think of it, i packaged filelight
[06:21] <ScottK> Great.  All the better
[06:21] <soulrider_> and its in my sent items in gmail
[06:21] <soulrider_> hold on a sec :P
[06:21] <alterlaszlo> i don't find it , perhaps confusion of tho envs
[06:21] <ScottK> What did the pbuilder say at the end?  Did it give you an error?
[06:22] <alterlaszlo> no errors
[06:22] <ScottK> ... building...
[06:23] <soulrider_> ScottK: can i send you the filelight package i build for you to check out please ?
[06:23] <alterlaszlo> found
[06:23] <alterlaszlo> , sorry
[06:24] <ScottK> No problem
[06:24] <alterlaszlo> i have deb
[06:24] <ScottK> alterlaszlo: Now sudo dpkg -i filename.deb to test it (Gutsy and Feisty are close enough at this point this is a good test).
[06:27] <alterlaszlo> it works!
[06:27] <ScottK> OK
[06:28] <ScottK> Now attach the debdiff to the bug and subscribe (do not assign) the bug to ubuntu-universe-sponsors.  Mark it confirmed and unassign yourself.
[06:31] <alterlaszlo> subscribe??
[06:32] <alterlaszlo> ScottK, what is not assign but subscribe
[06:33] <ScottK> On the left colum there is an option to "subscribe someone else"
[06:33] <alterlaszlo> ScottK, understood
[06:39] <ScottK> alterlaszlo: You should also probably mention in a comment on the bug that you've built binary packages in a Gutsy pbuilder and test installed them to verify the fix.
[06:39] <alterlaszlo> ok 
[06:42] <alterlaszlo> nothing more?
[06:42] <jdong> https://launchpad.net/ubuntu/+source/ktorrent/2.1.4-0ubuntu1~feisty1
[06:42] <jdong> ^^ why has this been queued 3 days...
[06:42] <jdong> on all arches
[06:42] <jdong> while dapper and edgy all went through in a heartbeat
[06:42] <ScottK> The next thing (for Gutsy) would be to ask here for someone from UUS to upload the fix.
[06:43] <ScottK> i.e.
[06:43] <ph1zzle> hey guys
[06:43] <ScottK> If anyone from UUS is available, alterlaszlo has a fix for Bug #112140 that is ready for UUS review and upload.
[06:43] <ubotu> Launchpad bug 112140 in pythoncad "pythoncad fails to exit when all windows are closed" [Medium,Confirmed]  https://launchpad.net/bugs/112140
[06:43] <ScottK> alterlaszlo: Next step is to tell Debian about the problem.
[06:44] <alterlaszlo> ...
[06:44] <jdong> ok, all the buildd's are idle....
[06:44] <alterlaszlo> listening
[06:45] <ScottK> alterlaszlo: Go to http://www.debian.org/Bugs/ and follow the directions for reporting a bug via email.  It's somewhat complex, but the needed information is there.  Attach your patch (not the debdiff).
[06:46] <alterlaszlo> OK
[06:46] <ScottK> alterlaszlo: If you want to write up the e-mail and send it to me to check, that's fine.
[06:47] <alterlaszlo> perfect, thanks ScottK 
[06:47] <alterlaszlo> is there a 'template'?
[06:48] <ScottK> Not really.  Just read the text and put the stuff in they ask for
[06:51] <ScottK> alterlaszlo: Sent
[06:51] <alterlaszlo> thx
[07:09] <ScottK> alterlaszlo: How's it going?
[07:11] <alterlaszlo> i was eating something
[07:11] <alterlaszlo> no tried yet
[07:13] <alterlaszlo> ScottK, Have you seen the comment added by hemmet to the bug?
[07:13] <ScottK> Yes.  That's good.
[07:13] <alterlaszlo> It says we should mention the change of maintainer in changelog
[07:13] <ScottK> Oh.
[07:13] <ScottK> Yeah.
[07:13] <ScottK> That
[07:14] <ScottK> That's right.
[07:14] <ScottK> We should.
[07:14] <ScottK> Add * Changed maintainer to MOTU to the changelog just below the line about the patch.
[07:14] <ScottK> Redo the source packate (debuild -S -uc)
[07:14] <ScottK> Redo the debdiff
[07:15] <ScottK> Attached the new debdiff to the bug and delete the old one.
[07:15] <ScottK> Sorry about that.
[07:15] <ScottK> BTW, Emmett is persia here.  So you know...
[07:17] <ScottK> alterlaszlo: Does that make sense?
[07:17] <alterlaszlo> doing it
[07:17] <alterlaszlo> almost finished
[07:17] <ScottK> Great.
[07:17] <ScottK> OK
[07:17] <ScottK> How about the bug report to Debian?
[07:19] <alterlaszlo> do I have to check the box that says 'this attachment is a patch' when posting a debdiff in LP?
[07:20] <ScottK> Yes.
[07:20] <ScottK> It doesn't make a huge difference, but it's better to.
[07:21] <ScottK> It affects how it gets served back.  If you check the box it gets served back as a text file.
[07:21] <alterlaszlo> ok done posting new debdiff
[07:22] <alterlaszlo> now... i have to pause to make my son eat...
[07:22] <alterlaszlo> i'll work on debian email as soon as I can.
[07:23] <ScottK> Sure.
[07:24] <ScottK> alterlaszlo: You are going to have to fix it again.
[07:24] <ScottK> alterlaszlo: You lost a blank line in changelog that's needed.
[07:24] <alterlaszlo> sorry
[07:24] <ScottK> No problem.
[07:25] <ScottK> Just add a blank line between your entry and the line with your name/address on it.
[07:25] <ScottK> This is all good for learning.
[07:29] <alterlaszlo> i really have to go now, i'll be back later..
[07:29] <alterlaszlo> thx folks
[07:36] <ScottK> alterlaszlo: See you later.  Three isn't so bad.  My first one was 5.
[07:37] <\sh> re
[07:37] <zul> is there a uds channel yet?
[07:43] <\sh> tomorrow it starts right?
[07:48] <zul> yep
[07:59] <\sh> hmm..there's too much \sh again on this merge page...gnarf
[08:18] <_filippo_> Lamego: i think there's a character encoding problem with trademark symbol of gnome mastermind
[08:18] <Lamego> _filippo_, yes, it was my typing of the "tm"
[08:19] <_filippo_> Lamego: maybe you could use &trade;
[08:19] <_filippo_> Lamego: it works fine on the home page
[08:20] <Lamego> _filippo_, done :)
[08:21] <_filippo_> Lamego: thanks now it looks fine ;)
[08:27] <_MMA_> zul: The channel is: #uds-sevilla.
[08:57] <zul> _MMA_: thanks
[09:25] <alterlaszlo> Scottk, can I attach the dpatch file to the debian mail or paste it?
[09:26] <ScottK> Attach it.
[09:26] <alterlaszlo> the dpatch is ok?
[09:26] <ScottK> Yes.  It's got nothing Ubuntu unique in it.
[09:35] <alterlaszlo> ScottK, sent you e-mail
[09:36] <ScottK> OK.
[09:37] <ScottK> Looks good.  What will you put as the subject in the one you send to Debian (title of the bug)?
[09:42] <alterlaszlo> suggestion?
[09:42] <ScottK> pythoncad fails to exit when all windows are closed
[09:43] <\sh> destroy event not correctly catched and called?
[09:43] <ScottK> That would work too.
[09:44] <ScottK> alterlaszlo: You're reporting the but, up to you.
[09:44] <\sh> just a quick guess, no clue if it's correct
[09:49] <ScottK> alterlaszlo: It's probably better to just file the bug than spend a long time thinking about it.
[09:50] <alterlaszlo> sorry, i was skyping with some friends in London
[09:50] <ScottK> No problem.
[09:53] <Q-FUN1> has there been any talk about releasing Pidgin as an update for dapper/edgy/feisty?
[09:54] <ScottK> jdong was talking about it.
[09:54] <\sh> backport?
[09:54] <ScottK> Yes, as a backport
[09:54] <\sh> so nothing critical ;)
[09:55] <alterlaszlo> ScottK, what about 'pythoncad fails to exit'
[09:55] <ScottK> Fine with me.
[09:55] <alterlaszlo> so i'm sending it
[09:56] <\sh> just one package left for today
[09:56] <Q-FUN1> backport? why not an actual update?
[09:56] <\sh> to risky I think for dapper
[09:56] <alterlaszlo> it has been a long day...
[09:57] <ScottK> Q-FUN1: Why an actual update?
[09:57] <\sh> actually I think there is nothing wrong with gaim in dapper...
[09:57] <Q-FUNK> because pre-release versions have various pointless bugs
[09:58] <ScottK> Q-FUNK: We don't have any actual officialt pigdin packages in those repos do we?
[09:59] <Q-FUNK> we have old gaim 2.0preX
[09:59] <ScottK> Q-FUNK: As a rule, they don't do new packages as updates.  Just relevant bugs that qualify for SRU. https://wiki.ubuntu.com/MOTU/SRU
[09:59] <ScottK> I know gaim is main, but same general policy
[09:59] <\sh> Q-FUNK, 1. you have to change the name from gaim to pigdin and that means 2. all reverse deps to gaim needs to be changed...useless risk
[10:00] <\sh> use backports if you want to be hip ;)
[10:00] <ScottK> alterlaszlo: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422422
[10:00] <ubotu> Debian bug 422422 in pythoncad "pythoncad fails to exit" [Unknown,Open]  
[10:00] <Q-FUNK> nothing to do with being hip.  I'm just getting tired of the various annoyances in preX versions
[10:01] <ScottK> Q-FUNK: Then find patches that fix SRU worthy bugs and propose that.
[10:02] <alterlaszlo> Nice. Should I submit the patch for version 0.1.35 too?
[10:02] <\sh> alterlaszlo, please do :)
[10:02] <ScottK> Yes
[10:03] <alterlaszlo> it's enough to change version number, isn't it?
[10:03] <ScottK> Are the line numbers for the patch the same?
[10:03] <\sh> depends..new upstream version or new release of the package?
[10:04] <ScottK> alterlaszlo: The patch you submitted was the one for 1.35
[10:04] <alterlaszlo> oops.
[10:05] <ScottK> I'd just submit a comment on the but that says that the issue is present in 1.35 also and that the patch is for 1.35.
[10:05] <ScottK> Don't worry about the 1.33 patch.
[10:05] <Q-FUNK> hm.  no pidgin package for fesity+1 ?
[10:05] <alterlaszlo> 4th error ;)
[10:05] <ScottK> Q-FUNK: Not in Debian yet.
[10:06] <ScottK> alterlaszlo: Not a big deal.
[10:06] <Q-FUNK> since when is feisty a debian release?!
[10:06] <ScottK> Q-FUNK: Where do we get the package from?
[10:06] <Q-FUNK> not always from debian
[10:07] <ScottK> Sure.  If someone packages it first.
[10:07] <Q-FUNK> precisely and ubuntu tends to get around these first
[10:07] <ScottK> jdong was working with the draft Debian package from their SVN yesterday or earlier today.
[10:07] <Q-FUNK> ah
[10:07] <ScottK> You might ask jdong what his intent is next time he's here.
[10:08] <Q-FUNK> yup
[10:08] <Q-FUNK> good point
[10:13] <ScottK> alterlaszlo: Next step is to link the debian bug to the Ubuntu bug in LP.
[10:14] <alterlaszlo> ok
[10:14] <alterlaszlo> how?
[10:14] <ScottK> alterlaszlo: See where it says ,"Also affects another distribution"?
[10:14] <alterlaszlo> 'also affects upstream' section and add debian bug #
[10:15] <ScottK> No, another distribution.
[10:15] <ScottK> Select Debian and then feed it the URL for the bug.
[10:16] <alterlaszlo> done
[10:16] <alterlaszlo> and commented patch in deb bugs
[10:17] <ScottK> alterlaszlo: Looks perfect.
[10:17] <alterlaszlo> ok
[10:17] <ScottK> alterlaszlo: Now, since you already checked and the problem is still present upstream, it'd be polite to report it to them too.
[10:18] <alterlaszlo> i'm still asking myself how they didn't see the problem.
[10:18] <alterlaszlo> I think that thy're yousing Mac and Cocoa interface section to develop
[10:19] <ScottK> That may be.  All the more reason to tell them.
[10:19] <alterlaszlo> ok
[10:19] <alterlaszlo> lot of things to do...
[10:19] <alterlaszlo> solving the problem took 1/100 time !?!
[10:19] <ScottK> alterlaszlo: Since this is your first one all the way through, we are being VERY thorough.
[10:20] <ScottK> alterlaszlo: This way your work benifits a lot more people.
[10:22] <ScottK> Adri2000 or Lutin are you around for a DaD bug report?
[10:23] <ScottK> Look at DaD's proposed merged changelog for clamav.  The entries are not in the correct order....
[10:24] <ScottK> 0.90.2-1ubuntu1, 0.90.2-1, 0.90.1-2, and then 0.90.2-0ubuntu1
[10:27] <alterlaszlo> ScottK, notified to Art Haas pythoncad developer.
[10:27] <ScottK> Great.
[10:27] <alterlaszlo> what happens to the patch now?
[10:28] <ScottK> Now to do more on that, we need to get crimsun or someone like that on the MOTU SRU team to decide if we should add it to the pending update for Feisty.
[10:28] <ScottK> For the Gutsy patch we wait for someone in Ubuntu Universe Sponsors to review and upload.
[10:28] <ScottK> Not so many people around today.
[10:29] <ScottK> So, for now I think you've done it.
[10:29] <ScottK> Congratulations and thank you for your contribution.
[10:29] <alterlaszlo> great, i'm tired...
[10:30] <ScottK> Pat yourself on the back and take a rest then.
[10:30] <ScottK> Now you know how the process works!
[10:34] <alterlaszlo> not exactly... but I have some notions now, thanks to You ScottK 
[10:35] <ScottK> Welcome to the club, now go fix some more bugs after you get a rest.
[10:42] <dothebart> ScottK: i've joined that team...
[10:42] <ScottK> dothebart: Excellent.
[10:43] <dothebart> and i've created a citadel project
[10:44] <dothebart> now i need to wait for approval?
[10:46] <ScottK> I don't know about what's invovled in making projects on LP.  I've never done it.
[10:49] <xtknight> clamav eh?
[10:49] <xtknight> they finally patch that up good?  i remember it had a ton of bugs :)
[10:51] <ScottK> It's always worked well for me.
[10:51] <ScottK> The bigger problems IME are in the GUIs for it.
[10:51] <ScottK> Different packages...
[10:52] <xtknight> well i think the original problem is it wouldn't update via the facilities provided in the GUI..it would segfault if you tried to update klamav or clamav
[10:52] <xtknight> ive actually not used it much myself
[10:52] <xtknight> but i remember there were a barrage of bugs and i attempted to investigate..didnt get too far as i dont know how to debug Qt apps well enough....strace revealed greek
[10:52] <ScottK> That works with klamav in Feisty as long as you have the build-depends installed.
[10:53] <xtknight> i need to get back into fixing bugs though..i love you guys ;)
[10:55] <Adri2000> ScottK: re clamav on DaD - isn't it the expected behavior in this case? the current ubuntu version is 0.90.2-0ubuntu1 and is based on 0.90.1-1. even if 0.90.1-2 < 0.90.2-0ubuntu1, it is applied after 0.90.2-0ubuntu1 because no one merged before
[10:56] <ScottK> hmmmm
[10:58] <Adri2000> I mean, it's in the order the changes have been/are applied in ubuntu
[10:59] <Adri2000> currently we have 0.90.2-0ubuntu1, and now we are adding the changes of 0.90.1-2 and 0.90.2-1. since we add it after 0.90.2-0ubuntu1, we put the changelog entries at the top.
[10:59] <ScottK> Adri2000: When I look at the proposed patch on DaD, it looks in a different order than I remember it being after I grab-merged it locall.
[11:00] <ScottK> locally..
[11:01] <ScottK> The sequence here: http://adrishost.homeip.net/DaD/merges/clamav/clamav_0.90.2-1ubuntu1.patch looks sane to me.
[11:01] <ScottK> I'm in the midst of test pbuilding binaries and about to have to leave, so I'll go back and look at it again and let know you if I still think something is amiss.
[11:04] <Adri2000> clamav_0.90.2-1ubuntu1.patch is a debdiff 0.90.2-1 0.90.2-1ubuntu1. grab-merge downloads the 0.90.2-1ubuntu1 package, so it should be the same order in the changelog.
[11:31] <ScottK> Adri2000: They are different.  See http://paste.ubuntu-nl.org/19343
[11:31] <ScottK> Gotta run.
[11:41] <Adri2000> ScottK: looking at you list. if we start at 0.90.1-1, it's exactly in the same order, except that 0.90.1-2 is missing from the first list (patch). it's just because it doesn't appear in the debdiff.
[11:54] <ScottK> Right
[11:57] <ScottK> Adri2000: Agreed that's the one difference.  The sequence that is in the grabbed changelog does not make sense to me.  It is in neither date nor version order.
[11:59] <ScottK> Adri2000: I guess I'm not entirely sure what the rule is for merging the changelog in this case, but it seems to me that date or version order would be the right thing to do.
[11:59] <ScottK> Adri2000: You can tell from the changelog that 0.90.1-2 was never merged (because there's no -2ubuntu1).
[12:00] <ScottK> Adri2000: I guess I can see it your way too if I think about it really hard.
[12:01] <ScottK> Adri2000: OK.  I agree not a bug, just not what I would have expected...
[12:09] <Daviey> Hi, i want to package a shell script.  Would it be better to compile the shell script or just package the it?