[02:15] <claydoh> hugs all around, belated as they are. Sorry I missed the party
[07:42]  * superfly is busy upgrading to 10.10, and looks forward to seeing what #kubuntu-devel has been up to the last 6 months :-)
[10:26] <Riddell> what should I say at my open week talk?
[10:29] <Riddell> d/win 15
[10:29] <Riddell> tsk
[10:40] <apachelogger> Riddell:  if you used quassel that would not have happened :P
[10:50] <Riddell> apachelogger: really?
[10:50] <persia> Is there a keystroke combination to change target channels with quassel?
[10:51] <Riddell_> d/win 2
[10:51] <Riddell> apachelogger: nope, still happens
[10:52] <apachelogger> lol
[10:52] <apachelogger> you use the mouse
[10:53] <superfly> there are some keystrokes for channels... can't remember what they are, but I'm sure they are there
[10:53] <apachelogger> alt+number
[10:53] <superfly> apachelogger: any suggestions as to why my Ubuntu One KDE notifier is not working?
[10:53] <apachelogger> I think
[10:53] <persia> What happens when one has > 10 channels?
[10:53] <apachelogger> oh
[10:54] <apachelogger> you'd need to set quick access to those
[10:54] <persia> Maybe something like '/' followed by a double-digit code?
[10:54] <superfly> (specifically, it tells me it's trying to connect, but doesn't get any further)
[10:55] <apachelogger> well
[10:55] <apachelogger> there is also alt+up/down to move relative
[10:55]  * persia stops with the iron-plated featherduster
[12:29] <shadeslayer> Riddell: can we SRU qoauth 1.0.1 ?
[12:31] <shadeslayer> or put it in backports atleast
[12:32] <Riddell> shadeslayer: SRUs are only if the diff is readable
[12:33] <Riddell> shadeslayer: what's the issue? current version doesn't work at all?
[12:33] <shadeslayer> it works but mtux says repos should really have 1.0.1
[12:34] <Riddell> does mtux say why?
[12:36] <shadeslayer> no ... http://pastebin.ca/1959217
[12:36] <shadeslayer> he does give a reason as to why we should ship 0.9.90 tho
[12:37] <shadeslayer> 1.0.1 has a new API .... im pretty sure that wont go through
[12:39] <Riddell> actually the API is in 1.0, diffing 1.0 and 1.0.1 there's no API change even if the changelog says so
[12:40] <Riddell> if there's no actual bugs it sounds like a job for backports
[12:42] <shadeslayer> ok backports then
[12:50] <shadeslayer> Riddell: oh btw i had a chat with Ravi, and TNT is asking for a reference number, do you have one?
[12:50] <cozziemoto> hey guys.. maverick    I dont see  kde-dev or devel ...renamed?
[12:50] <shadeslayer> cozziemoto: uh its kde-sc-dev-latest now i suppose
[12:51] <cozziemoto> shadeslayer,  ah ok let me try that   thanks...
[12:51] <shadeslayer> jussi: ubottu needs updating to maverick, still searches for lucid packages :)
[12:51] <jussi> yeah, Ill fix it soon
[12:52] <shadeslayer> ah thanks :D
[12:52] <jussi> shadeslayer:  in the mean time, use: !info package maverick
[12:52] <shadeslayer> right :)
[12:54] <Riddell> shadeslayer: I don't have a reference number, I e-mailed the shipit people
[12:54] <shadeslayer> thanks! :)
[12:55] <shadeslayer> ill go write a mail to the TNT guy then
[12:56] <Riddell> shadeslayer: why would you do that?
[12:57] <jussi> !info bash
[12:57] <jussi> shadeslayer:
[12:57] <shadeslayer> Riddell: because they havent released the shipment to my friend yet, so ill ask them whats the exact problem
[12:57] <shadeslayer> jussi: oooh :)
[13:05] <shadeslayer> .... even indian server has slowed down today :(
[13:05]  * Nightrose shamelessly plugs http://amarok.kde.org/en/roktober/2010 for a sec
[13:05] <Nightrose> please spread :)
[13:05] <shadeslayer> Roktober!
[13:08] <shadeslayer> Riddell: oh what do you suggest for lucid? release choqok 0.9.90 with qoauth 1.0.1 ?
[13:08] <shadeslayer> or same version as maverick?
[13:09] <shadeslayer> and then put 0.9.90 and qoauth 1.0.1 in lucid backports
[13:11] <Riddell> hmm
[13:12] <Riddell> same version as maverick in lucid-proposed I guess
[13:12] <Riddell> (which may not pass but worth a shot)
[13:12] <shadeslayer> Riddell: oh it passed, pitti said ok
[13:12] <Riddell> groovy
[13:13] <Riddell> let me know when you have something for me to upload
[13:13] <shadeslayer> he is also ok if we upload 0.9.90 ...
[13:13] <shadeslayer> so its really up to you now, whatever you think is the best :)
[13:18] <Riddell> go with 0.9.90 then
[13:19] <shadeslayer> hmm... pitti had some confusion apparently, he thought maverick had 0.9.90 :P
[13:19] <shadeslayer> ( discussing this with him in #ubuntu-devel atm )
[13:22] <jussi> ok, does someone feel like explaining what "desktop activities" are, and why I have a million of them=?
[13:22] <shadeslayer> jussi: hahaha
[13:22] <shadeslayer> theyre like multiple desktops
[13:23] <jussi> mhm
[13:23] <shadeslayer> just each is independent and can be configured
[13:23] <shadeslayer> +seprately
[13:23] <jussi> so what would I use them for?
[13:23] <shadeslayer> so each has its own widget set and such
[13:24] <shadeslayer> well... you can have 2 activities, Work and Play, Work has all the work stuff open and play has your media player and such
[13:24] <shadeslayer> ( just a example )
[13:26] <jussi> hrm, they arent very intuitive or explained at all...
[13:26] <jussi> and they dont seem to have anyway of renaming them
[13:27] <shadeslayer> there is
[13:27] <shadeslayer> jussi: go to a activity > right click > desktop settings
[13:27] <shadeslayer> and on the left click activity
[13:28] <jussi> hrmph
[13:28] <shadeslayer> you can also have a netbook activity along with a desktop activity
[13:29] <jussi> perhap right click on the activity when you have the list of activities opne (activity cashew, activities) would be helpful
[13:29] <jussi> Im beginning to understand now, they are sort of like an overlay of widgets.
[13:30] <jussi> how do I add the netbook activity?
[13:30] <shadeslayer> jussi: same activity setting, there are 3-4 options listed there
[13:30] <shadeslayer> afaik its search and containment
[13:31] <jussi> ahh yes.
[13:31] <jussi> interesting
[13:32] <Riddell> shadeslayer: on bug 656196 you removed the Hindi symbol from CurrencyUnitSymbols, is that deliberate?
[13:33] <shadeslayer> uh.. no .. that seems to be a mistake
[13:34] <shadeslayer> fixing
[13:36] <shadeslayer> err
[13:36] <shadeslayer> Riddell: the earilier symbol was the old one i think
[13:36] <shadeslayer> thats why i replaced it with the new symbol
[13:37] <Riddell> best to keep it though I think, incase there are documents that use the old Hindi one
[13:37] <shadeslayer> earlier it was : CurrencyUnitSymbols=Rs.,रू,INR
[13:38] <shadeslayer> that रू is replaced by the new symbol
[13:39] <shadeslayer> ill keep it
[13:39] <apachelogger> superfly: oh about u1 - it is called the upstream-broke-compatibility effect, for more info see the associated bug report
[13:46] <Riddell_> shadeslayer: hmm, this is weird
[13:46] <Riddell_> your patch has र as the old Hindi symbol
[13:46] <Riddell_> but the sources have रू
[13:46] <shadeslayer> 0_o
[13:47] <Riddell_> http://websvn.kde.org/trunk/KDE/kdebase/runtime/localization/currency/inr.desktop?revision=1177799&view=markup also has रू
[13:47] <Riddell_> so where did the र come from in your patch and what's the relationship to रू ?
[13:47] <shadeslayer> ill make a new patch hold on, ill keep that रू symbol
[13:48] <shadeslayer> no idea :S
[13:49] <ulysses> shadeslayer: after some time the load gone high again, I don't know what could be the problem...
[13:51] <Riddell_> http://en.wikipedia.org/wiki/Indian_Rupee doesn't list either of those Hindi signs, it just mentions 'Devanagari consonant "र"'
 so where did the र come from in your patch and what's the relationship to रू ?
[13:53] <al> they have the same base character
[13:53] <al> the second one has combining character added
[13:53] <al> "DEVANAGARI VOWEL SIGN UU" is what unicode calls it
[13:54] <shadeslayer> yeah रू is called "Roo" and र is "Ra"
[13:54] <Riddell_> is either used for a Rupee symbol?
[13:55] <shadeslayer> well रू is part of pronouncing Rupee
[13:56] <shadeslayer> i think thats how we write amounts in hindi, रू foo
[13:58] <superfly> apachelogger: oh right, gotcha
[14:08] <shadeslayer> Riddell: http://pastebin.com/tyxcvicG
[14:09] <Riddell> shadeslayer: lovely
[14:09] <shadeslayer> also could you commit that to kde? http://pastebin.com/KKm8JYL7
[14:09] <Riddell> please attach to bug 656196
[14:09] <shadeslayer> yes, im doing that right now :)
[14:09] <Riddell> yes will do the upstream commit
[14:11] <shadeslayer> uploaded new debdiff
[14:12] <Riddell> committed to trunk
[14:12] <shadeslayer> whee :)
[14:15] <Riddell> I'll e-mail release-team and kde-packager too
[14:30] <sheytan> I'm happy 10.10 user now. Thank you guys for this one ;D
[14:33] <Riddell> sheytan: great!
[14:33] <Riddell> shadeslayer: qoauth and choqok uploaded to lucid-proposed, awaiting approval
[14:33] <sheytan> Riddell yeah :D
[14:33] <Riddell> thanks for getting that done (although it's not complete yet of course)
[14:36] <sheytan> Hey, if i have some kubuntu ppas like kubuntu-ppa, or backports for lucid, do i have to remove them and add back for mm?
[14:37] <Riddell> sheytan: the upgrade will remove them
[14:37] <shadeslayer> Riddell: whee :D
[14:37] <Riddell> you can add them back after the upgrade if you wish
[14:37] <sheytan> Riddell i have turn them off before the upgrade :D
[14:37] <sheytan> So, i have to remove by hand now and add them back?
[14:38] <shadeslayer> Riddell: natty repos open? :O
[14:38] <ScottK> sheytan: Update manager will do that.
[14:38] <ScottK> shadeslayer: No
[14:38] <shadeslayer> https://launchpad.net/ubuntu/natty/+source/choqok
[14:38] <ScottK> Toolchain upload going on
[14:38] <shadeslayer> ScottK: ^
[14:38] <shadeslayer> ah right then
[14:39] <sheytan> ScottK but as i said. they where off when i upgraded.
[14:40] <ScottK> sheytan: I misread what you said.  Sorry.
[14:40] <sheytan> ScottK no problem, but now i have to remove them, and add again, right?
[14:41] <Riddell> sheytan: only add them if there is something you want from them
[14:41] <ScottK> Right.
[14:43] <sheytan> ok, thank you guys :)
[14:43] <sheytan> we've done well with kpk :D
[14:43] <sheytan> i really like it now :D
[14:45] <ScottK> And danti isn't here to hear about it.
[14:45] <shadeslayer> yeah ^ :(
[15:01] <sheytan> ScottK well, he already knows that :D
[15:02] <sheytan> Rekonq is veeery fast :D
[15:02] <sheytan> nice :D
[15:02] <ScottK> OK
[15:03] <shadeslayer> sheytan: awesome :D
[15:04] <sheytan> shadeslayer i'm now adding my bookmarks. Will stay with it for a while
[15:04]  * sheytan is wondering if the new 64bit flash will work with rekonq
[15:04] <shadeslayer> sheytan: hmm... im thinking we need a bookmark migration tool for rekonq
[15:04] <shadeslayer> it does
[15:04] <sheytan> shadeslayer you do.
[15:05] <sheytan> and tell me how :D
[15:05] <shadeslayer> then you can port your bookmarks from chromium/firefox
[15:05] <shadeslayer> sheytan: itll need to be coded
[15:05] <sheytan> i mean, is it enough when i put flash to mozilla folder?
[15:05] <shadeslayer> yes
[15:05] <sheytan> ok, thank you :)
[15:15] <sheytan> Riddell is Ubuntu Open Week a good time to become a kubuntu member? :D
[15:17] <sheytan> shadeslayer when i click on a bookmark using the wheel, much tabs open :D
[15:17] <sheytan> why? :D
[15:27] <Riddell> sheytan: no, it's a series of talks unrelated to membership
[15:49] <sheytan> anyone here with 4.5.2 on 10.10?
[15:54] <yuriy_work> congratulations on the release everyone!
[16:04] <Riddell> shadeslayer or anyone around in an hour for the Kubuntu Open Week talk?
[16:11] <Sput> sheytan: flash works with rekonq
[16:11] <ScottK> Here too
[16:11] <sheytan> i meant the 64bit ;)
[16:12] <Sput> yes, me too
[16:19] <sheytan> ok, thanks :)
[16:24] <allee> I'll work on Bug 658047.   Is there a wiki page that lists procedure / tools to handle pkging with bzr ubuntu/debian  only checkouts?
[16:25] <Riddell> allee: bzr-buildpackage can do a lot
[16:26] <Riddell> but often I just copy over the debian/ directory from bzr to the package, it's as easy as looking up bzr-buildpackage commands sometimes
[16:26] <shadeslayer> Riddell: sorry not this time :(
[16:26] <Riddell> shadeslayer: ok
[16:26] <allee> Riddell: thx.  I'll play with it.
[16:56] <Riddell> ** Kubuntu talk at Ubuntu Open Week in #ubuntu-classroom in 5 minutes
[16:57] <maco> Riddell: are you giving it?
[16:58] <Riddell> maco: unless someone else turns up in the next two minutes
[16:58]  * maco hides
[16:58]  * ulysses hides behind maco
[17:08] <shadeslayer> apachelogger: whats a KMimeType::Ptr  , i dont understand the api docs
[17:53] <Miritad> what is the minimum requirements to join the kubuntu devel team?
[17:54] <ScottK> Miritad: Show up and do stuff.
[17:54] <ScottK> Riddell: I've figured a ~OK work around for Bug #641712 (it's in the bug).  How do we get that into the release notes now?
[17:55] <Riddell> Miritad: you do have to be good looking though, that's important
[17:55] <Miritad> Riddell: yeah, I am ;)\
[17:56] <Riddell> Miritad: excellent, welcome along
[17:56] <Riddell> ScottK: it's a wiki page, edit https://wiki.kubuntu.org/MaverickMeerkat/ReleaseNotes
[17:56] <ScottK> Riddell: The main ones aren't though.
[17:56] <ScottK> I'll edit that one.
[17:57] <ScottK> That gets copied onto ubuntu.com
[17:57] <apachelogger> shadeslayer: a special pointer type that allows that the same object is hold within multiple scopes, the object will only be deleted once all reference holders are deleted
[17:57] <Riddell> ScottK: according to https://lists.ubuntu.com/archives/ubuntu-announce/2010-October/000139.html the release notes are http://www.ubuntu.com/getubuntu/releasenotes/1010 which forward to that wiki page
[17:58] <shadeslayer> oic
[17:58] <apachelogger> shadeslayer: say you have instance of class A and you want to it using both an instance of both class B and class C and it is not clear if B or C needs to delete the object, both will do so, however the actual deletion will only be carried out if both have done so
[17:58] <ScottK> Riddell: OK.  Thanks.
[17:59] <Riddell> Miritad: what sort of a person are you likely to be?  a packager, triager, documenter, coder, artist, html-er...?
[17:59] <shadeslayer> apachelogger:  got it
[17:59] <apachelogger> k
[17:59] <shadeslayer> Riddell: artist, wikier
[17:59] <shadeslayer> oh artist is already there :P
[18:00] <Miritad> Riddel: a 17-year-old boy, IOI medalist, and coder
[18:00] <Riddell> we could dowith some wikiers, our wiki pages have plenty of holes
[18:00] <shadeslayer> Quintasan: you have competition :P
[18:01] <Riddell> Miritad: what's an IOI medalist?
[18:01] <shadeslayer> me too .. but then im almost 20 now :S
[18:01] <ScottK> Miritad: What languages do you have experience with?
[18:02] <Miritad> Riddell: International Olympiad in Informatics. I speak C/C++ natively, and most of my experience is in algorithms
[18:02] <Riddell> golly
[18:03] <nigelb> Riddell: thank you; great session :)
[18:05]  * apachelogger is famous now \\o/
[18:05]  * apachelogger hugs Riddell
[18:05] <shadeslayer> apachelogger: whatcha do? :D
[18:05] <shadeslayer> also
[18:06] <apachelogger> shadeslayer: jr mentioned me in his session ^^
[18:06] <shadeslayer> oic
[18:06] <shadeslayer> apachelogger: i thought you had a blog, thats why you were famous :P
[18:06] <apachelogger> that old thing is only for when I am in a flame mood ;)
[18:07] <apachelogger> ohh
[18:07] <apachelogger> battery is running low
[18:07] <apachelogger> omg
[18:07] <shadeslayer> btw, suppose i want to pass what  KMimeType::findByUrl() to  KMimeType::name(), how do i do that?
[18:07] <shadeslayer> not so fast!
[18:07] <shadeslayer> tell me that  :P
[18:12] <shadeslayer> meh nvm
[18:15] <Riddell> yay, we made the dot http://dot.kde.org/2010/10/11/plasma-mobile-technology-preview-features-kubuntu-1010
[18:15] <Riddell> those guys are far more harsh in what they will publish than when I was the only editor
[18:16] <shadeslayer> whee
[19:11] <apachelogger> shadeslayer: did you figure it out?
[19:11]  * apachelogger got cut off by some very weird bug
[19:11] <shadeslayer> yes, sort of
[19:11] <shadeslayer> one sec
[19:11] <apachelogger> ScottK: did you ever get a grey screen on your netbook, looking like a window background drawn all over the screen
[19:12] <apachelogger> with alt+tab being disfunct
[19:12] <shadeslayer> apachelogger: http://pastebin.com/aa9jfw8n
[19:12] <shadeslayer> that makes this appear http://imagebin.ca/view/puOba3.html
[19:12]  * apachelogger is not sure but suspects it could be something Xish
[19:12] <ScottK> apachelogger: Sounds like plasma failed to start.
[19:12] <shadeslayer> on clicking magnet links
[19:12] <apachelogger> ScottK: no in session
[19:12] <ScottK> Oh.
[19:12] <apachelogger> why switching between windows
[19:12] <apachelogger> s/why/while
[19:12] <ScottK> Nope.
[19:12] <apachelogger> ok
[19:13]  * apachelogger needs to look into that
[19:13] <apachelogger> very nasty, I only got rid of it by restarting X
[19:13] <shadeslayer> apachelogger: any ideas why it doesnt load the application?
[19:13] <shadeslayer> based on contents of URL
[19:13] <apachelogger> shadeslayer: is that a valid magnet url?
[19:14] <apachelogger> considering it does not have a double slash after the magnet:
[19:14] <shadeslayer> apachelogger: yes, also apt:rekonq wont work now, brings up same dialog
[19:14] <shadeslayer> no its a magnet:?foo link
[19:14] <apachelogger> well
[19:14] <apachelogger> running by name might be a bit fishy to begin with
[19:14] <apachelogger> IMHO
[19:15] <shadeslayer> running by name?
[19:15] <apachelogger> shadeslayer: also for the sake of correctness, you really should use a KMimeType::Ptr type rather than KSharedPtr
[19:15] <apachelogger> shadeslayer: I gather you Krun the url by the name of the mimetype, no?
[19:17] <shadeslayer> ok first issue fixed, still dont understand what you mean by 2nd issue
[19:18] <apachelogger> http://api.kde.org/4.x-api/kdelibs-apidocs/kdecore/html/classKSycocaEntry.html#ad4bec37ac129fe86b3eae0b3a8cbd643
[19:19] <shadeslayer> right, that name() call?
[19:19] <apachelogger> well, what does it return?
[19:19] <shadeslayer> mimetype?
[19:19] <apachelogger> is that actually the mimetype name?
[19:19] <apachelogger> shadeslayer: are you sure about that?
[19:20] <shadeslayer> er, i think so
[19:20] <apachelogger> considering it does not work I would not be sure about that... ;)
[19:20] <shadeslayer> :)
[19:20] <shadeslayer> so what *does* name() return?
[19:21] <apachelogger> well gdb it
[19:21] <apachelogger> or add a kDebug()
[19:23] <shadeslayer> rekonq(22115): couldn't create slave: "Unable to create io-slave: klauncher said: Error loading 'apturl %u'.  << something relevant?
[19:24] <shadeslayer> hmm .. no
[19:26] <cmagina> Where is the ppa for the Ubuntu One KDE stuff?
[19:27] <shadeslayer> apachelogger: damn, i cant get the output of that var
[19:27] <shadeslayer> apachelogger: http://pastebin.com/9vAsajQr
[19:28] <shadeslayer> stupid frigging chromium
[19:33] <shadeslayer> heh.. i dont believe it, i actually like the menubar in konqueror :S
[19:34] <apachelogger> :P
[19:34] <shadeslayer> apachelogger: doesnt mean im switching sides :P
[19:35] <shadeslayer> anyways, whats the problem with name()? i cant seem to get the debug value out of it
[19:35] <apachelogger> kdebugdialog
[19:36] <shadeslayer> right
[19:39] <shadeslayer> application/octet-stream
[19:39] <shadeslayer> rekonq(24264) ProtocolHandler::preHandling: OMG  values here "application/octet-stream"
[19:39] <shadeslayer> hmm
[19:40] <shadeslayer> apachelogger: seems fine to me... whats the problem?
[19:40] <shadeslayer> thats from apt:rekonq
[19:40] <apachelogger>  the problem is that you are handling by mimetype rather than protocol I suppose?
[19:40] <apachelogger> the name itself seems to be fine
[19:40] <apachelogger> shadeslayer: how does konqueror do it?
[19:40] <shadeslayer> apachelogger: couldnt find out
[19:41] <apachelogger> you did not make your homework :P
[19:41] <apachelogger> someone else found it :P
[19:41] <apachelogger> using only one grepy :P
[19:41] <shadeslayer> thats what im using
[19:41] <shadeslayer> but the keyword makes all the difference
[19:42] <apachelogger> how
[19:42] <apachelogger> about
[19:42] <apachelogger> proto
[19:43] <shadeslayer>  in src/konqmainwindow.cpp ?
[19:43] <shadeslayer> ./src/konqmainwindow.cpp:        url = KParts::BrowserRun::makeErrorUrl(KIO::ERR_UNSUPPORTED_PROTOCOL, url.protocol(), url.url());
[19:43] <apachelogger> sounds righty
[19:43] <apachelogger> well
[19:43] <apachelogger> well that line there does not sound right since it seems to go for unsupported proto :P
[19:43] <apachelogger> which for that matter would also be useful I suppos
[19:43] <apachelogger> e
[19:47] <shadeslayer> apachelogger: theres a whole bunch of code that i think handles that stuff, but idk where it ends :P
[19:47] <apachelogger> and that my dear minion is the homework :P
[19:47] <apachelogger> shadeslayer: it is not so much a question of where it ends than what it does
[19:48] <apachelogger> in particular what it does that you need to do too in rekonq
[19:48] <shadeslayer> openUrl() will that help me?
[19:49] <apachelogger> OTOH I  always was in favor of using konqueror with the webkit kpart since that cuts off all those silly issues of a new browser :P
[19:49] <apachelogger> shadeslayer: possibly
[19:52] <shadeslayer> apachelogger: btw konqueror is broken while opening magnet links too
[19:52] <apachelogger> more likely the protocol file is bogus
[19:53] <shadeslayer> Could not start process Unable to create io-slave:
[19:53] <shadeslayer> klauncher said: Error loading 'ktorrent '%u''.
[19:53] <shadeslayer> .
[19:54] <apachelogger> see
[19:54] <apachelogger> now that is wrong
[19:55] <apachelogger> that ''%u'' is surely the problem there
[19:55] <shadeslayer> oh yes
[19:55] <shadeslayer> i figured that bit out ;)
[19:58] <shadeslayer> aha! Exec=ktorrent %i -caption "%c" %u
[19:58] <shadeslayer> see right there
[19:58] <shadeslayer> that needs to be fixed in ktorrent.desktop i bet
[19:58] <shadeslayer> Exec=ktorrent %i -caption "%c" ?
[19:59] <shadeslayer> apachelogger: ^
[19:59] <apachelogger> eh?
[19:59] <apachelogger> why?
[19:59] <apachelogger> whut?
[19:59] <shadeslayer> ktorrent.desktop
[20:00] <apachelogger> not sure what you are getting at here
[20:00] <shadeslayer> maybe it doesnt load because it has that %u there?
[20:00] <apachelogger> the desktop file aint got nothing to do with the protocol
[20:00] <apachelogger> the Exec in the protcol defines the binary, not the desktop file name
[20:01] <apachelogger> so upon execution of the protocol Exec line it will expand %u and run the first ktorrent binary it can find in PATH with the expanded %u
[20:20] <apachelogger> Nightrose: butterfly butterfly butterfly
[20:20] <Nightrose> apachelogger: honey honey honey pink pony?
[20:21] <Riddell> they've developed a new language!
[20:21] <apachelogger> Nightrose: unicorn fart!
[20:21] <apachelogger> rororororroktober \o/
[20:21] <Nightrose> \o/
[20:21] <apachelogger> you know, that thing is almost as old as my life in FLOSS ;)
[20:22] <Nightrose> :P
[20:22] <Riddell> rbelem: you made it onto KDE Dot News!
[20:22] <Riddell> well your work did
[20:22] <apachelogger> rbelem's work is famous now \o/
[20:24] <rbelem> :-D
[20:24] <rbelem> \o/
[20:25] <apachelogger> oh oh, so I was doing my maths homework and got overwhelmed by unicorns
[20:25] <apachelogger> sqrt(192) = rainbows
[20:25]  * apachelogger hopes that is about right and hugs Nightrose
[20:26]  * Nightrose hugs apachelogger
[20:26] <Nightrose> apachelogger: i'm sure it is
[20:26]  * rbelem is checking the kde dot news :-)
[20:26] <apachelogger> yay
[20:29] <shadeslayer> apachelogger: actually krunner begs to differ :P
[20:29] <apachelogger> shoot
[20:30] <rbelem> wohooo!!! :-D
[20:30] <apachelogger> yeeehaaaa
[20:30] <shadeslayer> krunner says its, 13.856406, so i bet krunner is broken
[20:30] <apachelogger> well
[20:30] <apachelogger> it sure is
[20:30] <apachelogger> it surely got more digits than that
[20:30] <rbelem> plasma-mobile rulez!!! \o/
[20:31] <rbelem> thanks guys
[20:31] <apachelogger> rbelem: now if only markey would get knut to send us n900s ^^
[20:31] <shadeslayer> rbelem:  we just need N900's to make it popluar
[20:31] <rbelem> you rock!
[20:31]  * shadeslayer needs one too
[20:31] <rbelem> eheheh
[20:32] <shadeslayer> apachelogger: dude, toolchain isnt done yet
[20:32] <shadeslayer> cjwatson told me to wait :)
[20:32] <shadeslayer> everyone really
[20:32] <apachelogger> of natty?
[20:32] <shadeslayer> yes
[20:32] <apachelogger> isnt natty frozen?
[20:32] <shadeslayer> lol... not really :P
[20:33] <shadeslayer> toolchain wont be done for another few days
[20:33] <apachelogger> back in the days the new series was frozen until the toolchain was done
[20:33] <shadeslayer> it is .. waiting for toolchain
[20:33] <apachelogger> so
[20:33] <apachelogger> what is the problem? :P
[20:34] <shadeslayer> that you cant start merging atm ?
[20:34] <shadeslayer> because toolchain isnt done yet?
[20:35] <apachelogger> well you can, you just cannot merge and testbuild and stuff and star blinky
[20:35] <apachelogger> s/merge/upload
[20:38] <shadeslayer> off to sleep...
[21:07] <ScottK> debfx: Congratulations.
[21:08] <debfx> ScottK: thanks
[21:10] <Riddell> what's he being congratulated for?
[21:11] <ScottK> Riddell: He's MOTU now.
[21:11] <Riddell> gosh, a master of the universe
[21:11] <debfx> too bad I can't upload yet ;)
[21:11] <debfx> until natty is open
[21:12] <ScottK> All dressed up and no where to go ...
[21:12] <shadeslayer> oh
[21:12] <shadeslayer> debfx: congrats
[21:13]  * apachelogger cannot stop wondering how shadeslayer can write while sleeping
[21:13] <apachelogger> debfx: congrats
[21:13] <shadeslayer> apachelogger: i started watching House :p
[21:13] <apachelogger> shadeslayer: you can sleep, watch house and sleep at the same time :O
[21:14] <shadeslayer> no... i didnt go to sleep, i started watching house... after i left season 5 in the middle
[21:14] <ari-tczew> debfx: enjoy the merging packages :)
[21:16] <shadeslayer> also, i found a bug in kpk
[21:16] <shadeslayer> so trying to see where it originates ...
[21:18]  * apachelogger sings the theme song from the last unicorn
[21:19] <shadeslayer> ah well.. when dantti returns ill tell him
[21:19] <shadeslayer> now really really off to sleep, its 2 AM here ....
[21:19] <apachelogger> he said. and will yet return in at least 30 minutes :P
[21:20] <shadeslayer> apachelogger: keep waiting and see :>
[21:20] <apachelogger> no, I shall be in bed at that time :P
[21:20] <debfx> ari-tczew: I though you were doing all the merging and syncing this cycle :P
[21:20] <ulysses> it's only 22:20 here
[21:20] <apachelogger> calculus at 8am
[21:21] <ari-tczew> debfx: unfortunately not, not enough time. :)
[21:23]  * apachelogger looks at the empty champagne bottles still rolling around
[21:24] <ari-tczew> now I'm waiting with coolbhavi to merging natty.
[21:24] <apachelogger> Nightrose: we need a post-party bot
[21:24] <ulysses> apachelogger: just for you: http://www.youtube.com/watch?v=P9dpTTpjymE
[21:24] <apachelogger> ulysses: I no :P
[21:27] <debfx> oh no, I can see private bugs now, that triples the number of open bugs in virtualbox ...
[21:27] <apachelogger> hehe
[21:31] <ulysses> hm, I found some untranslatable message in kpkp
[21:31] <ulysses> kpk
[21:34] <Riddell> ulysses: like what?
[21:35] <ulysses> Riddell: some category names like Science & Engineering, Developer Tools, Themes & Tweaks
[21:39] <sheytan> shadeslayer can you shoot for me a screenshot of your font settings?
[21:40] <Riddell> ulysses: hmm, I don't remember where those strings come from
[21:40] <Riddell> but it'll be .desktop files somewhere
[21:40] <ulysses> Sure, I don't find they in the translation memory.
[21:40] <sheytan> Riddell ulysses aren't they in app-install-data package somwhere?
[21:43] <Riddell> /usr/share/app-install/categories.xml looks likely
[21:43] <Riddell> dunno how that's ment to get translated
[21:44] <sheytan> dantti should know, but he's not here
[22:07] <apachelogger> hm
[22:07] <apachelogger> oh
[22:07] <apachelogger> I do hate the translation stripping
[22:07] <apachelogger> I do hate it so much
[22:07] <Riddell> mm
[22:07] <Riddell> those solid actions are annoying
[22:07] <apachelogger> *nod*
[22:08] <Riddell> afiestas__: ping
[22:08] <Riddell> afiestas__: the rc4 of bluedevil we have is looking for the wrong translations catalogue, I see it has been fixed in git
[22:08] <Riddell> how do I get the patch
[22:10] <Riddell> ooh I worked it out!
[22:10] <Riddell> my git foo must be improving
[22:10] <apachelogger> :)
[22:12] <bbigras> I saw a little bug while installing kubuntu 10.10. Where can I get that installer's (ubiquity I think) code?
[22:14] <ScottK> bbigras: apt-get source ubiquity
[22:15] <bbigras> ScottK: thanks
[22:15] <ScottK> bbigras: No problem.  Thanks for looking into it.
[22:16] <bbigras> ScottK: :)
[22:17] <Riddell> bbigras: it's not a simple programme mind
[22:18] <bbigras> Riddell: thanks for the advice.
[22:19] <bbigras> there's a lot of dependencies
[22:20] <bbigras> Is the kubuntu's installer a modified version of the Ubuntu's one?
[22:32] <Riddell> bbigras: it's the same programme, they have different frontends
[22:33] <bbigras> Riddell: oh, thanks


 Qt 5.15 bugs status: … 6 bugs are fixed, 2 are in Debian's DELAYED queue, 7 bugs are open and need fixing. … https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=qt5.15
 ack. thanks
 I will probably bump severities to serious soon, and try to NMU the remaining bugs if I have time.
 And when we have the new series and the new toolchain is uploaded, I will prepare a new PPA.
 awesome. thank you!


[19:46] <Ankman> hi
[19:47] <avoine> hello
[19:48] <Ankman> i want to upgrade to the new ubuntu release. but the computer has no display and no keyboard etc. so i access it via ssh...
[19:49] <Ankman> i used 'do-release-upgrade' before, but it always fails as it seem it wants to open an "x-dialog" at some point...
[19:49] <Ankman> and 'do-release-upgrade' seems to have no options. anyway, if i edit the /etc/apt/sources.list, just put the new ubuntu name (version's name) there and run aptitude (update and upgrade). shouldn't that work?
[19:55] <avoine> Ankman: yep that would work
[20:00] <Ankman> ty :-)
[21:21] <Ankman> avoine: well here i go. i'll blame it on you if it fails ;-)
[21:33] <Ankman> nah, doing do-upgrade thing again
[21:33] <Ankman> i exported DISPLAY to ""
[21:33] <Ankman> logged in via ssh, getting
[21:33] <Ankman> Continue running under SSH?
[21:33] <Ankman> This session appears to be running under ssh. It is not recommended
[21:33] <Ankman> to perform a upgrade over ssh currently because in case of failure it
[21:33] <Ankman> is harder to recover.
[21:33] <Ankman> as it's supposed to be
[21:33] <Ankman> wish me luck :-)
[21:48] <Ankman> You have to download a total of 1235 M. This download will take about
[21:48] <Ankman> 1 hour 20 minutes with your connection.


[15:45] <a1fa> hey how is steam integration with budgie?
[17:46] <fossfreedom> alfa: just fine.  Just make sure you meet the steam game hardware requirements and you are good to go.
[17:56] <a1fa> thanks fossfreedom


[00:26] <cjohnston_> Would someone take a look at python(3)-urwid with me.. I would like to request a merge, but I'm unable to figure out the delta and if it needs to be merged or if the delta can be removed and synced.
[08:06] <dholbach> good morning
[08:24] <geser> good morning
[11:52] <bdrung> cjohnston: for what?
[12:16] <cjohnston> bdrung: bug #1139097
[12:35] <bdrung> cjohnston: you're welcome :)
[13:00] <jokerdino> hey guys, our package, on the course of making it to the archive, seems to be stuck in the NEW queue. is there anything that can be done?
[13:01] <tumbleweed> jokerdino: Debian or Ubuntu's NEW queue?
[13:01] <tumbleweed> either way, not much to be done, just sit back and wait
[13:01] <jokerdino> tumbleweed: the Ubuntu queue. it's been in the queue for a couple days now.
[13:02] <tumbleweed> jokerdino: reviewing new packages takes time
[13:02] <jokerdino> ah, I thought MOTU's review is enough?
[13:02] <tumbleweed> no. ftp-masters in Debian, and archive-admins in Ubuntu do a final review
[13:03] <tumbleweed> mostly checking that the package is distributable
[13:03] <jokerdino> right then. i am just worried about the feature freeze deadline.
[13:03] <tumbleweed> it's in NEW before the freeze, so that's ok
[13:03] <tumbleweed> also, sounds like the freeze may go away :P
[13:04] <jokerdino> haha, i dont know
[13:04] <jokerdino> tumbleweed: also, i think you would be a good guy to bounce some stuff off.
[13:04] <tumbleweed> right now, I'd bet on it going away
[13:04] <jokerdino> the package I am talking about is a unity tweak tool. the rolling release might break our package any time.
[13:05] <tumbleweed> that's to be expected in any development release
[13:05] <tumbleweed> rolling just means the development release rolls for longer :P
[13:05] <jokerdino> for another year or so.
[13:05] <tumbleweed> so, if it breaks, fix it ASAP
[13:05] <jokerdino> so, in that case of breakage, will the review work fasteR?
[13:06] <tumbleweed> probably not, but after several uploads, if your sponsors agree, you can apply for PPU rights
[13:07] <jokerdino> actually, that's sorta what I have in mind.
[13:07] <jokerdino> the rolling release idea got me confused
[13:08] <jokerdino> and i think it is more than likely they will get on rolling.
[13:08] <jokerdino> the discussion invitation seems namesake.
[13:08] <foxx2> morning all! does anyone here have any idea how to remove 'fuzz' from a quilt patch? im creating two patches, the first one applies fine, the second doesn't.. patch works outside of pdebuild, but not inside.. docs seem to suggest its due to fuzzing not being accepted in dpkg-source/dpkg-buildpackage.. but i cant seem to find anything that explains how to fix this problem.. any thoughts?
[13:09] <foxx2> (done the usual homework, my google-fu fails me this time)
[13:10] <tumbleweed> quilt push; quilt refresh (repeat for all patches)
[13:10] <foxx2> thanks - ah, i didnt do the push on each step, only the refresh. let me try that, sec
[13:11] <tumbleweed> some may not apply with a push, then things get extra fun
[13:11] <foxx2> heh, im scared.
[13:23] <foxx2> tumbleweed: sadly that still failed :X if you have a moment, would you mind reviewing on pastebin? http://pastebin.com/ALJf6id1 - its got the command sequence i used, the output of pdebuild, and the patch contents.. ive tried so many combinations to make this work :/
[13:23] <foxx2> its not even a complex patch, its like 1 line lol
[13:23] <foxx2> 1 line patch on a 3 line file :X
[13:31] <tumbleweed> foxx2: what's the output of debuild -S -uc -us
[13:31] <tumbleweed> also, why are you using --include-binaries?
[13:32] <foxx2> same output.. include-binaries because otherwise it refuses to add the precompiled binary files :/
[13:33] <tumbleweed> why are you precompiling binary files?
[13:33] <foxx2> (just in case - http://pastebin.com/gtxDi8d4 )
[13:33] <foxx2> oh, its for an existing non-free software  called Atlassian Bamboo
[13:33] <tumbleweed> sure
[13:33] <foxx2> they dont give the source away :/
[13:34] <tumbleweed> --include-binaries is about modifications you've made to the source package, not the source you got from upstream
[13:34] <foxx2> ohhh
[13:34] <tumbleweed> the manpage says: "Add all modified binaries in the debian tarball."
[13:34] <foxx2> okay that makes sense, i shall remove that thenm
[13:35] <tumbleweed> yes
[13:35] <tumbleweed> if you find yourself using it, you are probably doing something wrong
[13:35] <foxx2> sadly same hunk error still lol
[13:35] <foxx2> haha okay :)
[13:35] <tumbleweed> right, so it looks like dpkg-source thinks that you haven't got any patches applied
[13:35] <tumbleweed> try quilt pop -a; then debuild -S ?
[13:35] <foxx2> was just aboutt o say, should i try pop - sec
[13:36] <tumbleweed> (I don't know why it thinks that, though because it should handle that situation)
[13:36] <foxx2> same - http://pastebin.com/qrAbENq2
[13:36] <tumbleweed> but if you quilt push, they apply?
[13:37] <foxx2> quilt push; quilt apply?
[13:37] <tumbleweed> quilt push -a
[13:38] <tumbleweed> (quilt doesn't have an apply command)
[13:38] <foxx2> odd that seems to have only applied 1 patch
[13:38] <foxx2> http://pastebin.com/5p1pYj0C
[13:38] <tumbleweed> oh, I think you misread they as then
[13:38] <foxx2> ahh sorry lol
[13:39] <tumbleweed> I thought you had two patches? I only see one there
[13:39] <foxx2> the fix-debian-target.patch doesnt seem to come up
[13:39] <foxx2> yeah lemme try pop again, sec
[13:39] <foxx2> okay there we go;
[13:39] <foxx2> http://pastebin.com/BXBGNB7k
[13:39] <foxx2> seems to apply without problem
[13:40] <tumbleweed> weird
[13:40] <foxx2> is this a common problem?
[13:40] <tumbleweed> no
[13:40] <foxx2> lol well thats just great.. anything i could look at that might assist in debugging? any verbose output or anything?
[13:41] <foxx2> not sure if this is relevant but
[13:41] <foxx2>  $ cat src/webapp/WEB-INF/classes/bamboo-init.properties.rej
[13:41] <foxx2> cat: src/webapp/WEB-INF/classes/bamboo-init.properties.rej: No such file or directory
[13:41] <tumbleweed> no, not relevant
[13:41] <tumbleweed> you sure you haven't made any modifications to src/webapp/WEB-INF/classes/bamboo-init.properties that aren't represented in the patches?
[13:42] <tumbleweed> my guess is that quilt is basing the patches against something that wasn't the original source
[13:42] <tumbleweed> (it backs up the original source to the .pc directory, when you quilt add a file, so that it can generate diffs)
[13:42] <foxx2> almost 100% positive.. i even did all this from hand 3 times in a row with no automation just to be sure
[13:42] <tumbleweed> so, try extract the upstream tarball in a new directory, copy your debian directory in, and see if the quilt patches apply
[13:42] <foxx2> okay 2 secs
[13:43] <foxx2> (ty for the help btw, much appreciated)
[13:43] <tumbleweed> slow day today (or I'm being lazy, or something) :)
[13:44] <foxx2> hmm, same thing.. (ls output + patch error) - http://pastebin.com/mBfdXf2G
[13:44] <foxx2> i did a fresh extract from the orig tar into a new dir
[13:45] <foxx2> cp -Ra the debian dir, etc
[13:45] <tumbleweed> err
[13:45] <tumbleweed> your source package cotains a tarball?
[13:45] <foxx2> oh wait
[13:45] <foxx2> now we have something
[13:45] <foxx2> http://pastebin.com/MDfmqDRD
[13:45] <foxx2> now when i do push -a manually, it fails
[13:45] <foxx2> (i did pop before hand too)
[13:46] <tumbleweed> it looks like you are doing things in the wrong directories
[13:46] <tumbleweed> atlassian-bamboo-4.4.4.tar.gz should be called atlassian-bamboo_4.4.4.orig.tar.gz
[13:46] <tumbleweed> debian should be inside atlassian-bamboo-4.4.4
[13:46] <foxx2> ahhh, sorry yes i messed that up, let me try again, sec
[13:48] <foxx2> heh i think i know what i did wrong, 2 mins just testing now
[14:02] <foxx2> tumbleweed: it works! :) so here was the problem.. because the dir layout of the atlassian bamboo tar is a bit messy, i was making some changes to the folder structure AFTER creating the .orig.tar.gz file (so orig contained the old layout, but the extracted dir contained the new layout), which in my case, was renaming a root dir and moving all the contents inside to a dir called 'src/'..
[14:02] <foxx2> when running the patches on this dir it worked fine, but of course when pbuilder kicked in, it was using .pc, which threw up massive differences which it couldnt figure out (and rightly so)... the fix was to extract the tar, make the changes, create a new tar with this dir struct and rename to the appropriate .orig.tar.gz file, apply the usual patch structure, then it worked fine
[14:03] <foxx2> your original guess of "are you sure you havent changed anything" was correct :)
[14:03] <tumbleweed> I try and avoid repacking orig tarballs, unless I need to remove undistributable bits
[14:04] <foxx2> what if the original tarball changes its foldername on every release? i.e. inside the tar is SOFTWARE-VERSION.VERSION.VERSION
[14:04] <tumbleweed> if you do need to, I suggest automating it for next time (e.g. with a get-packaged-orig-source rule in debian/rules)
[14:04] <tumbleweed> it doesn't matter what the top level directory name in the tarball is
[14:04] <foxx2> oh holy shit, i didnt know about get-packaged-orig-source
[14:04] <tumbleweed> (as long as there is only one top level directory)
[14:05] <tumbleweed> foxx2: there isn't, but it's the (semi-)standard name for a rule that does this
[14:05] <foxx2> ah
[14:05] <foxx2> go fundementally i need to change my approach on automating this.. got it
[14:05] <tumbleweed> either automate, or don't repack
[14:05] <tumbleweed> (otherwise nobody else knows what's going on)
[14:06] <foxx2> well, at the moment im using a manual script that runs and automates all these steps, (including downloading the source, repacking, and executing the pbuilder stuff)
[14:06] <foxx2> should i really be shifting all that inside the actual debian rules?
[14:06] <tumbleweed> as it's a 3rd party thing maybe not. but for anything in the archive, I'd strongly suggest doing so - it's what people expect
[14:07] <foxx2> got it, yeah that makes sense because renaming a dir or moving a dir is just the same as making a change
[14:07] <tumbleweed> we all have our own workflows for doing most of the things you mentioned
[14:08] <foxx2> and moving the dir struct without tracking it in the package, is just the same as making a change to the source instead of using a quilt patch, right?
[14:08] <foxx2> (i.e. if someone wanted to modify the package without this bootstrap script, its break)
[14:08] <tumbleweed> exactly
[14:09] <foxx2> makes sense - ty for the advice :)
[14:25] <foxx2> just found a good example of that method i think; http://anonscm.debian.org/viewvc/python-modules/packages/python-gd/trunk/debian/rules?revision=20305&view=markup
[14:26] <foxx2> seems clean
[14:26] <tumbleweed> yip, that's what I mean
[14:27] <foxx2> something that does confuse me slightly.. where is get-packaged-orig-source invoked?? i couldnt find any other mentioning of that name in any of the other files
[14:27] <tumbleweed> it'd be run by hand
[14:28] <foxx2> ahh
[14:28] <foxx2> make debian/rules get-packaged-orig-source ?
[14:28] <tumbleweed> (bzr-builddeb knows how to run it, too, if you keep your package in bzr)
[14:28] <tumbleweed> yes
[14:28] <foxx2> got it, so could just throw a Makefile into the root dir above debian/, and have make builddeb, that would execute the get-packaged-orig-source, and the pdebuild.. sound clean?
[14:31] <tumbleweed> no
[14:31] <tumbleweed> dh will see that makefile and try to use it
[14:33] <foxx2> even if its one dir above the debian dir? i.e.
[14:33] <foxx2> - /
[14:33] <foxx2> - /Makefile
[14:33] <foxx2> - /debian/rules
[14:33] <foxx2> oh wait, of course
[14:33] <tumbleweed> that's where makefiles usually live :P
[14:33] <foxx2> haha yes, *doh*
[14:33] <tumbleweed> this sounds like it's a personal script, it's nothing to do with teh package
[14:34] <foxx2> yeah, just a convinience script.. which should be kept outside of the package, right?
[14:34] <foxx2> (or at the very least, in another dir above that one
[14:35] <tumbleweed> yeah
[14:35] <foxx2> i gotta admit, this is all starting to look a lot cleaner now.. 90 degree learning curve, but its really quite nice
[14:36] <foxx2> a lot of those "wtf is this for" moments are now "ahh yes, now i see"
[14:36] <tumbleweed> good ogood
[14:37] <tumbleweed> make that, good good
[14:41] <foxx2> sorry, design question.. if the download stage relies on some messy shell script and python script.. is it acceptable to place those scripts into a subdir of the debian/ dir, and then call them from the debian/rules file?
[14:42] <foxx2> (in this case, a python script fetches the most recent release URL, then a shell script does a curl download and repacking)
[14:44] <tumbleweed> sure
[14:44] <foxx2> ty
[14:44] <tumbleweed> if uscan can't do it
[14:44] <foxx2> uscan.. *googles*
[14:45] <foxx2> oh nice.. tho im not sure it would be compatible.. atlassian expose a malformed JSON file, which has to be mangled and parsed to find the appropriate release URL
[14:46] <foxx2> 	d = f.read()
[14:46] <foxx2> 	d = json.loads(d[10:][:-1])
[14:46] <foxx2> 	d = filter(lambda x: x['platform'] == 'Unix' and x['type'] == 'Binary', d)
[14:46] <foxx2> v annoying
[14:46] <tumbleweed> right
[14:58] <foxx2> hmm i just thought, developers would most likely want the ability to specify the package they are about to compile... so it would make more sense to make this a configurable..
[14:58] <foxx2> the most sane approach for that would be to include a ./configure script right?
[14:59] <foxx2> i.e. ./configure; askes them for the version they wish to compile against, the configure script then stores this version number for the Makefile to use during make
[14:59] <tumbleweed> foxx2: the get-packaged-orig-source you pointed at figured out the version you want from looking at debian/changelog
[14:59] <foxx2> (slightly off-topic from packaging)
[14:59] <foxx2> ahhhhh
[14:59] <foxx2> okay yes, now i see, so they just modify the changelog version number and it takes care of itself
[15:00] <foxx2> perfect, ty
[15:55] <foxx2> hmm, is it normal for "quilt push -a" to have a return code of "2" even if it was successful?
[15:56] <Laney> see "EXIT STATUS" in quilt's man page
[15:57] <foxx2> hmm, i dont seem to have EXIT STATUS in my man page :X lemme google sec
[15:57] <foxx2> checked 3 different sources for man quilt, nothing mentioning exit codes or exit status
[15:58] <foxx2> lol - https://lists.gnu.org/archive/html/quilt-dev/2013-01/txtJTixiCUfQ7.txt
[15:58] <foxx2> that'd be why
[15:58] <foxx2> only added in january :X
[15:59] <foxx2> there we go, that explains what exit code 2 is.. ty :)
[16:00] <Laney> wha
[16:01] <foxx2> gotta love reading documentation from patch files on dev trunk.. lol
[16:01] <Laney> xnox: how come when I go to http://manpages.ubuntu.com/manpages/raring/en/man1/quilt.1.html I get redirected to .../precise/... (that's what happens if the release isn't found, for example 's/precise/laneyrules/')
[16:01] <Laney> did oneiric and raring not get generated correctly?
[16:04] <xnox> Laney: no idea. I only did a monkey patch, I may have gotten it wrong. And all I did was ask IS to deploy this and hope it works. I am not aware if there are funky deployments instructions to go with suite updates.
[16:04] <Laney> BLAST!
[16:04] <Laney> kirkland: ↑ this is yours IIRC - can you help us?
[16:04]  * xnox wonders if they are generated only once on deploy, as they previously were always generated post-release.
[16:05] <foxx2> lol did i just open a can of worms? sorry :X
[16:05] <xnox> and hence are not cronned to be kept up to date?
[16:05] <ogra_> oh, fun so we'd have 2 years outdated manpages :)
[17:33] <jtaylor> oO new mails in-devel 205 since yesterday? not even the worst threads on dd managed that :O
[17:34] <ogra_> heh
[17:34] <tumbleweed> no, I think mail from lists.ubuntu -> gmail jammed up a bit
[17:34] <ogra_> you should try ubuntu-users
[17:34] <tumbleweed> all the gmail users seem to have been complaininng, but there was actually very little discussion today
[17:34] <ogra_> at good times 300/day are normal there
[17:39] <jtaylor> I finally got the mail that started all
[17:39] <jtaylor> I wonder why it was delayed so much
[17:39] <ogra_> you are not the only one it seems
[17:39] <ogra_> someone complained last night too
[17:39] <tumbleweed> presumably because the ubuntu lists have been fairly idle in recent months
[17:39]  * ogra_ had all of them on time
[17:39] <jtaylor> oh its l.u -> gmail, not other way round
[17:39] <tumbleweed> gmail rate-limits source IP addresses
[17:40] <tumbleweed> yeah, you guys were missing out on the fun
[17:40] <kirkland> Laney: howdy ... looking
[17:41] <jtaylor> and thunderbird marks the mail as scam :)
[17:41] <jbicha> it's all part of the big Canonical conspiracy to pretend to have important conversation in the open ;)
[17:41] <tumbleweed> naah, it's all your fault for using proprietary e-mail services :P
[17:42] <jtaylor> is there a good free one?
[17:42] <tumbleweed> good question, probably not
[17:42]  * tumbleweed runs his own
[17:57] <jtaylor> why did I add adt tests to all my stuff, now I actually have fix all the breakage ._.
[17:58] <tumbleweed> :P
[17:58] <tumbleweed> out of interest, how do you know they broke?
[17:58] <jtaylor> from the jenkins instance
[17:59]  * tumbleweed finds running adt-run ultra-painful, and I don't go looking at that jenkins often
[17:59] <jtaylor> I have a more lightweight script
[17:59] <jtaylor> quite easy to use
[17:59] <jtaylor> using chroots
[17:59] <tumbleweed> share?
[18:00] <jtaylor> its super ugly :)
[18:00] <tumbleweed> in that case, make it beautiful first :)
[18:00] <tumbleweed> maybe I should write myself one...
[18:00] <jtaylor> http://paste.ubuntu.com/5585766/
[18:01] <jtaylor> sadtrunner.py <dsc-file> <changes-file>
[18:01] <jtaylor> multiple test handling is not perfect it just installs all deps
[18:01] <jtaylor> also no restriction handling
[18:01] <tumbleweed> that's not *super ugly, it seems sane
[18:01] <jtaylor> look at the handling of stderr :)
[18:01] <tumbleweed> yeah, I'd be quite keen to run each set of tests in its own chroot
[18:01] <tumbleweed> *each test
[18:02] <jtaylor> I wanted to just remove the dependencies and run again, but didn't get it right on first try and haven't tried again
[18:02] <jtaylor> there are probably still some remnants of the try in there
[18:13] <jtaylor> why does python-imaging in experimental behave different than raring?
[18:13] <jtaylor> Image.open("/usr/share/pyshared/scipy/ndimage/tests/dots.png") gives mode P, in debian it gives RGB
[18:14] <jtaylor> no relevant diff it appears, strange
[18:16] <jtaylor> possibly because the image is compressed different in ubuntu?
[18:18] <jtaylor> indeed
[18:18] <jtaylor> nice
[18:28] <tumbleweed> oh, on the samples?
[18:28] <tumbleweed> that'd make sense
[18:40] <jtaylor> anther issue found only by autopkgtest :)
[18:44] <foxx2> having a bit of trouble with pbuilder if anyone has a moment.. google fails me again.. seems to be an issue getting dependancies to work inside pbuilder.. see http://pastebin.com/seCdFU11 (at the bottom is the debian/control file, at the top is the pbuilder output)
[18:45] <tumbleweed> foxx2: why do you want ia32-libs?
[18:46] <tumbleweed> foxx2: if this thing is 32-bit only, just build it on i386 and be done. The i386 package can be installed on an amd64 machine thanks to multiarch
[18:47] <foxx2> ohhhh
[18:47] <foxx2> DIST=squeze ARCH=i386 pbuilder create - is that right?
[18:47] <tumbleweed> it looks like your pbuilder chroot didn't have i386 available as a foreign architecture (which is quite sane)
[18:48] <tumbleweed> yeah, for the common pbuilderrc
[18:48] <tumbleweed> except that squeeze doesn't support multiarch
[18:48] <foxx2> oh
[18:48] <tumbleweed> your pastebin was a of a sid chroot
[18:49] <jtaylor> I recommend use DIST=stable  using names may cause cachers to collect data forever
[18:49] <foxx2> if i use ARCH=i386 DIST=stable to compile the package, i can still install the package on a squeeze distro right
[18:50] <tumbleweed> no, squeeze predates the multiarch work
[18:50] <tumbleweed> what I mean is, you can't istall i386 packages on amd64 squeeze installs
[18:51] <foxx2> got it.. so id have to somehow make my amb64 pbuilder environment work with the ia32-libs dependancy?
[18:51] <tumbleweed> yeah
[18:51] <tumbleweed> which it probably will for squeeze, but won't for sid
[18:52] <foxx2> im assuming that means ive gotta manually fudge the /etc/apt/sources.list in the chroot??
[18:53] <tumbleweed> no
[18:53] <tumbleweed> I suspect your package will build as-is on squeeze amd64
[18:54] <foxx2> oh so i should remove ia32-libs from the deps? the app fails to run without it installed though
[18:54] <tumbleweed> I'm saying the opposite
[18:55] <tumbleweed> on squeeze, I think it's fine as-is
[18:55] <tumbleweed> on sid, build on i386, not amd64, and avoid the whole ia32libs thing
[18:55] <foxx2> ohhh, wait sorry i just re-read the convo again (brain is dying) - i understand now.. ill give that a try, ty :)
[18:56] <foxx2> im not sure how ive ended up with a sid chroot.. i must have made a typo somewhere
[19:21] <jtaylor> hm I still get these strange bus errors in raring chroots
[19:21] <jtaylor> am I still the only one?
[19:21] <jtaylor> (cowbuilder)
[19:23] <lfaraone> Hmm, I seem to be getting a bunch of ubuntu-devel mails from 3 days ago in my inbox :/
[19:23] <lfaraone> Is that happening to anybody else?
[19:23] <jtaylor> lfaraone: not only you
[19:23] <jtaylor> all gmail users
[19:28] <jtaylor> pbuilder broken too
[19:35] <ScottK> pbuilder is broken on gmail?
[19:35]  * ScottK is confused
[19:36] <jtaylor> that was related to a earlier line :)
[19:36] <jtaylor> my raring pbuilder/cowbuilder chroots on raring and quantal for some reason don't --build anymore
[19:36] <jtaylor> since about a week
[19:37] <jtaylor> other dists work
[20:19] <foxx2> tumbleweed: yeah fixing the distro so it was squeeze instead of sid seems to have fixed the problem. ty :)
[20:27] <ScottK> jtaylor: It was funnier my way.
[21:13] <jtaylor> is there a recap of what I have to do to be able to participate at the uds?
[21:14] <jtaylor> irc + a audo webcast is probably not happening this time?
[21:16] <tumbleweed> irc + youtube
[21:17] <jtaylor> regular anonymous youtube is enough?
[21:17]  * jtaylor does nto even know what this hangout is which keeps getting mentioned
[21:17] <tumbleweed> should be
[21:17] <jtaylor> good
[21:17] <tumbleweed> only a few people can participate in the hangouts
[22:13] <ScottK> 10
[22:34] <ScottK> lfaraone: Since you're interested in AFS, you might want to read  DSA-2638-1 and then prepare patches for an Ubuntu security upload.
[22:39] <lfaraone> ScottK: Sure.