=== gryc_ is now known as gryc
=== bigon is now known as bigon`
=== gryc__ is now known as gryc
=== gryc_ is now known as gryc
=== bigon` is now known as bigon
=== stu1 is now known as stub
[08:02] <carlos> morning
[08:52] <indu> hi all
[08:53] <indu> I need help in loggerhead configurations
[08:53] <kiko> hello indu
[08:53] <kiko> loggerhead configurations?
[08:53] <indu> can I get any help here regarding this
[08:53] <indu> logggerhead, a bazaar web front end
[08:53] <kiko> right
[08:53] <kiko> indu, you might have more luck at #bzr 
[08:53] <kiko> though mwhudson might know something about it too
[08:54] <indu> but #bzr no, one is responding to my queries
[08:54] <kiko> indu, maybe try later, it's kinda early still
[08:54] <indu> even there I am asking mwhudson, but i think today he is not avalilable, as he was helping me the other day
[08:54] <indu> kiko, any idea from ur side?
[08:55] <kiko> I don't know anything about loggerhead
[08:55] <kiko> indu, is there a mailing list about it?
[08:55] <indu> i dont find any
[08:58] <kiko> indu, well, I know that mwhudson is off on leave until feb 4th
[08:58] <indu> kiko, oh no, i need this configs, very soon
[08:58] <kiko> indu, you might want to contact robey, the former maintainer: https://edge.launchpad.net/~robey
[08:58] <indu> kiko, can you suggest me someone else who knows about this
[08:58] <kiko> that's the only person I know
[08:59] <kiko> it's probably something you can figure out yourself, in particular if you look at the source
[08:59] <kiko> anyway, that's the best I can advise.
[08:59] <indu> ok kiko thankyou
[08:59] <mpt> Gooooooooooooooooooooooooooood morning Launchpadders!
[09:17] <indu> kiko, i have  posted my query here, https://answers.edge.launchpad.net/loggerhead/+question/21630
[09:19] <kiko> indu, okay, cool.
[09:33] <mpt> hey kiko
[09:33] <mpt> Would you be able to change the owner of Geda <https://launchpad.net/geda> as requested by Peter Clifton in launchpad-users@?
[09:34] <mpt> ("Changing ownership of gEDA project", 2007-12-30)
[09:35] <ubotu> New bug: #180972 in malone "Launchpad doesn't recognise Trac's 'accepted' status" [Undecided,Triaged] https://launchpad.net/bugs/180972
[09:35] <kiko> yes will do so now
[09:35] <mpt> thanks
[09:36] <Fujitsu> mpt: Hah, I was just about to ask the same thing, after talking to Peter yesterday.
[09:38] <mtaylor> kiko: any good ideas on how to build something with sun java on ppa? 
[09:38] <Fujitsu> Ewww.
[09:39] <Fujitsu> I'm not sure if infinity worked his magic there as well.
[09:39] <geser> Fujitsu: did you got an answer for the missing Contents file for hardy?
[09:39] <kiko> mtaylor, well, is sun java in Ubuntu?
[09:40] <Fujitsu> geser: I did not.
[09:40] <mtaylor> kiko: it is - but it requires a click-through license
[09:40] <mtaylor> kiko: which doesn't work in non-interactive :(
[09:40] <Fujitsu> mtaylor: Try build-depending on it. If it doesn't work, someone should poke infinity.
[09:40] <elmo> Fujitsu: hr did, it's the same chroots
[09:40] <Fujitsu> elmo: Ah, thanks.
[09:40] <kiko> mtaylor, so if you build-depend it fails?
[09:40] <Fujitsu> s/hr/he/, I presume? Or has HR got more technical? :P
[09:40] <mtaylor> kiko: yes. the sun-java-jdk aborts
[09:41] <mtaylor> s/aborts/install aborts/
[09:41] <kiko> mtaylor, hmmm, interesting problem. how does anything build against it, though?
[09:41] <mtaylor> kiko: I'm not sure anything does
[09:41] <Fujitsu> mtaylor: Is there any reason you can't build against icedtea?
[09:42] <mtaylor> kiko: but you know - source packages aren't always source packages to java people -- they're weird
[09:42] <mtaylor> Fujitsu: hrm. you know, I haven't tried icedtea yet
[09:42]  * mtaylor goes to try that right now
[09:43] <Fujitsu> icedtea is generally better, and it works in most cases that Sun Java does.
[09:43] <elmo> mtaylor: where's a build log of when it fails?
[09:43] <elmo> (but yes, icedtea would be better, if it works)
[09:43] <mtaylor> http://launchpadlibrarian.net/11162870/buildlog_ubuntu-gutsy-i386.ndb-connectors_0.5.6.3.7.1-1_FAILEDTOBUILD.txt.gz
[09:44] <Fujitsu> Hmmm...
[09:44] <elmo> mtaylor: thanks, I'll ask infinity to look into why it failed, it shouldn't have
[09:44] <mtaylor> elmo: cool. 
[09:44] <mtaylor> in the meantime, I'll give icedtea a shot
[09:45] <mtaylor> actually, that makes me thirsty
[09:45]  * Fujitsu sees that key being set in the .bash_history of the Hardy i386 chroot, at least.
[09:45] <Fujitsu> elmo: Maybe he only did it for Hardy?
[09:47] <elmo> Fujitsu: ah, yeah, looks like it was only hardy.  since we have an example of others needing done, I guess we can do them now
[09:47] <Fujitsu> Yep.
[09:47] <elmo> what do PPAs support again?
[09:48] <Fujitsu> i386/amd64/lpia.
[09:48] <elmo> sorry, suite wise
[09:48] <elmo> gutsy, hardy... ?
[09:48] <Fujitsu> dapper -> hardy
[09:48]  * Fujitsu points at /ubuntu/+ppas
[09:48] <Fujitsu> I think it shows it there now, at least.
[09:49] <mtaylor> lpia fails for me alot... but that's ok... I don't have any of those :)
[09:49] <Fujitsu> It is a somewhat special arch, so I'm not surprised.
[09:50] <mtaylor> it would be nice if there were a lp option somewhere to turn off archs for a ppa
[09:50] <mtaylor> it doesn't _Really_ matter
[09:50] <mtaylor> but I hate wasting the machine time
[09:50]  * Fujitsu petitions for P-a-s for PPAs.
[09:51] <elmo> err, PPAs do use P-a-s?
[09:51] <Fujitsu> elmo: That was turned off a couple of months ago.
[09:51]  * elmo rolls his eyes
[09:52]  * Fujitsu finds the bug
[09:52] <kiko> there was actually a bug filed requesting it, too :)
[09:52] <elmo> kiko: that doesn't make it a good idea :-P
[09:52] <Fujitsu> Bug #144257
[09:52] <ubotu> Launchpad bug 144257 in soyuz "ppa builds should not be affected by P-A-S" [Low,Fix released] https://launchpad.net/bugs/144257 - Assigned to Celso Providelo (cprov)
[09:52]  * mtaylor is knocked over by flying acronyms
[09:54] <elmo> I somehow, and handwavingly, think there ought to be a  better feedback loop for those kind of changes
[09:54] <Fujitsu> elmo: Quite possibly, yes.
[09:54] <kiko> elmo, well, we do mail out a list of changes every release 
[09:54] <Fujitsu> kiko: That doesn't seem to cover all changes.
[09:54] <kiko> it's just that it's hard to sift through it to find what you want
[09:54] <kiko> Fujitsu, it does.
[09:54] <mtaylor> alright - here we go build-depping on icedtea
[09:55] <kiko> Fujitsu, it only doesn't cover all changes when the change is really invisible to the end-user -- which is rarely
[09:55] <Fujitsu> Not those that never have bugs filed for them, and are fixes that remove `bugs' that turn out to be features requested by members of the distro team months earlier....
[09:55] <kiko> Fujitsu, the release notes are not driven by bugs. they are driven by changes to the codebase.
[09:56] <Fujitsu> If there were bugs on everything, people could scream before the release broke things.
[09:56] <kiko> not really
[09:56] <kiko> there will always be changes that have unexpected effects
[09:56] <elmo> kiko: yeah, and in theory, I could subscribe to launchpad bugs to and follow things that way
[09:56] <elmo> kiko: both are too high bandwidth for me
[09:56] <kiko> elmo, you could filter only soyuz bugs, if that helps. but it's high-volume.
[09:57] <Fujitsu> If I saw a bug labelled "Secruity uploads shouldn't announce to <release>-changes", I would have questioned the validity of it, for example.
[09:57] <elmo> kiko: I guess what I'm really suggesting is that before a major behavioural changes to soyuz, in particular, should be discussed with major stakeholders (nb: not me) first
[09:57] <Fujitsu> kiko: I like the new feeds for keeping up to date with bugs.
[09:57] <kiko> elmo, we try to, but it's hard to decide what is a "major behavioural change"
[09:58] <kiko> Fujitsu, wasn't that a side-effect of another bug-fix, not actually an intentional change?
[09:58] <elmo> kiko: and btw, that bug was committed as !log :-P
[09:58] <elmo> so it wasn't in the release notes
[09:58] <kiko> elmo, really? now that's weird.
[09:58] <Fujitsu> kiko: I don't know. The people involved ran off and discussed it elsewhere one I mentioned it to someone.
[09:59] <Fujitsu> *once
[09:59] <kiko> Fujitsu, and fixed it, too? :)
[09:59] <Fujitsu> That they did.
[09:59] <kiko> mpt, done.
[09:59] <Fujitsu> Thanks kiko, Peter will be most pleased.
[09:59] <mpt> thanks kiko
[09:59] <Fujitsu> All but one member of their team seems to love LP.
[10:23] <cprov> good morning, guys
[10:24] <Fujitsu> Hey cprov.
[10:24] <geser> Hi cprov
[10:26] <cprov> hey, what's the alternative for PPA-Pas ? first, nobody was up to change P-a-s based on PPA inputs, thus it was turned off for PPAs. Now you seem to want it back ?
[10:27] <Fujitsu> User-customisable P-a-s would be workable, I presume.
[10:28] <Fujitsu> Is Soyuz's P-a-s support implemented sanely enough that that it could easily grab them from a DB, rather than the traditional file?
[10:29] <cprov> Fujitsu: no, it is still file-based
[10:29] <Fujitsu> Ah. That would make it a bit more difficult :(
[10:30] <cprov> Fujitsu: you can always make you package 'i386 amd64' instead of 'any'
[10:30] <Fujitsu> I'm not one who wants it, but that is an option, I guess.
[10:30] <Fujitsu> Hmm... Won't that just cause sbuild to fail early?
[10:33] <cprov> Fujitsu: yes, not-respecting PPA will cause more build failures, but OTOH it allow developers to work on the fix instead of being blocked by a P-a-s change
[10:34] <Fujitsu> True.
[10:34] <cprov> Fujitsu: per-PPA P-a-s sound too complicated for the PPA-approach 
[10:35] <Fujitsu> I guess you probably do want to keep it simple.
[11:16] <ubotu> New bug: #180983 in soyuz "PPA binary package size counter is wrong" [High,Confirmed] https://launchpad.net/bugs/180983
[11:16] <ubotu> New bug: #180984 in launchpad "PPA's Packages and Packages.gz ignore recommends and suggests packages control section" [Undecided,New] https://launchpad.net/bugs/180984
[11:17] <Fujitsu> Dupe.
[11:21] <kiko> yeah
=== kiko is now known as kiko-phone
[11:55] <ubotu> New bug: #180990 in soyuz "Misleading warning on oversized PPAs" [Medium,Confirmed] https://launchpad.net/bugs/180990
[12:15] <ubotu> New bug: #180992 in launchpad "Launchpad prevents us to create RSYNC only archive mirrors" [Undecided,New] https://launchpad.net/bugs/180992
=== kiko-phone is now known as kiko
=== mrevell is now known as mrevell-lunch
=== mrevell is now known as mrevell-lunch
[13:35] <ubotu> New bug: #181009 in malone "Difficult to incorporate a comment into the bug description" [Undecided,New] https://launchpad.net/bugs/181009
[13:45] <ubotu> New bug: #181013 in malone "References to other bugs are mysterious in mail notifications" [Undecided,New] https://launchpad.net/bugs/181013
=== mrevell-lunch is now known as mrevell
[13:54] <gmb> Good use of the word "mysterious".
=== cprov is now known as cprov-lunch
[14:10] <soren> I did a vgabios upload yesterday (changes file: http://launchpadlibrarian.net/11180130/vgabios_0.6a-3ubuntu1_source.changes). It shows "Launchpad-Bugs-Fixed: 180756" as expected, but the bug wasn't closed. Is this because the bug was reported against kvm? Should I have added changed the bug to be against vgabios first?
[14:46] <uws> Hmm. It seems I can't delete a series for my project on lp.net. Can someone please delete this? https://launchpad.net/gnome-specimen/ignore-this
[14:46] <uws> I made a mistake, it should've been a release in the development series
[14:46] <uws> (which I've already added)
=== salgado is now known as salgado-lunch
=== matsubara is now known as matsubara-lunch
[15:02] <kiko> uws, will do, hang on.
=== \sh_away is now known as \sh
[15:04] <uws> kiko: I should be able to do this myself right? I'm the maintainer
[15:05] <uws> and the owner of the project in lp
[15:08] <kiko> uws, I've done it. yeah, it's a bug, but easy to work around.
[15:18] <effie_jayx> hello all
=== cprov-lunch is now known as cprov
[15:18] <effie_jayx> a quick rosetta question, Could one language be translated from another language that is not English?
[15:22] <uws> kiko: how can I workaround it?
[15:23] <kiko> uws, I've done it for you.
[15:26] <uws> kiko: Thanks. But I don't trust myself... I might make this mistake again some time in the future ;)
[15:27] <kiko> uws, just ask and we'll fix it -- it's our fault until we fix the bug
[15:27]  * uws hands some more cookies to kiko
[15:27] <uws> good code monkey, hmm... s/cookies/bananas/  ;-)
[15:32] <kiko> heh
[15:34] <effie_jayx> anyone know if I can translate from a language other than English to a third language?
=== matsubara-lunch is now known as matsubara
[15:39]  * effie_jayx tries the ubuntu-translators mailing list
=== salgado-lunch is now known as salgado
=== salgado_ is now known as salgado
[17:01] <mahoney> Hey there guys, I would like some help from a Launchpad Administrator...
[17:03] <kiko> so far so good
[17:03] <mahoney> :-/
[17:05] <mahoney> How do I recognize an Admin :-D ?
[17:06] <soren> it's much easier for admins to recognize you. Just ask your question.
[17:06] <mahoney> ahhhh, thx
[17:08] <mahoney> I accidentally deleted my account on Ubuntu Wiki, and now I can't seem to log in to enything but Launchpad.  Trying to create a new account doesn't work, I've also tryied changing the name of the wiki on my launchpad account, that won't work as well.  How do I get an account on Ubuntu Wiki again?
[17:09] <kiko> mahoney, what do you mean by "accidentally deleted your Ubuntu Wiki account"?
[17:11] <mahoney> I was trying to change my username (and thus wiki address), from "MahoneyD82" to "mahoney".  I thought that by deleting the wiki, but not the launchpad account, I would be able to simply register a new one and link it to my launchpad account.
[17:12] <mahoney> But I was wrong :-( .
[17:14] <mpt> mahoney, I think the best way to deal with this is to ask for help at https://answers.launchpad.net/launchpad
[17:15] <mahoney> I wasn't sure where to ask for help.  I'll try there, thanks guys.
[17:15] <mpt> mahoney, you are suffering from bug 6283
[17:15] <ubotu> Launchpad bug 6283 in launchpad "Disabling the account thru Wiki causes more harm than good. That option should be nuked." [Medium,Confirmed] https://launchpad.net/bugs/6283 - Assigned to Andrew Bennetts (spiv)
[17:16] <mahoney> I'll tattoo 6383 on my forehead...
[17:16] <mahoney> 6283
[17:18] <kiko> mahoney, did you select the "Disable this account forever" option in the wiki?
[17:18] <kiko> if so, I wonder if mthaddon can fix that.
[17:19] <mthaddon> not sure I can help with that one, but I can forward it to the sysadmins who can
[17:20] <kiko> yeah.
[17:20] <mahoney> yup, I selected that option.  I'll try registering a second email address with my launchpad account and logging in with that.
=== salgado_ is now known as salgado
[17:50] <ubotu> New bug: #181063 in malone "Two "You might talk to..."-sentences" [Undecided,New] https://launchpad.net/bugs/181063
=== Ubulette_ is now known as Ubulette
=== salgado is now known as salgado-afk
=== matsubara is now known as matsubara-afk
[19:13] <sivang> kiko: ping
[19:13] <sivang> kiko: did you get my email ?
[19:13] <sivang> howdy all
[19:14] <kiko> sivang, yeah, I did
[19:14] <kiko> sivang, am catching up with the 200+ over the holidays!
[19:14] <kiko> how's it going?
[19:25] <thumper> morning
[19:25] <kiko> mdz!!
=== salgado-afk is now known as salgado
=== matsubara-afk is now known as matsubara
=== cprov is now known as cprov-out
[19:36] <sivang> matsubara: hey dude, what's up?
[19:39] <matsubara> hey sivang! how're the portuguese lessons going?
=== kiko is now known as kiko-afk
[19:40] <kiko-afk> kiko seu mané
[19:41] <matsubara> heh
[19:41] <sivang> kiko seu mane, me ensina pourtugese :)
[19:41] <sivang> or something like that without all the spelling mistakes
[19:42] <sivang> matsubara: flouresta amazonica :)
[19:42]  * sivang does the accent for himself
[19:50] <Kmos> sivang: portugues nao costuma ser fácil de aprender.
[19:50] <Kmos> :)
[19:52] <sivang> Kmos: what does that mean? :)
[19:53] <Kmos> sivang: learn portuguese is not always easy to do
[19:53] <Kmos> :)
[19:53] <mtaylor> leaning portugese is impossible!
[19:53] <Kmos> hehe
[19:56] <sivang> that's true!
[20:29] <sivang> kiko-afk: guess what I'm listening to now
[20:57] <bdmurray> Any malone people around?
[20:57] <thumper> bdmurray: some
[20:57] <bdmurray> I went to this url https://bugs.launchpad.net/ubuntu/+bug/176435 and it says "Bug 176435 is not in Ubuntu"
[20:57] <ubotu> Launchpad bug 176435 in twill "python-twill missing a dependency" [Medium,Fix released] https://launchpad.net/bugs/176435
[20:57] <bdmurray> which seemed odd to me
[20:58] <bdmurray> maybe my url construction is wrong though
[21:05] <thumper> bdmurray: the bug is in the sourcepackage twill of ubuntu
[21:05] <thumper> bdmurray: so yes your url construction is a little wrong
[21:05] <thumper> bdmurray: to use the generic bug reference, use what ubotu shows above
[21:09] <bdmurray> thumper: okay I think I understand
[21:10] <bdmurray> so https://bugs.launchpad.net/ubuntu/+bug/ would be used for bugs without a package then?
[21:13] <thumper> bdmurray: yes, I think so
[21:13] <Ubulette> how come i keep receiving every few days ftbfs emails for the same package (that's i've synced 1 month ago) on hppa ?
[21:13] <bdmurray> okay, I suspected the person who sent it to me handcrafted the url then
[21:16] <geser> Ubulette: does it build on hppa?
[21:17] <Ubulette> no: https://edge.launchpad.net/ubuntu/+source/ruby-gnome2/0.16.0-10/+build/466217
[21:17] <Ubulette> The following packages have unmet dependencies:
[21:17] <Ubulette>   libcairo-ruby: Depends: libcairo-ruby1.8 but it is not installable
[21:19] <geser> Ubulette: there was a massive give-back and some large give-backs due to broken chroots in the last two weeks
[21:19] <Ubulette> got that exact same ftbfs about 5 times
[21:20] <geser> if the reason for the ftbfs isn't fixed but the package gets retried, you get everytime a mail about it
[21:21] <Ubulette> oh, ok
[21:21] <geser> Ubulette: if you want that is stops, try to find out why libcairo-ruby1.8 is missing on hppa an how to fix it :)
[21:23] <Ubulette> it's "need-building"
[21:23] <Ubulette> https://edge.launchpad.net/ubuntu/+source/libcairo-ruby/1.5.0-1/+build/435640
[21:27] <geser> lamont: ^^^ are the hppa buildds so much loaded that it didn't build a package queued 2 months ago?
[21:27] <lamont> geser: everything was just given back
[21:33] <geser> lamont: so the date listed at "Queued" doesn't contain any useful information?
[21:37] <lamont> geser: lots of useful information, just none of it related to why hppa hasn't tried to build it yet...
[21:37] <lamont> it's finished off the queue several times now
=== \sh is now known as \sh_away
[21:48] <lifeless> statik: around?
[21:48] <statik> lifeless: I am, and lurking on #bzr, and just sent a pm to zeasier
[21:48] <statik> :)
[21:49] <lifeless> :>
[21:49] <lifeless> get my mail a few days ago?
=== neversfelde_ is now known as neversfelde
=== kiko-afk is now known as kiko-zzz