[01:39] <LaserJock> any code hosting people around?
[01:39] <mwhudson> yes
[01:40] <LaserJock> mwhudson: do you happen to know if a team changes name if that breaks associated bzr branches?
[01:41] <mwhudson> it breaks the urls, yes 
[01:41] <LaserJock> but in Launchpad the urls get updated?
[01:41] <mwhudson> the branches themselves are fine of course, but i'm guessing that's not what you really mean
[01:41] <mwhudson> LaserJock: yes
[01:41] <LaserJock> no, I mean in Launchpad itself
[01:41] <LaserJock> I'm not so concerned about people who have existing branches
[01:42] <mwhudson> everything in launchpad is resilient to name changes, pretty much
[01:42] <mwhudson> (it's almost like there's a database with lots of foreign key references behind everything...)
[01:43] <LaserJock> who'da thunk it?!
[01:43] <mwhudson> i think maybe ppa's break if you change team/person name, i can't remember the details
[01:43] <mwhudson> but branches are certainly fine
[01:43] <LaserJock> yeah, PPAs are a bit interesting
[03:36] <emgent> barry-away: thanks for reply :)
[07:27] <gnomefreak> anyone here yet? i know its early
[07:28] <Hobbsee> no
[07:29] <gnomefreak> i have a wiki that isnt able to be edited its a */community/* as far as i know its what was named wiki
[07:29] <gnomefreak> https://help.ubuntu.com/community/FirefoxFAQ
[10:06] <beuno> mpt, gooooood morning!  Are you here yet?
[10:30] <mpt> Goooooooooooooooooooooooood morning Launchpadders!
[10:30] <mpt> Good morning beuno!
[10:30] <wgrant> Hello mpt.
[10:31] <beuno> mpt, let me know when you can chat for a bit
[10:31] <mpt> beuno, any time
[10:31] <beuno> mpt, I'll hunt you down in a minute then  :)
[10:36] <qball> morning mpt 
[10:37]  * qball needs to trick people into translating his app.
[10:38] <persia> qball: Rule #72 from the handbook of sneaky people: never disclose your motives
[10:44] <qball> damn couldn't you have said that sooner
[10:44] <qball> where can  I get that book.
[10:59] <mtaylor> BjornT: Bug 74449 "Fix Released"... I don't see it on Edge - do I need to do something to register the upstream tracker? 
[10:59] <mtaylor> haha
[10:59] <mtaylor> my email is quicker than ubott
[10:59] <mtaylor> my email is quicker than ubottu
[11:05] <BjornT> mtaylor: hmm. looks like that bug isn't fixed after all. i'll look into it.
[11:05] <mtaylor> :) thanks
[11:22] <therve> jamesh: need any more info?
[11:22] <therve> jamesh: this is pretty critical for me :/
[11:23] <BjornT> mtaylor: it looks like it works if you specify the long version for the url, e.g. http://bugs.mysql.com/bug.php?id=24788
[11:23] <BjornT> mtaylor: i'll see if we can get the short version work as well.
[11:23] <mtaylor> BjornT: aroo? 
[11:24] <mtaylor> BjornT: perhaps we're talking about different areas?
[11:24] <mtaylor> I was talking about listing bugs.mysql.com as the upstream bug tracker for a project - and it doesn't seem to be in the list... 
[11:24] <mtaylor> but now I'm really interested in what _you_ are talking about :)
[11:26] <BjornT> mtaylor: oh :) i thought that you wanted to link to bugs in that bug tracker from launchpad.
[11:26] <mtaylor> well, that too
[11:27] <mtaylor> I think I'm starting to understand that there are two concepts here
[11:27] <BjornT> mtaylor: ok. so to link bugs, then you need to use the long version for the url for now. the first time you link to such a bug, the bug tracker will be registered automatically
[11:27] <mtaylor> gotcha
[11:28]  * siretart waves to mrevell
[11:28] <BjornT> mtaylor: but if you want, you can register the bug tracker at https://launchpad.net/bugs/bugtrackers/+newbugtracker
[11:28] <mrevell> Hi siretart!
[11:28] <BjornT> mtaylor: choose "PHP Project Bugtracker" as the type
[11:29] <siretart> I've just read your mail, and though I'd ping you that I'm already here for some time :)
[11:30] <mrevell> siretart: Great. Give me five minutes to get a cup of tea and I'll ping you.
[11:31] <siretart> mrevell: no hurry. I'm currently at work and have a meeting in about an hour, but will be available again later
[11:34] <mrevell> siretart: Cool, when's the best time for you to talk?
[11:35] <therve> I've changed my email-address in launchpad, and I can't connect anymore
[11:35] <therve> login fails with "This account cannot be used."
[11:35] <therve> does anyone have a clue?
[11:38] <mrevell> siretart: Sorry, machine froze, so I'm not sure if you replied.
[11:38] <siretart> not yet :) - was fetching coffee
[11:39] <mrevell> heh :)
[11:39] <siretart> I should be more available at 13:30 UTC, the meeting is scheduled to end by 13:00 UTC
[11:40] <lifeless> therve: have you validated the new email ?
[11:40] <therve> lifeless: indeed
[11:40] <therve> lifeless: I have also tried to reset the password
[11:40] <lifeless> therve: and you are logging in with the new email ?
[11:41] <therve> lifeless: both fail
[11:41] <lifeless> therve: and you are logging in with the new email ?
[11:41] <therve> lifeless: yes
[11:41] <therve> lifeless: and with old too
[11:41] <therve> lifeless: both fail
[11:41] <lifeless> it could be a cookie issue
[11:41] <lifeless> can you clear all launchpad.net cookies from your browser
[11:41] <therve> ok I try
[11:42] <spiv> There's a bug about changing email addresses breaking accounts atm, IIRC>
[11:42] <lifeless> also, what is your lp account name/new email
[11:42] <lifeless> spiv: ah, I hadn't seen that. reference?
[11:42] <spiv> Looking for it now.
[11:43] <therve> lifeless: it doesn't seem to work
[11:43] <spiv> https://bugs.launchpad.net/launchpad/+bug/244499
[11:44] <therve> looks like it
[11:44] <lifeless> therve: lets see if I can unwedge this for you
[11:44] <therve> lifeless: thomas@canonical.com ?
[11:44] <therve> lifeless: thanks a lot
[11:45] <lifeless> ok, curtis has a script according to the page
[11:47] <lifeless> therve: so, there is a script to fix it, but I know not where it is.
[11:47] <lifeless> therve: starting to look
[11:49] <therve> I guess curtis is on the other side of the planet :)
[11:50] <lifeless> stub: ping
[11:50] <stub> lifeless: pong (Dodgy ISP - having real trouble maintaining connections to the other irc server)
[11:50] <lifeless> bug 244499
[11:51] <lifeless> stub: do you know where the script is, or do I need to duplicate the investigation to fix therve's login
[11:52] <stub> No idea where 'the script' is
[11:53] <stub> It might just look for an account with valid but no preferred email addresses and set one to preferred.
[12:51] <klette> Hi! We're in the process of switching bugtrackers from sf.net, and launchpad is one of the alternatives. My question is this, are there any scripts out there that takes a xml-dump from sf.net and pushes all of the info to launchpad?
[12:54] <soren> klette: You generally just ask the launchpad guys to do it.
[12:55] <soren> klette: They've got magic "import project from sf.net" stuff they can invoke.
[12:56] <klette> soren: oh, nice :-)
[12:56] <soren> klette: It is. :)
[12:57] <persia> klette: If nobody offers to do it here soon, post a request on answers.launchpad.net/launchpad
[12:59] <klette> persia: will do. It's not decided yet though. The choice is between hosing a trac-instance on our own servers, or let someone else do all the work (launchpad! ;-))
[12:59] <soren> I think you can ask them to do a test-import.
[13:00] <soren> So that you can see how it works out and such.
[13:22] <therve> lifeless: do you have any news? is there something I can do?
[13:23] <lifeless> therve: sorry, its late here, I got distracted by life ;)
[13:23] <geser> what does "Duplicated ancestry
[13:23] <therve> lifeless: no problem :)
[13:24] <lifeless> stub: could you poke at therve's account, 22:23 is not a good time to be doing adhoc sql on prd
[13:24] <geser> what does "Duplicated ancestry" for an "Failed to upload" error mean?  should it be simply retried in a few hours as the package was moved from universe to multiverse?
[13:32] <wgrant> geser: It's a bug for which I forget the number. Just retry after the next publisher.
[13:32] <wgrant> geser: It occurs when a build is started or finished (I forget which) before the first publisher run after an override.
[13:33] <Hobbsee> geser: oh, was that what pitti demoted earlier?
[13:34] <geser> Hobbsee: yes, xmlgraphics-commons
[13:35] <Hobbsee> geser: yeah, i suspected it might, when i asked pitti
[13:35] <Hobbsee> oh well.
[13:35]  * Hobbsee tries throwing it back at the buildds.
[13:35] <Hobbsee> hm, it's built now...
[13:38] <geser> Hobbsee: that's interesting as that's the same build I got the "Failed to upload" mail for
[13:39] <Hobbsee> cprov: ?
[13:39] <geser> is it possible to recover "failed to upload" builds from the rejected queue?
[13:40] <glatzor> mpt, how can I link a ppa to a project? I donÄt find the option in the menus
[13:40] <wgrant> geser: I've only seen it done once.
[13:40] <wgrant> And that was for OOo, IIRC.
[13:41] <wgrant> glatzor: I don't believe you can.
[13:41] <mpt> glatzor, I don't think you can. Can you give an example of the PPA and project you want to link?
[13:41] <glatzor> https://edge.launchpad.net/ubuntu-translator-tools/
[13:41] <glatzor> https://edge.launchpad.net/~ubuntu-translator-tools-hackers/+archive
[13:43] <mpt> glatzor, you could include the URL of the PPA in the project description
[13:46] <glatzor> for sure.
[13:47] <mpt> glatzor, and conversely, you could include the URL of the project in the PPA description
[13:48] <sinzui> therve: ping
[13:50] <therve> sinzui: yes
[13:50] <mpt> glatzor, reported bug 245183
[13:51] <Hobbsee> projects don't *have* ppas.
[13:51] <sinzui> therve: I was told you needed my assistance. Did you change your launchpad contact address and get locked out?
[13:51] <mpt> Hobbsee, ubuntu-translator-tools is a counterexample to that assertion.
[13:52] <therve> sinzui: thanks for the assistance, but stub had managed to make it work
[13:52] <sinzui> therve: fab. stub rocks.
[13:52] <therve> sinzui: I think he's creating another bug for the problem
[13:53] <sinzui> ok, I'll look for that, I have a code fix, but it has not been released yet.
[13:53] <Hobbsee> mpt: that has it's team of developers having a ppa, where the team of developers happens to be the same as the project itself, no?
[13:53] <glatzor> thanks mpt 
[13:53] <therve> sinzui: ok great
[13:53] <Hobbsee> mpt: (which afaik, is As Good As It Gets (tm) )
[13:54] <therve> sinzui: this is a frustrating problem :)
[13:54] <glatzor> Hobbsee, you always need a team for a project to handle the access to the main bzr branch
[13:54] <mpt> Hobbsee, the PPA is pretty obviously dedicated to that particular project. It *could* be for multiple projects, but it isn't.
[13:54] <stub> sinzui: therve's issue doesn't match the comments in the other bug I saw, so I opened a new bug: https://bugs.edge.launchpad.net/launchpad/+bug/245185
[13:54] <sinzui> stub: it is the same as 244499
[13:55] <Hobbsee> glatzor: i guess that's a point.  i wasn't aware that team creation and project creation happened simultaneously, automatically, though.
[13:55] <sinzui> stub: I have code ready for review that fixes the problem.
[13:56] <glatzor> Hobbsee, It doesn't
[13:56] <stub> sinzui: The data bug I saw does not match your comments in bug ﻿244499
[13:56] <glatzor> Hobbsee, but would perhaps also a good idea
[13:57] <mpt> Projects vs. teams is still a little awkward in Launchpad, I think
[13:57] <Hobbsee> glatzor: i was thinking that - but only if the project chose to use code and or ppa.
[13:57] <stub> sinzui: Or did the invalid NEW status cause the emailaddress to not be linked to the account?
[13:57] <mpt> e.g. I reported a bug yesterday about the teams who expect to be able to file bugs on the team rather than on a particular project
[13:57] <sinzui> True, I was negligent in updating the bug with what I found yesterday afternoon. Salgado's fix allowed me to see the deeper bug that affected the two users.
[13:59] <sinzui> stub: the way in which the email was created mean it did not an account. that was a workflow issue in the code.
[13:59] <stub> ok. ta.
[14:13] <pep> Hey!
[14:13] <pep> I have a situation here... :s
[14:13] <pep> We accidentely handed over a team ownership to a random person on launchpad...
[14:17] <intellectronica> pep: whoops. can you please file a question. i'll try to make sure that someone attends to it shortly
[14:18] <pep> Very well.
[14:21] <Laibsch> Hi, I wonder about the semantics of the "propose for merging" flag
[14:21] <Laibsch> who is supposed to act on that (and how)?
[14:22] <Laibsch> I am asking in particular about the branches scheduled to be merged into https://code.launchpad.net/~subdownloader-developers/subdownloader/trunk
[14:22] <pep> I am actually chatting with JendaVancura right now on Jabber (he can't connect to IRC) and the problem is: what used to be the diy-team is now relatively dead, its projects are abandoned. Now, a new team has set itself up and just took over the projects. So the new team in charge is now this one: https://launchpad.net/~spreadubuntu and this old one:https://launchpad.net/~ubuntu-diy-team was accidentally handed over to this person that happened to have diy
[14:22] <pep> as its nick: https://launchpad.net/~diy :/ But I'm filing a question.
[14:28] <pep> intellectronica: mhh, sorry but where do I ask the question at? I can't ask it concenring a team.... :/
[14:29] <intellectronica> pep: see the topic :)
[14:29] <pep> right, sorry about that :s :)
[14:29] <mpt> Laibsch, the owner of the destination branch should accept it or decline it
[14:31] <Laibsch> I am part of the team that owns the branch
[14:31] <mpt> Laibsch, or anyone who has permission to change the destination branch (in this case, any member of Subdownloader Developers)
[14:31] <Laibsch> So, how am I supposed to act?
[14:31] <Laibsch> I was the one making the request
[14:32] <Laibsch> Should I chekc out both branches, push from the obsolete to the new branch and after that delete the obsolete branch?
[14:32] <mpt> Laibsch, if you already have permission to do the merge, you don't need to propose it, unless you were asking for code review or something like that
[14:32] <Laibsch> I was unsure how this is supposed to work
[14:32] <mpt> Laibsch, so merge the source into the destination using bzr, then mark the merge as done
[14:32] <mpt> (I'm not sure how you do that, because the page doesn't look the same for me since I don't have the same permissions)
[14:33] <mpt> abentley can probably tell you in more detail
[14:41] <pep> Thanks for your help intellectronica, I filed question 38094.
[15:02] <pep> who can delete a project? its driver?
[15:02] <andrea-bs> pep: only a Launchpad administrator
[15:02] <pep> I see.
[15:03] <pep> thank you...
[16:06] <pygi> hey hey folks
[16:06] <pygi> to further enhance the bugging I've been doing lately, here's a new semi-started specification for Rosetta :)
[16:07] <pygi> any feedback or comments more then welcome
[16:07] <pygi> https://blueprints.edge.launchpad.net/rosetta/+spec/translation-workflow-and-notification-system
[16:42] <thekorn> hi, I've got a loggerhead related question: is there some url magic to always show the latest version of a file
[16:48] <bdmurray> thekorn: I know the answer to that
[16:49] <bdmurray> somewhere ...
[16:49] <thekorn> bdmurray, cool :) mind to share your knowledge
[16:50] <bdmurray> I'm trying to find where I hid it. ;)
[16:50] <thekorn> take your time
[16:51] <bdmurray> I think its bug 185353
[16:52] <seb128> hello there
[16:53] <seb128> I was wondering which people are listing under the "also notified" category
[16:53] <seb128> there is a zillion of those for any ubuntu bug
[16:53] <bdmurray> seb128: those are all people who've subscribed to all ubuntu bug reports
[16:54] <bdmurray> quite a few of them are actually deactivated accounts too
[16:54] <persia> I suspect there's some causality involved between clicking the "receive all ubuntu bug reports" button and deactivating the account.
[16:54] <thekorn> this reminds me: I always wanted to write a greasemonkey script to make this subscribers list toggleable
[16:55] <bdmurray> persia: I'd imagine!
[16:55] <seb128> thekorn: you can toggle it on launchpad no?
[16:56] <thekorn> seb128, yes but i want to auto hide them
[16:56] <seb128> thekorn: the change is persistant on launchpad no?
[16:57] <seb128> ie, if you toggle it, it's toggled for all pages you browse
[16:57] <thekorn> and to be able to toggle per section ('also notified', 'per duplicate',..)
[16:57] <seb128> ah ok
[16:57] <seb128> well, that was sort of my complain
[16:57] <seb128> what is the point to have a zillion of "also notified" people listed on every ubuntu bug
[16:57] <thekorn> I#m mostly intrested in direct subscribers,
[16:57] <seb128> mpt: ^ do you know if there is a bug or some discussions about that?
[16:58] <mpt> seb128, yes there is
[16:58] <thekorn> I dont care about 'also notified', so I would like to hide this category
[16:58] <seb128> thekorn: I expect that's the case for most users
[16:58] <seb128> that's also what leads to the "you have to scroll to go to the subscribing option since they are after this list"
[16:59] <seb128> and the list is over a screen for any ubuntu bug
[16:59] <seb128> mpt: ok good, thanks ;-)
[17:00] <mpt> seb128, bug 241150
[17:01] <mpt> but I think once we (a) replace the source package info box with a tooltip, and (b) move the "Subscribe yourself" etc from the bottom of the Subscribers list to the top, you won't care nearly so much
[17:01] <seb128> mpt: thank you
[17:02] <seb128> well, I'm wondering who cares about the "also notified" list
[17:02] <seb128> usually people care about direct subscribers and bug contacts for the component
[17:02] <mpt> I think few people explicitly care about it. But it may act as a subtle disincentive to adding useless comments to a bug report.
[17:03] <thekorn> bdmurray, re my loggerhead question, I always thought this has still been implemented, but the links shown there do not work
[17:03] <bdmurray> I care about it explicitly fwiw
[17:04] <seb128> why?
[17:04] <seb128> what information do you get from knowing that this list of people is subscribed to any ubuntu bug?
[17:04] <bdmurray> s/care about/am interested in/
[17:04] <bdmurray> thekorn: the linkified one works for me now
[17:07] <thekorn> bdmurray, ok, it works for me too now, but sometimes get a server error,
[17:07] <thekorn> but I was looking for a link to the most recent version of a file
[17:07] <seb128> who could I bribe to get bug #229040 on the 2.0 list? ;-)
[17:11] <bdmurray> thekorn: I think it is possible to increment the revision number such that is much higher than the actual revision and get the latest version of the file
[17:12] <mpt> seb128, bigjools or cprov for a start
[17:12] <bigjools> very unlikely to happen :(
[17:12] <seb128> not sure if the bug is hard to fix, but I would suggest to default to text rather than html meanwhile, most of attachements are patches and debdiff and so are texts
[17:13] <seb128> or could you special case on the filename? *diff = text?
[17:14] <pep> Is there a way to see how many people of my team have subscribed to the list?
[17:14] <cprov> seb128: can't you make firefox deal correctly with gzip-patch MIME ?
[17:15] <seb128> cprov: that's not gziped, those are just diffs
[17:15] <seb128> and I don't want to start gziping diffs no ;-)
[17:15] <seb128> cprov: right know launchpad sets debdiff as htmls
[17:16] <cprov> seb128: wow, that's not soyuz bug them
[17:16] <cprov> seb128: I've misread you bug report, that's in malone.
[17:17] <cprov> seb128: there is a similar problem with the debdiff generated by launchpad/soyuz, those are gzip-patch and firefox doesn't like to render them by default.
[17:17] <seb128> cprov: it suggests opening those rather?
[17:18] <cprov> seb128: yes, I open them with the file-roller, but that's annoyingly slow.
[17:19] <cprov> well, not a blocker, life goes on ...
[17:19] <seb128> I noticed that too when opening diff.gz
[17:19] <seb128> sometimes there are displayed in the browser and sometime not
[17:19] <seb128> I should ping asac (the firefox maintainer) about that ;-)
[17:20] <cprov> seb128: yes, when it becomes a 'fix this, pretty please, or someone will die' issue ;) 
[17:21] <seb128> lot of bugs are not that bad but annoying
[17:21] <cprov> today we have to feed the soyuz monster properly so it stops eating uploads from dedicated people ...
[17:22] <seb128> the debdiff detected as html means you have to add the diff, wait for the page to reload, go to the page to edit the patch, change the type, and do that for every attachement on every bug you work on
[17:23] <seb128> soyuz eating uploads? bad soyuz, no cookie today ;-)
[17:24] <cprov> seb128: talk to intellectronica or allenap, see what they can do for you.
[17:24] <seb128> cprov: oh btw speaking about soyuz, should I do something special when binaries fail to be uploaded for some reasons?
[17:24] <cprov> seb128: no, not today ;)
[17:24] <cprov> seb128: depends how they failed 
[17:24] <seb128> ok, because I got a mail about the amd64 hardy pidgin build which failed to be uploaded today
[17:25] <seb128> "DETAIL:  Process 14933 waits for ShareLock on transaction 145257993; blocked by process 14480.
[17:25] <seb128> Process 14480 waits for ExclusiveLock on tuple (478,2) of relation 16634 of database 16409; blocked by process 14933.
[17:25] <seb128> )"
[17:25] <seb128> cprov: ^
[17:25] <cprov> seb128: does it weirdly mention ' ShareLock blah bla' ?
[17:25] <cprov> seb128: afff
[17:25]  * Yhouse e' away (Sto andando via)
[17:26] <cprov> seb128: I've already reprocessed all failed binaries from today, check LP they should be published already.
[17:27] <seb128> cprov: yes, some people mentioned that they tried the update so I figured that somebody fixed it, I was just wondering if I should ping somebody in such cases or if you guys are automatically notified
[17:27] <seb128> cprov: thanks for fixing ;-)
[17:27] <cprov> seb128: ping me (as usual) I will help you.
[17:27] <seb128> alright
[17:28] <seb128> ok, I think that's enough launchpad bugs chatting for today, I'll go back to work for a bit and call it a day ;-)
[17:28] <cprov> seb128: and yes, my inbox gets stuffed with failure-notifications too.
[17:28] <cprov> seb128: good, seya, then.
[17:28]  * seb128 hugs cprov for the good job he's doing on soyuz
[17:29]  * cprov hugs seb128 too
[17:40] <allenap> seb128: bug 229040 should be quite easy to fix; I'll talk to BjornT about it.
[17:42] <seb128> allenap: thank you
[18:08] <pep> Hi, is there an easy way to send an email or message to all members of a launchpad team if the team does not have a mailing list? (being the owner of the team...)
[18:40] <ScottK> Is 30 minutes long enough to wait to assume that if LP doesn't know about my upload, soyuz has eaten it somehow?
[18:43] <cprov> ScottK: kde-guidance_0.8.0svn20080103-0ubuntu19_source.changes ?
[18:43] <ScottK> Yes
[18:43] <cprov> ScottK: eaten, please, upload again.
[18:43] <ScottK> Thanks.
[18:44] <ScottK> cprov: Done.
[18:46] <ScottK> cprov: That one made it.  Thanks again.  What happened?
[18:51] <cprov> ScottK: we having several scripts trying to update the same information at the same time, so they conflict very often and die.
[18:51] <ScottK> Ah.  Thanks.
[18:51] <cprov> ScottK: it will be fixed in 2 hours, don't lose your faith in soyuz ;)
[18:52] <ScottK> OK.  I won't.  It's generally pretty reliable.
[18:53] <ScottK> It appears no ia64 buildd's are currently running for Intrepid.  Can you look into that here or should I go to #canonical-sysadmin?
[18:54] <ScottK> Nevermind.
[18:54] <ScottK> Looks like it just took longer to wake up.
[18:57] <Rinchen> >>> LP Team Meeting in #launchpad-meeting in 2 minutes.
[20:48] <popey> any news on https://lists.ubuntu.com/archives/launchpad-users/2008-July/003896.html ?
[20:49] <popey> we have a user trying to check in changes and they are getting the "This account cannot be used" error message
[20:50] <salgado> popey, will be fixed in a couple hours
[20:50] <matsubara> popey, the fix is in the pqm queue
[20:51] <popey> thanks
[22:09] <CWii> Oh!
[22:09] <CWii> When 1800UTC
[22:09] <CWii> When is* :P
[22:35] <geser> CWii: it was over 3 hours ago, see the output of "date -u": Thu Jul  3 21:35:23 UTC 2008
[22:35] <CWii> Yeah.
[22:35] <CWii> I figured that out awhile ago :P
[23:47]  * Yhouse e' away (Sto andando via)