[12:32] <mpt> Goooooooooooooood afternoon Launchpadders!
[12:33] <LarstiQ> heh
[12:42] <lifeless> mpt: just woke up ?
[12:43] <mpt> yes
[01:46] <lifeless> spiv:
[01:46] <lifeless> sftp://chinstrap/home/warthogs/archives/daf/launchpad/flaky
[01:46] <lifeless> I presume that fell through de cracks
[01:53] <spiv> lifeless: Hmm, I guess it must have.
[01:53] <spiv> lifeless: I'll deal with it.
[05:14] <M0RB> hello all
[06:50] <stub> jamesh: I just reviewed your ErrorReportManagement branch. It would be good if you can land that today.
[06:51] <jamesh> stub: okay
[07:30] <dilys> Merge to devel/launchpad: [trivial]  migrate bug aliases during bugzilla import (r2990: James Henstridge)
[07:49] <dilys> Merge to devel/launchpad: soft timeout support, log SQL statements in error reports, r=stub (r2991: James Henstridge)
[08:21] <dilys> Merge to devel/launchpad: [r=lifeless for most, trivial for the rest]  Trims margins and gutters of page layout and portlets. Fixes bug 3557 ('New' bug status is almost unreadable) and bug 6563 (No easy way to go to branch listings from a branch page). Updates the copyright info. Fixes the spec status colors. (r2992: Matthew Paul Thomas)
[09:23] <carlos> morning
[09:28] <jamesh> hi carlos
[09:58] <SteveA> morning!
[10:00] <mpt> evening :-)
[10:00] <jamesh> so, product milestone pages don't seem to handle bug privacy
[10:14] <daf> morning
[10:26] <stub> jamesh: Can I set up what is needed for the bugzilla migration now? I'm hoping to be elsewhere at 12:00UTC (although I'll have my phone and can return if needed)
[11:12] <jamesh> stub: sure.  I just need the DB access and know that the database has been backed up
[11:14] <stub> jamesh: What access do you need? Connect as the launchpad user from jamesh@macquarie?
[11:14] <jamesh> stub: yeah.
[11:14] <stub> I'll be kicking the backup off in a tick
[11:14] <jamesh> same as I had for the initial contacts migration
[11:15] <ddaa> stub: any idea why the bzrsyncd logs do not seem to show up on launchpad-error-reports?
[11:17] <stub> Most likely the emails are not getting to the mailing list.
[11:17] <stub> Check the MAILTO= line in the crontab (if you are running from crontab), and if you can check the mailq on that box
[11:17] <ddaa> I set the mailto yesterday... mhh checking mailq right now
[11:17] <stub> jamesh: You should have access now
[11:19] <ddaa> okay, it's full
[11:19] <ddaa> A857D450143     2262 Fri Jan 13 07:30:02<EMAIL_ADDRESS>[11:19] <ddaa> (delivery temporarily suspended: connect to lists.canonical.com[<IP_ADDRESS>] : No route to host)
[11:19] <ddaa><EMAIL_ADDRESS>[11:20] <ddaa> stub: should I ask a sysadmin to fix that?
[11:24] <jamesh> stub: thanks
[11:57] <jamesh> lifeless: is there some problem synching commits from pqm?
[11:59] <jamesh> lifeless: I've had two pqm success emails today, but neither of those commits appear in the branch on chinstrap.
[12:25] <matsubara> good morning!
[12:28] <daf> stub: on the MaloneRunsUbuntuTaskList, there's an item "fti triggers are off"
[12:39] <matsubara> Is there someone who can fix the rf-built tree? It hasn't been update for awhile.
[12:47] <daf> ooh, ZODB has been released as a separate package
[12:48] <daf> plus Zope 3.2
[12:48] <daf> no "x"
[12:49] <jamesh> matsubara: the rocketfuel/launchpad/devel branch on chinstrap doesn't seem to have been updated for a while either
[12:51] <matsubara> jamesh: hmm, do you have any idea why?
[12:53] <cprov> morning hackers
[12:54] <stub> daf: Done
[12:54] <daf> stub: awesome
[12:55] <jamesh> matsubara: merges get performed on another machine.  I assume that there is a problem mirroring the changes back to chinstrap
[12:55] <stub> jamesh: Can you confirm you can connect? The backup has just completed and I'm heading out (retrievable by mobile if necessary)
[12:56] <jamesh> stub: seems fine.
[12:57] <daf> jamesh: "ensure bug aliases are imported" is also on the list -- has that been fixed?
[12:57] <daf> yo Bradster
[12:58] <bradb> hey daf
[12:58] <jamesh> daf: I merged it earlier today, but it hasn't gotten through to the rocketfuel mirror on chinstrap
[12:58] <jamesh> daf: I'm just going to apply the patch directly to the LP tree I use for the import
[12:59] <daf> jamesh: right -- that's good enough for me :)
[01:01] <daf> bradb: do we have a bug on "Ensure bug contacts are subscribed to existing bugs"?
[01:01] <daf> bradb: if not, maybe you could file it, since you know the SQL-fu involved
[01:02] <mpt> grr
[01:03] <ajmitch> mpt: not working late, are you?
[01:03] <mpt> ajmitch, no, no, not at all, just marking duplicates
[01:03] <mpt> that's not work
[01:04] <daf> er, is there something about these duplicates that means you have to deal with them now?
[01:15] <jamesh> the dilys messages indicate that there are 16 revisions not mirrored to chinstrap
[01:15] <ddaa> is staging known to be down, or is it not on staging.ubuntu.com anymore?
[01:15] <ddaa> (or do I have some other problem?)
[01:16] <ddaa> mpt: I saw you fixed one of my usability bugs, I'd like to look at the result...
[01:17] <SteveA> cprov: hi
[01:17] <SteveA> cprov: is kiko at async yet?
[01:17] <cprov> SteveA: hi, not yet AFAIK ...
[01:17] <SteveA> we're supposed to be starting the bugzilla->malone work already
[01:18] <cprov> SteveA: let me call him
[01:19] <cprov> SteveA: kiko's ETA 30 min, busy at home due personal issues
[01:19] <SteveA> ok, thanks
[01:20] <SteveA> jamesh: is this okay for you?
[01:20] <jamesh> SteveA: sure.  I'm just getting things ready for the migration at the moment (disabling bugzilla, etc)
[01:22] <SteveA> ok
[01:22] <bradb> daf: We don't have a bug filed that I know of. It was one of the things on my task list from #c-m yesterday. I can open a bug for it.
[01:23] <daf> up to you
[01:26] <mpt> ddaa, you could merge rocketfuel or just merge my trivial branch
[01:26] <ddaa> I'm having enough trouble with i/o contention, slow bzr, and contention for different db schemas, so I'd rather not...
[01:31] <daf> er, is Launchpad down?
[01:33] <Kinnison> it's certainly not responding for me
[01:33] <ajmitch> works here
[01:33] <mpt> worksforme
[01:33] <mpt> move to NZ
[01:33] <daf> ah, it's back
[01:34] <matsubara> mpt: hey! Johan has a feature request for you on bug 6725. :)
[01:35] <daf> mpt: by the way, that dup was because searching for "upstream" returned all 200 open bugs
[01:35] <mpt> matsubara, I saw that, and I vaguely remember disagreeing
[01:35] <mpt> daf, yeah, I had the same problem when searching for the original, and eventually resorted to the search function of my mail client
[01:37] <mpt> however, daf, removing the product/package name from the searched text is also covered in the MaloneSearch spec :-)
[01:37] <daf> I don't see why "upstream" would match every bug though
[01:37] <mpt> because the name of the product is "upstream malone"
[01:37] <mpt> as silly as that seems
[01:37] <daf> doh!
[01:37] <mpt> or rather, "malone (upstream)"
[01:39] <mpt> I reported that as a bug quite a while ago
[01:39] <daf> I wonder how hard it is to fix
[01:39] <daf> #?
[01:40] <mpt> haha, you expect me to be able to find it?
[01:40] <daf> :)
[01:40] <daf> aha, bug 5782
[01:40] <Ubugtu> Error: Could not parse data returned by Malone: Connection to Malone bugtracker failed: The read operation timed out
[01:41] <daf> (I searched for "search")
[01:41] <mpt> yes
[01:41] <mpt> You're lucky that "search" worked, because substring searching isn't implemented yet either
[01:41] <mpt> and the title has "searching"
[01:42] <daf> I think maybe it's fti being clever about suffixes
[01:42] <mpt> oh, right
[01:42] <mpt> so I need a better example in the spec
[01:42] <daf> which, of course, it horribly English-specific
[01:43] <Kinnison> fti has language modes
[01:43] <bradb> mpt: Substring searching on the targetname is implemented.
[01:43] <Kinnison> but I think only english (and russian?) are implemented
[01:43] <sabdfl> hey folks
[01:43] <sabdfl> how is the malone transition going?
[01:43] <bradb> It's waiting on kiko-zzz, it seems. SteveA?
[01:44] <SteveA> hi
[01:44] <jamesh> SteveA: login to bugzilla is now disabled.  Do you want me to wait for kiko before starting the migration?
[01:46] <SteveA> i can't get kiko on the phone
[01:46] <SteveA> so, i'm not sure what's up, or when he'll be around
[01:47] <SteveA> ok
[01:47] <SteveA> kiko will be around in 15 mins
[01:47] <daf> mpt: did I send you a mail about headings?
[01:47] <SteveA> jamesh: what's the next step?  run the script?
[01:47] <jamesh> SteveA: yeah
[01:47] <mpt> daf, yes
[01:48] <SteveA> Znarl: are you available to change the bugzilla front page shortly?
[01:48] <SteveA> jamesh: who else do we need around here?
[01:48] <Znarl> SteveA : Yes.
[01:48] <daf> mpt: ok, wasn't sure
[01:48] <jamesh> SteveA: I don't think we need anyone else at this point.
[01:48] <seb128> good luck :)
[01:49] <daf> push that big red button!
[01:49] <SteveA> has stu done the right kind of backups or whatever?
[01:49] <daf> yes
[01:49] <jamesh> yes
[01:49] <SteveA> okay
[01:49] <SteveA> so, no reason to wait any longer.  run the script, james
[01:50] <SteveA> jamesh: have you tested that bugzilla logins are disabled?
[01:50] <jamesh> SteveA: yes.
[01:50] <seb128> I've tested
[01:50] <SteveA> cooll
[01:50] <seb128> I get a page saying to mail jdub if I want to complain :p
[01:51] <mpt> my eyes, the redness
[01:52] <jamesh> https://launchpad.net/distros/ubuntu/+source/openssl/+bug/6761 <- ubuntu bugzilla bug #1
[01:52] <mpt> er, "Please press Back and try again?" I don't think that will do much
[01:52] <Ubugtu> Error: Could not parse data returned by Malone: Connection to Malone bugtracker failed: The read operation timed out
[01:53] <seb128> jamesh: malone is update on the fly, no lock? we can use it?
[01:53] <daf> seb128: yes
[01:53] <jamesh> seb128: yeah
[01:53] <seb128> ah, nice :)
[01:53] <ddaa> I'm sure when you were a kid you just loved putting your fingers in mechanisms...
[01:54] <seb128> yeah, it's fun :)
[01:54] <bradb> mdz: ping
[01:55] <ddaa> how comes you are not packaging KDE then? It actually has a gear as its logo!
[01:55] <SteveA> ddaa: http://source.schooltool.org/trac/timeline
[01:55] <SteveA> ddaa: http://source.schooltool.org/trac/changeset/5485
[01:55] <bradb> jamesh: How long does this take to run?
[01:55] <ddaa> yeah, I now the timeline feature rocks
[01:55] <SteveA> ddaa: are we going to have pages like this in launchpad?
[01:56] <jamesh> bradb: the run against staging took about 3 hours
[01:56] <jamesh> bradb: I don't know how representative that is for a production import though
[01:56] <ddaa> I remember somebody asked for that. But the timeline thing is actually something more.
[01:56] <mpt> past 7000 bugs ...
[01:56] <bradb> jamesh: ok, thanks
[01:56] <jamesh> we are talking of about 22000 bugs
[01:56] <ddaa> SteveA: for example it can display bug tracker activety.
[01:56] <lifeless> jamesh: I will check logs
[01:57] <lifeless> matsubara: it is up to date with the rocketfuel on chinstrap
[01:57] <lifeless> matsubara: which is what it updates against: it is not broken.
[01:58] <ddaa> SteveA: I think that would a feature with a feature with good effort/result ratio: make a page per product that collates all the product's activity: bugs, branches, translations, specs
[01:58] <ddaa> with some "projection views" that show only some of those aspects
[01:58] <bradb> Kamion: the BZ migration is running. Now might be a good time to set up the bug contact for ubuntu: https://launchpad.net/distros/ubuntu/+editbugcontact
[01:58] <mpt> ddaa, give it the URL launchpad.net/products/foo
[01:58] <Kamion> I suspect I don't have the necessary privileges, but will check
[01:58] <jordi> oh my
[01:58] <Kamion> wow, lp's slow
[01:59] <jordi> is the bugzilla migration being done right now?
[01:59] <ddaa> SteveA: but as far as I'm concerned, this sort of stuff is probably post march sprint.
[01:59] <Kinnison> Kamion: it appears to be having problems if you're in the UK
[01:59] <jamesh> Kamion: I've created an ubuntu-bugs team pointing at the existing list
[01:59] <Kamion> bradb: if I can, do I want to set it after the migration's finished, or does it not matter?
[01:59] <Kinnison> Kamion: dunno why
[01:59] <bradb> Kamion: It shouldn't matter
[02:00] <Kamion> yeah, 403 on +editbugcontact
[02:00] <Kamion> Keybuk may be able to set it
[02:00] <bradb> Kamion: I can set it. Is there already a team reg'd though?
[02:00] <ddaa> SteveA: important priorities, like importd->bzr transition, fixing the branch UI, unblocking grumpy, setting up branch email notifications take precedence.
[02:00] <kiko> doctor is in
[02:00] <SteveA> hi kiko
[02:00] <SteveA> so, bugzilla is locked
[02:00] <SteveA> the import script is running
[02:00] <ajmitch> nice, the bug count on launchpad rises quickly now..
[02:00] <lifeless> stale write lock on chinstrap
[02:01] <mpt> past 8000 ...
[02:01] <Kamion> bradb: https://launchpad.net/people/ubuntu-bugs
[02:01] <SteveA> znarl is available to change the front page of bugzilla whenever
[02:01] <lifeless> thats been removed, next commit to pqm will straighten everything out
[02:01] <kiko> SteveA, Znarl: by locked, what do you mean?
[02:01] <jamesh> so, we are up to bug 1300 in about 10 minutes
[02:01] <Kamion> kiko: login disabled
[02:01] <ddaa> SteveA: if you want that given some serious thought soon, we'll need to reprioritize some other things.
[02:01] <kiko> Kamion, disabledtext not null for everybody?
[02:02] <SteveA> ddaa: no, not for now.  it came up in a separate conversation, and i just wanted your opinions.
[02:02] <ddaa> My opinion: it rocks, launchpad can do much better, there's no spec and no time ATM.
[02:02] <kiko> jamesh, did you manage to get alias conversion going?
[02:02] <jamesh> kiko: yeah.
[02:02] <kiko> great.
[02:03] <bradb> Doh, no stub.
[02:03] <kiko> jamesh, are you running the import off a branch of yours then?
[02:03] <lifeless> bradb: you'll be getting those due to lock contention I expect
[02:03] <jamesh> kiko: rocketfuel + my alias migration patch
[02:04] <bradb> I thought as much. I hope the same doesn't happen to the import script though.
[02:04] <kiko> lifeless, there's about 10 patches missing in launchpad/devel and -built
[02:04] <jordi> woa, lp is totally dead
[02:04] <SteveA> jordi: not for me
[02:04] <jordi> works again
[02:04] <SteveA> it's pretty fast
[02:05] <bradb> Kamion: Hm, timeouts trying to set the bug contact. I'll set the bug contact as soon as LP lets me.
[02:05] <jamesh> kiko: the alias stuff is merged into rocketfuel, but the rocketfuel mirror on chinstrap doesn't seem to have everything that PQM says it has merged
[02:05] <jordi>
[02:05] <jordi> 6758. OOPS-13A303
[02:05] <jordi> launchpad (upstream), reported by  Vincent Gache on 2006-01-13
[02:05] <jordi> timeout this looks bad
[02:05] <kiko> lifeless, note jamesh' comment -- are you aware of non-mirroring of changes into chinstrap?
[02:06] <jamesh> kiko: he's looking into it
[02:06] <kiko> ah, okay -- he wrote me mail saying it was up-to-date :)
[02:06] <lifeless> kiko: it was, for what it claims to be up to date against
[02:06] <lifeless> kiko: 00:00 < lifeless> stale write lock on chinstrap
[02:06] <kiko> yeah, I figured that would have been the case
[02:06] <lifeless> kiko: 00:01 < lifeless> thats been removed, next commit to pqm will straighten everything out
[02:09] <bradb> It's Friday the 13th, the Malone migration is running, and there's fire trucks, ambulance and police out front. I hope this isn't a sign.
[02:10] <kiko> launchpad is dying all over the place for me
[02:10] <bradb> lock contention, most likely
[02:10] <mpt> 9000...
[02:12] <kiko> gangotri is mostly idle
[02:12] <kiko> we could nice process 14181 if we want to make the script lose more often
[02:13] <lifeless> gnight
[02:13] <mpt> 10000 bug reports in Malone
[02:13] <daf> 6927 against Ubuntu
[02:14] <kiko> fun
[02:14] <bradb> jamesh: Do you have a moment to look at my reply to your status notes as comments review from yesterday?
[02:14] <ajmitch> mpt: a shame i didn't get to file #10000, like I did #5000
[02:15] <mpt> or me, since I reported #1000 :-)
[02:15] <ajmitch> it's such an honour :)
[02:15] <kiko> jamesh, and your script doesn't set the default bug contacts?
[02:16] <jordi> I think I reported my birth year or something :)
[02:16] <daf> mpt: you haven't fixed #6666 for me yet
[02:16] <mpt> ubugtu 6666
[02:20] <bradb> http://www.alistapart.com/articles/sensibleforms # I love the artwork
[02:21] <kiko> jamesh?
[02:31] <carlos> SteveA, kiko hi
[02:31] <kiko> hey carlos
[02:31] <carlos> sorry, I missed the whole morning trying to fix my mobile phone card but Vodafone is .... I'm still without mobile phone and will work until late today
[02:32] <carlos> I think I will need to go out again this afternoon but this time will be really one hour (if they call me to tell me that all is fixed)
[02:33] <carlos> I'm going to have lunch now.
[02:33] <carlos> kiko, SteveA is there anything you need from me before I leave?
[02:33] <kiko> carlos, not really
[02:34] <carlos> ok
[02:34] <carlos> anyway I will be near the computer
[02:34] <carlos> see you later
[02:34] <[GNU] > hello all
[02:35] <jamesh> kiko: it doesn't set the specifically, but everyone who was subscribed to the bug before should be subscribed after
[02:35] <[GNU] > is there a short desription out there on "how to make a suggestion for improvments for a given product" ?
[02:35] <jamesh> bradb: sure.  I'll look now
[02:35] <bradb> jamesh: thanks
[02:36] <kiko> bradb, jamesh' bugs probably don't have the initial bug contacts added, right
[02:36] <kiko> ?
[02:37] <jamesh> kiko: currently most of the initial contacts in Malone are ported over from Bugzilla
[02:37] <bradb> We have to write a separate script either way, because all the existing Ubuntu bugs need ubuntu-bugs Cc'd as well
[02:37] <kiko> okay
[02:37] <bradb> I thought kiko meant the Cc's
[02:37] <kiko> I didn't
[02:37] <jamesh> kiko: the existing bug subscribers in bugzilla get ported over, which should be pretty much the same
[02:37] <jamesh> bradb: would it be difficult to have "distro component bug contacts"?
[02:38] <kiko> jamesh, well, I'm talking about the default bug contact in malone, which has no counterpart in bugzilla.
[02:38] <bradb> jamesh: InitialBugContacts provides for that using mailman keywords, but I didn't implement that header yet.
[02:39] <bradb> i.e. So that you can create mailman topics out of the Keywords header
[02:39] <jamesh> kiko: the assignee?
[02:39] <kiko> jamesh, no. ubuntu-bugs.
[02:40] <jamesh> kiko: I was planning on setting it as the distro bug contact after the import, and make sure it is subscribed
[02:40] <bradb> I tried setting it earlier, but I'm still getting timeouts.
[02:40] <kiko> that would have been ideal, jamesh -- but we can sql script it now.
[02:40] <jamesh> I wonder if one of the app servers is having trouble.
[02:40] <bradb> 15,000 bugs and counting
[02:41] <kiko> carlos, ping?
[02:41] <jamesh> we're up to bugzilla #8980
[02:41] <ddaa> A Miracle!
[02:42] <ddaa> Holy Brad!
[02:42] <ddaa> The Multiplication Of Bugs!
[02:42] <carlos> kiko, pong
[02:42] <AlinuxOS> boys, is it import module switched on?
[02:42] <seb128> by default bugs are not assigned with malone?
[02:42] <daf> https://launchpad.net/distros/ubuntu/+bugs says "All bugs ever reported (12216)"
[02:43] <jamesh> seb128: correct.  But some people may get CC'd by default.
[02:43] <kiko> seb128, by default, no.
[02:43] <seb128> grumpf
[02:43] <seb128> I think I'm not going to like not having "My Bugs" to work on
[02:43] <LarstiQ> AlinuxOS: currently bugzilla bugs are imported into malone
[02:43] <daf> I'm guessing we don't have a bug open on auto-assign
[02:44] <AlinuxOS> I mean .po file upload (import).
[02:45] <kiko> seb128, you can set yourself as a bug contact for the packages you want to look at
[02:45] <AlinuxOS> yesterday I've updated some .po files... and It worked...
[02:45] <seb128> bradb: can we change the default assignee for a package from somewhere?
[02:45] <bradb> Seems to be importing about 500 bugs/minute
[02:45] <kiko> and if it's a large set of packages, seb128, you can give us a list and we can do a mass-update
[02:45] <kiko> seb128, a bug contact for the packages will be CCed on all new bugs filed on those packages
[02:45] <bradb> seb128: Yeah, https://launchpad.net/distros/ubuntu/+source/3dchess/+subscribe.
[02:45] <seb128> kiko: basically all the bugzilla component I was the default assignee :p
[02:45] <kiko> you can assign yourself to the bugs as fit
[02:46] <seb128> grumpf
[02:46] <kiko> bradb, jamesh: the package bug contacts have been migrated, right?
[02:46] <seb128> I get like 100 GNOME bugs week on my package
[02:46] <jamesh> kiko: yes.
[02:46] <seb128> now I'll have to reassign that to me instead of getting it "just working"?
[02:46] <seb128> s/package/packages
[02:46] <kiko> seb128, no, there's a slight change in concepts.
[02:47] <kiko> seb128, you get subscribed to all bugs reported on those packages (and jamesh confirmed that all package bug contacts have been migrated, so don't worry)
[02:47] <seb128> is there a "Bug I'm watching" list ?
[02:47] <kiko> you can assign yourself to the ones you are actually going to work on
[02:47] <Kamion> it basically means that now we can't tell the difference between "somebody subscribed me because they thought I might have something to contribute" and "new bug on one of my packages"
[02:47] <kiko> seb128, yes.
[02:47] <Kamion> that was what default-assignee gave us
[02:47] <kiko> Kamion, yes. but now you can differentiate between a bug reported on one of your packages and a bug you are working on.
[02:47] <seb128> kiko: I'm basically going to work on all the bugs assigned to my packages
[02:47] <Kamion> kiko: I could already do that, by state (NEW vs. ASSIGNED)
[02:48] <AlinuxOS> how I can convert .mo file to .po file?
[02:48] <Kamion> I was hoping that "Bugs on Maintained Software" would give me bugs on all the packages for which I'm the contact, but apparently not
[02:48] <kiko> seb128, you'are also probably going to invalidate, reassign, dupe and redirect bugs.
[02:48] <Kamion> AlinuxOS: msgunfmt
[02:48] <seb128> AlinuxOS: msgunfmt .mo
[02:49] <seb128> Kamion: yeah, would be nice
[02:49] <AlinuxOS> Kamion, I dosen't have this package
[02:49] <Kamion> AlinuxOS: gettext
[02:49] <bradb> Kamion: There's a bug open on that.
[02:49] <AlinuxOS> sudo apt-cache search msgunfmt
[02:49] <AlinuxOS>  NO results
[02:49] <kiko> Kamion, seb128: in general, open source doesn't benefit from default assignees because people don't see these bugs as bugs that are up-for-grabs -- even if the person sitting on them is not going to work on them anytime soon.
[02:49] <jamesh> bradb / kiko: https://launchpad.net/distros/ubuntu/+bug/16257 is an example imported bug with its alias migrated
[02:49] <kiko> jamesh, lovely work
[02:49] <Ubugtu> Error: Could not parse data returned by Malone: Connection to Malone bugtracker failed: The read operation timed out
[02:49] <Kamion> AlinuxOS: it's in the gettext package. apt-cache search doesn't do a file search.
[02:50] <seb128> kiko: if I can't even have a list on bug I'm supposed to take care of them you are sure I'll not work on them :p
[02:50] <seb128> kiko: I like bugzilla "My Bugs"
[02:50] <AlinuxOS> ah Kamion thanks
[02:50] <bradb> Darn, it looks like stub didn't fix the fti's either, which is making the search seem much worse than it is.
[02:50] <Kamion> kiko: open source or not open source, I have a job to do which involves taking care of bugs on a set of packages
[02:50] <bradb> jamesh: nice
[02:50] <Kamion> so I need a way to see them; I'm not bothered exactly what that way is
[02:51] <seb128> same for me
[02:51] <kiko> Kamion, seb128: there is a way to see them, worry not.
[02:51] <bradb> Kamion: bug 6610
[02:51] <Kamion> kiko: what is it?
[02:51] <seb128> I want a list of the bugs on "my packages" because that's the bugs I'm supposed to take care of
[02:51] <kiko> I'm trying to load a page bug launchpad seems to have trouble
[02:51] <kiko> s/bug/but
[02:51] <Ubugtu> Error: Could not parse data returned by Malone: Connection to Malone bugtracker failed: The read operation timed out
[02:51] <Kamion> bradb: thanks
[02:51] <AlinuxOS> msgunfmt gaim.mo -o gaim.po .done.
[02:51] <bradb> np
[02:52] <AlinuxOS> Kamion, seb128 thanks!
[02:52] <seb128> np
[02:52] <jamesh> kiko: seems to be a problem with one of the app servers.  Znarl is checking it
[02:52] <kiko> okay.
[02:53] <jamesh> we're a bit over half way there
[02:53] <jamesh> in one hour
[02:54] <kiko> wake up app server
[02:54] <kiko> Znarl, can you turn off the pound redirect to the broken app server?
[02:54] <Znarl> kiko : Yes, I can.
[02:55] <kiko> that would help already
[02:56] <kiko> bradb, really unfortunate the fti borkage
[02:56] <bradb> indeed
[02:58] <daf> stub said he'd fixed it earlier
[02:58] <kiko> did he?
[02:59] <daf> hes, just before he left
[02:59] <daf> * yes
[03:04] <kiko> yet bradb seems to think it's still off
[03:05] <bradb> It's off for as long as searching for "maintained" doesn't find bug 6610
[03:08] <kiko> bradb, email to stuart and launchpad, please
[03:09] <bradb> sent
[03:10] <jamesh> kiko: how hard do you think it would be to get the bugzilla status watching code to update bugtask statuses?
[03:10] <kiko> jamesh, not very hard at all.
[03:10] <jamesh> kiko: and send email on such changes? :)
[03:11] <kiko> I mean, it's following a single foreign key and updating
[03:11] <kiko> I'm not sure -- bradb how hard is it to generate some bugmail?
[03:12] <kiko> bradb, matsubara: why is https://launchpad.net/people/seb128/+packagebugs empty?
[03:12] <bradb> Not hard. Just publish an SQLObjectModifiedEvent along with the status change.
[03:12] <bradb> kiko: bug 6610
[03:12] <Ubugtu> Malone bug 6610: ""Bugs on Maintained Software" should be changed to a "Bugs for Bug Contact" report" Fix req. for: malone (upstream), Severity: Normal, Assigned to: Nobody, Status: Confirmed http://launchpad.net/bugs/6610
[03:12] <kiko> bradb, I <3 you
[03:14] <seb128> kiko: I've no bug, \o/
[03:14] <bradb> jamesh: How does the status notes as comments diff look?
[03:14] <Kamion> bradb: I tried to think of a better title for that and couldn't
[03:14] <kiko> seb128, you can give me a massage now
[03:15] <Kamion> bradb: any problem with just leaving it as "Bugs on Maintained Software", even though that's not exactly what it corresponds to under the hood any more?
[03:15] <bradb> Kamion: That's not what it corresponds to in the UI.
[03:16] <bradb> Under the hood is just details, one way or the other. :) We don't have a "maintainer" in the UI anymore though.
[03:16] <kiko> maintainer is a bad bad name
[03:16] <seb128> kiko: you wish :)
[03:16] <kiko> my legs hurt
[03:17] <bradb> Kamion: Leaving it "Bugs on Maintained Software" would mean that I see bugs on that page, even if I'm subscribed to bugs in that package for reasons other than being responsible for fixing those bugs.
[03:17] <daf> bradb: I think +packagebugs might be misleading
[03:17] <jamesh> bradb: sorry haven't looked through all of it
[03:17] <kiko> I thought the name +packagebugs was well-suited to package bug contacts
[03:17] <jamesh> bradb: one issue I noticed first up is that you are importing canonical.launchpad.database.* classes into helpers.py
[03:18] <daf> are bug contacts always on packages?
[03:18] <Kamion> "Bugs on My Packages" except that it's not always My
[03:18] <daf> or on products too?
[03:18] <jamesh> bradb: which shouldn't be done, iirc
[03:18] <ddaa> I would need to use a literal url "http://bazaar.launchpad.net/" (the root of the supermirror) in at least two places in the code. This has only one globally meaningful value. Should I make it a configuration setting? I thinking of making it an optional config entry in the "launchpad" section with the right default value. Would that be okay?
[03:19] <seb128> hum
[03:19] <kiko> ddaa, I think that's okay.
[03:20] <bradb> jamesh: Hm, I'm a bit stumped on how to do create-bug-message without firing off the event then, like IBug.newMessage does.
[03:21] <bradb> The use case for not firing it off is so that a separate email doesn't get sent containing only a comment when a comment is made with a change.
[03:21] <jamesh> bradb: a really cheesy way to do it would be to add a "no notify" argument to newMessage(), which defaults to false
[03:21] <bradb> jamesh: Yeah, I considered that.
[03:22] <bradb> It seemed a bit strange, but if you think it's ok, I'd be happy to do it.
[03:22] <jamesh> bradb: as I said in my original email, long term it might be worth trying to collate events for a particular bug and generate a single mail at the end of the transaction or something similar.
[03:23] <bradb> yeah
[03:23] <jamesh> bradb: the additional argument to newMessage() would be cleaner than moving the code to helpers.py (although still a bit ugly)
[03:23] <bradb> ok
[03:23] <jamesh> I suppose it would be okay if you add appropriate XXX comments
[03:24] <bradb> Sure, I'll do that and open a bug.
[03:24] <jamesh> the rest of that incremental diff looks okay
[03:25] <bradb> ok, cool
[03:27] <AlinuxOS> hello hakers :) I've cheked https://launchpad.net/rosetta/imports all of my imported files are FALSE cheked.
[03:30] <jamesh> 85%
[03:34] <AlinuxOS> carlos, ?
[03:34] <AlinuxOS> jordi, ?
[03:34] <kiko> bradb, maybe fti.py caching is the culprit?
[03:35] <bradb> Not sure.
[03:37] <carlos> AlinuxOS, that only happens with files that are the first time we see them
[03:37] <carlos> AlinuxOS, look at the first table, you have the bum file waiting for being importe
[03:37] <carlos> imported
[03:37] <bradb> Whoa, I just opened bug #25724 :)
[03:39] <daf> jamesh: the bug count seems to have stopped going up -- are we done?
[03:39] <jamesh> daf: I don't think so
[03:40] <jamesh> the script has stopped generating output, but it hasn't completed
[03:40] <bradb> https://launchpad.net/distros/ubuntu/+source/zeroconf/+bug/22057 looks like a very new bug report, at least :)
[03:40] <Ubugtu> Malone bug 22057: "Zeroconf process use 100% CPU" Fix req. for: zeroconf (Ubuntu), Severity: Normal, Assigned to: Nobody, Status: Unconfirmed http://launchpad.net/bugs/22057
[03:40] <bradb> (the newest open bug I see on ubuntu)
[03:41] <kiko> bradb, see how it has no subscribers?
[03:41] <daf> bradb: but the next-newest one is 13332 :)
[03:41] <jamesh> bradb: that's not a migrated bug
[03:41] <kiko> well, the reporter.
[03:42] <jamesh> there are no bug contacts for zeroconf
[03:42] <kiko> and for a distro contact ubuntu?
[03:42] <kiko> ahhm
[03:42] <kiko> and a distro contact for ubuntu?
[03:42] <jamesh> I haven't set the distro contact yet
[03:42] <bradb> hm
[03:43] <kiko> bradb, should I set the ubuntu bug contact?
[03:43] <bradb> bug 13332 doesn't have an external bug linked to it
[03:43] <Ubugtu> Malone bug 13332: "Please run update-rcconf-guide automatically after installing (in postinst)" Fix req. for: rcconf (Ubuntu), Severity: Normal, Assigned to: Nobody, Status: Unconfirmed http://launchpad.net/bugs/13332
[03:43] <bradb> kiko: Sure, if that page isn't timing out anymore.
[03:43] <kiko> bradb, I'm wondering if we're going to spam that with migrated bugs?
[03:44] <kiko> bradb, hmmm good point
[03:44] <AlinuxOS> carlos, and Is it automatical update ?
[03:44] <kiko> jamesh?
[03:44] <daf> bug 100030 has the correct bug contacs, I think
[03:44] <Ubugtu> An error has occurred.
[03:44] <AlinuxOS> or someone really must rewev it?
[03:44] <bradb> There are big gaps in thoses last few bug #'s
[03:44] <bradb> after 6757
[03:44] <kiko> daf, missing ubuntu-bugs
[03:44] <daf> er, 10030
[03:44] <kiko> guessed that
[03:44] <jamesh> I think the importer has hung on a transaction commit
[03:44] <daf> hmm, desktop-bugs isn't enough?
[03:45] <kiko> daf, no -- distro bug contact?
[03:45] <daf> ok
[03:45] <jamesh> daf: desktop-bugs is a contact for mainly gui stuff
[03:45] <AlinuxOS> carlos, who decides imported .po files destiny? Translators Group Admin, Owner or someone esle?
[03:45] <bradb> jamesh: Is the importer resumable?
[03:45] <carlos> AlinuxOS, Rosetta Experts, that's jordi, daf and me
[03:46] <carlos> AlinuxOS, if we can guess the destination, it's done automatically
[03:46] <jamesh> kiko: set the distro bug contact
[03:46] <jamesh> bradb: yeah.
[03:46] <bradb> jamesh++
[03:46] <carlos> we need to improve the current logic
[03:46] <AlinuxOS> so there is no more automatic.
[03:46] <carlos> AlinuxOS, is automatic
[03:46] <bradb> jamesh: The migration script doesn't send bugmail, right?
[03:46] <carlos> but not always
[03:46] <jamesh> importer seems to have started again
[03:46] <carlos> that lets our users to upload files without the language code as the name of the file
[03:47] <AlinuxOS> carlos, what means destination?
[03:47] <jamesh> I think something else must have been blocking the transaction
[03:47] <carlos> AlinuxOS, language and source package
[03:47] <jamesh> bradb: it disables sendmail(), yes.
[03:47] <carlos> that lets us 'fix' uploads of de_DE instead of de and things like that
[03:47] <jamesh> 92%
[03:47] <AlinuxOS> for example   	 vlc in Ubuntu Dapper   	 ka.po   False
[03:48] <AlinuxOS> why it's stopped?
[03:48] <bradb> kiko: So the bug contact won't get spammed from the migration.
[03:48] <jamesh> no
[03:48] <carlos> that only means that vlc does not have any string for Georgian
[03:48] <AlinuxOS> today I've make some translations... for Dapper pakages collection.
[03:48] <carlos> AlinuxOS, in that case we should improve our current logic to do it automatically
[03:48] <jamesh> I've got Znarl to update the mailing list config too, so that it should accept mails generated by Malone
[03:49] <AlinuxOS> carlos but it works with on line translation.
[03:49] <carlos> AlinuxOS, because you already selected the language with your upload
[03:49] <AlinuxOS> yes of cource
[03:49] <carlos> AlinuxOS, yes
[03:50] <AlinuxOS> so you must approve my todays translation or?
[03:51] <AlinuxOS> for example I translated yesterday 90% of BUM, and today I've finished it... and reuploaded it... but after 2 hours, I've finished it on-line.
[03:51] <AlinuxOS> can we change something with this way of doing?
[03:51] <bradb> 26,700 Malone bugs and counting...!
[03:52] <sd-tux> carlos: my translations are waiting for import too... i'm uploading files always named ka.po and from +lang/ka ..
[03:53] <sd-tux> evolution was uploaded from https://launchpad.net/distros/ubuntu/breezy/+source/evolution/+pots/evolution-2.4/ka/+upload
[03:55] <carlos> AlinuxOS, bum is not waiting for any admin review
[03:55] <carlos> AlinuxOS, if it's not imported, there is a problem with it
[03:55] <carlos> as I said, the reviews are needed only the first time we see that file
[03:56] <carlos> sd-tux, yours need that an admin reviews the import request, I will try to take a look later today.
[03:56] <AlinuxOS> yes but doday I've finished rest of bum...and there was no imports.
[03:57] <sd-tux> carlos: ok
[03:57] <carlos> AlinuxOS, you did the import two hours ago, right?
[03:57] <AlinuxOS> carlos, aha
[03:57] <AlinuxOS> right caros amigos :)
[03:58] <carlos> AlinuxOS, and after that, you did the translations using the web UI?
[03:58] <AlinuxOS> aha
[03:58] <AlinuxOS> :)
[03:59] <carlos> AlinuxOS, Ok, the only thing I can think on is that the poimport script is a bit busy atm, I should get an email soon with the run log
[03:59] <carlos> as the last one I have was sent before you uploaded the file
[03:59] <jamesh> bugzilla importer bailed on one of the bug aliases
[03:59] <AlinuxOS> so I've done everything ina regular mode...I mean not erroneous.
[04:04] <AlinuxOS> carlos, hehe, I can remove my imports :)
[04:04] <bradb> jamesh: Why would an alias cause it to bail?
[04:04] <bradb> oh, validation failure, presumably
[04:04] <jamesh> yeah
[04:05] <kiko> friggin timeouts.. try 3.. jamesh, bradb: still not done.
[04:05] <kiko> RequestExpired: (("SELECT EmailAddress.id, EmailAddress.status, EmailAddress.person, EmailAddress.email FROM EmailAddress WHERE lower(email) =<EMAIL_ADDRESS>ORDER BY email",), {})
[04:05] <kiko> always fails
[04:05] <AlinuxOS> but better is if there is PUT button :)
[04:05] <jamesh> the little alias sanitisation routine didn't catch aliases beginning with a digit
[04:06] <bradb> jamesh: So this should be simple to fix and resume, right?
[04:06] <jamesh> yep
[04:06] <bradb> great
[04:06] <daf> it would happen when it was nearly finished :)
[04:06] <jamesh> It's currently going through and checking which bugs it's already migrated
[04:06] <jamesh> up to ~ 8000
[04:07] <carlos> AlinuxOS, PUT button?
[04:07] <jamesh> it was up to 21391 before
[04:07] <jamesh> out of 21770 bugs
[04:07] <AlinuxOS> :) publishing button :)
[04:07] <carlos> AlinuxOS, ;-)
[04:07] <jamesh> of course, it needs to process the duplicates table after that
[04:08] <jamesh> bradb: one of the Ubuntu guys noticed that the malone 1.1 milestone page was giving forbidden errors
[04:08] <Ubugtu> Malone bug 1: "Microsoft has a majority market share" Fix req. for: Ubuntu, Severity: Critical, Assigned to: Mark Shuttleworth, Status: Confirmed http://launchpad.net/bugs/1
[04:09] <jamesh> bradb: it seems that the page doesn't handle private bugs properly.  I've filed a bug with the details
[04:09] <AlinuxOS> eh I remmember that before a general update, it was really simple to update/import a .po file, that took 5 minutes maximum.
[04:09] <bradb> jamesh: Ah, right, thanks.
[04:10] <jamesh> https://launchpad.net/products/malone/+bug/6751
[04:10] <Ubugtu> Malone bug 6751: "Forbidden error when viewing a milestone with private bugs" Fix req. for: malone (upstream), Severity: Normal, Assigned to: Nobody, Status: Unconfirmed http://launchpad.net/bugs/6751
[04:21] <ddaa> Another question...
[04:22] <ddaa> I would like that when any "well behaved" code sets a branch's title, description or URL to the empty string, what gets actually written to the database is NULL.
[04:22] <ddaa> Where should I do that?
[04:23] <kiko> hmmm.
[04:23] <kiko> you can do it in various places
[04:23] <kiko> I'm unsure which is correct
[04:23] <jamesh> the importer is on to duplicate processing
[04:24] <ddaa> kiko: who would know?
[04:24] <kiko> ddaa, SteveA for sure.
[04:24] <ddaa> SteveA: you here?
[04:24] <SteveA> ddaa: no
[04:24] <ddaa> Is that an answer to "Where should I do that"?
[04:25] <SteveA> no
[04:25] <kiko> good ole SteveA humor
[04:25] <ddaa> SteveA: ddaa: I would like that when any "well behaved" code sets a branch's title, description or URL to the empty string, what gets actually written to the database is NULL.
[04:25] <ddaa> ddaa: Where should I do that?
[04:26] <SteveA> what do you expect things to read after that?
[04:26] <ddaa> Well, NULL, obviously.
[04:26] <SteveA> do you expect to write an empty string, but read a None ?
[04:26] <SteveA> that sounds dodgy to me
[04:26] <SteveA> you could write a property that does that
[04:26] <SteveA> it sounds like misdesign
[04:27] <sivang> hi all
[04:27] <ddaa> I think SQL is misdesigned in that respect.
[04:28] <ddaa> The motivation is that often the empty string and NULL are interchangeable. Forms do not care. Templates do not care. Python, _if written with the right idioms_ does not care.
[04:28] <ddaa> but it's a pain to use in SQL requests and it's error-prone with python code.
[04:28] <SteveA> you can use a property in the database code.  ask stub if it is a good design.
[04:28] <SteveA> i'm not here
[04:29] <ddaa> well... stub isn't either...
[04:30] <kiko> Znarl, jamesh: somehow people are getting ubuntu-bugs spam when filing malone bugs.
[04:30] <seb128> kiko: I've just given the filter rule to jdub
[04:30] <seb128> kiko: but I've bugged you guys for ages about that
[04:30] <seb128> seems you don't want to fix it
[04:31] <kiko> don't want to fix what?
[04:31] <seb128> and prefer blame list admin who have moderation
[04:31] <kiko> bug?
[04:31] <seb128> don't send moderation mails to the user
[04:31] <seb128> you forge the comment like they were sent from the user
[04:31] <jamesh> seb128: I asked Znarl to make the config changes to the lists
[04:31] <seb128> so he gets the moderation mail
[04:31] <kiko> seb128, convince Keybuk of that.
[04:31] <seb128> the user should not have to care
[04:31] <kiko> I am not convinced that your proposal is correct
[04:31] <seb128> he comments on a bug tracker
[04:31] <SteveA> jamesh: did you file an RT request?
[04:32] <jamesh> it should be letting LP emails through to ubuntu-bugs
[04:32] <seb128> whoever is subscriber to launchpad should not be his issue
[04:32] <bradb> lifeless: ping (semi-urgent)
[04:32] <jamesh> SteveA: no.  I asked him on IRC earlier, and he said he did it
[04:32] <seb128> jamesh: jdub is going to change that but that's still an issue
[04:32] <kiko> seb128, if you write email to a list and one of the list subscribers is a moderated mailing list, it's still a problem.
[04:32] <kiko> seb128, but as I said, talk to Keybuk and see if he and you can find a solution which doesn't undo the work we put into the headers.
[04:33] <seb128> kiko: you don't write to a list, you comment on a bug tracker, I don't get why you should be bothered because some people subcribed to the bug with a broken config
[04:33] <jamesh> kiko: the solution at the very bottom of https://wiki.launchpad.canonical.com/BugzillaImportProcess should handle it (this is what I pointed Znarl at)
[04:33] <seb128> it should be between launchpad and the list
[04:33] <seb128> not bounced back to the user who comments on it
[04:33] <bradb> seb128: I agree.
[04:33] <kiko> jamesh, yeah, but doesn't help with what seb128 is complaining about.
[04:34] <kiko> bradb, seb128: how about you two talk to Keybuk.
[04:35] <jamesh> if people ask for information about a particular bug to be sent to them, and then reject said email, it seems like their problem.
[04:35] <bradb> Can anybody else force rocketfuel to get mirrored to chinstrap from whatever the merge machine is? I can't merge status notes as comments because of conflicts, but I can't get at the latest patches.
[04:35] <kiko> bradb, lifeless /was/ looking into that
[04:36] <bradb> Yeah, he said a merge had to land and all would be well. Pretty hard to land a non-trivial merge with 10 patches missing. :/
[04:36] <kiko> bradb, I can send an empty merge request
[04:36] <bradb> kiko: hey, true, that'd be good
[04:37] <bradb> beat pqm at its own game
[04:39] <Keybuk> doesn't Malone send out an "I'm Malone" header with it's emails?
[04:39] <bradb> kiko: Are you sending it, or do you want me to?
[04:40] <kiko> sent already
[04:40] <kiko> Keybuk, it does.
[04:40] <bradb> kiko: thanks
[04:40] <Keybuk> seb128: whitelist that header
[04:41] <Keybuk> I had it just the other day
[04:41] <kiko> Keybuk, is there a good way to avoid bounce mail being sent to the original poster?
[04:41] <Keybuk> ahh, what are you setting the envelope-return-path too
[04:41] <Keybuk> I hadn't yet looked at those, those could be wrong
[04:42] <Keybuk> the envelope should have a return-path of something like<EMAIL_ADDRESS>[04:42] <Keybuk> Return-Path<EMAIL_ADDRESS>[04:42] <Keybuk> ^ just like it does
[04:42] <Keybuk> hmm, bounces shouldn't go to the original poster :p
[04:42] <Keybuk> unless there's buggy software
[04:42] <kiko> right. so why is mailman bouncing to the OP?
[04:42] <Keybuk> mailman is fucked ;)
[04:43] <LarstiQ> Keybuk: unfuck it?
[04:43] <Keybuk> the "post to a moderated list" mails, yeah it knowingly ignores Sender for those
[04:43] <Keybuk> cf. same discussion for debbugs years ago
[04:44] <Keybuk> mailman's justification is that those aren't really "bounces"
[04:44] <kiko> Keybuk, no option to fix that?
[04:44] <seb128> Keybuk: it's done
[04:45] <Keybuk> seb128: then what's the problem?
[04:45] <bradb> kiko: I don't see a merge request in pqm's queue. did it have a tag?
[04:45] <seb128> Keybuk: it's that even with a broken list config the luser who use malone should not be bothered by an obscur moderation mail which should be an internal launchpad detail for him
[04:46] <seb128> Keybuk: the user who do reply to a comment doesn't care than motu list is misconfigured
[04:46] <Keybuk> seb128: this is a long-running argument about how mailing list managers should behave
[04:46] <Keybuk> seb128: otoh, users subscribed to that list and receiving the bugs probably do care about the bug information
[04:47] <seb128> list admin does care
[04:47] <seb128> luser using malone doesn't
[04:47] <Keybuk> so?
[04:47] <Keybuk> fix mailman
[04:47] <Keybuk> malone is sending e-mails out entirely correctly
[04:47] <Keybuk> it asks for bounces to be sent to<EMAIL_ADDRESS>[04:47] <seb128> malone is sending mails like they were sent to the list by the commenter
[04:47] <Keybuk> and identifies itself in the Sender: header (as specified in the RFC) as the real originator of the e-mail
[04:47] <Keybuk> damned right
[04:48] <kiko> bradb, hmmm. but I sent it.
[04:48] <seb128> the guy comment on malone, it doesn't send a mail to the list
[04:48] <Keybuk> and it isn't
[04:48] <seb128> the Sender should be malone
[04:48] <Keybuk> it's sending mails like they were sent by Malone on behalf of the commenter
[04:48] <LarstiQ> seb128: aiuK, it is
[04:48] <daf> isn't this exactly what happens with debbugs and debian-bugs-dist?
[04:48] <kiko> daf, yes.
[04:49] <Keybuk> Sender should probably not be<EMAIL_ADDRESS>but something more descriptively Malone, but that's not truly important
[04:49] <Keybuk> the general mailing list trick is a catch-all address, so you have foo-bounces and foo-owner which go to the same place
[04:49] <Keybuk> daf: and most of the mailman hosted commit lists too
[04:49] <Keybuk> including, amusingly, mailman's own commit list :p
[04:50] <Keybuk> which was the time I saw mailman closest to actually getting fixed
[04:50] <kiko> Keybuk, can't they be pursued to adding an option?
[04:50] <kiko> that would be less terrible but would still inconvenience us
[04:50] <kiko> (given not all lists would be ported over to this new version, and have the option activated..)
[04:51] <kiko> Keybuk, mind you, I have a patch on mailman that I've kept up to date for 2 YEARS
[04:51] <kiko> nobody's ever even replied to my nagging
[04:51] <kiko> and this, because I know barry fairly well
[04:51] <Keybuk> kiko: *shrug* if a sysadmin can change the option, they can add the appropriate white list
[04:51] <kiko> I guess.
[04:52] <Keybuk> badly configured mailing lists generate hate, News At Eleven
[04:52] <jamesh> okay.  The main migration is done
[04:53] <seb128> rocl
[04:53] <seb128> rock
[04:53] <jamesh> what I haven't done is go through and make sure ubuntu-bugs is subscribed to all the ubuntu bugs
[04:53] <seb128> "1   20  of 689 results", oh joy
[04:53] <seb128> (Bugs Assigned)
[04:53] <bradb> jamesh: We have to do that for all Launchpad products, bzr, and possibly other things too.
[04:54] <Keybuk> jamesh: only the "main" ones, no?
[04:54] <Keybuk> ubuntu-bugs would be mad if it had universe too
[04:54] <Keybuk> but then maybe mdz has other ideas
[04:54] <bradb> Keybuk: All of them.
[04:54] <seb128> grumpf
[04:54] <seb128> upstream bugs are "unconfirmed"
[04:54] <seb128> grumpf
[04:55] <Keybuk> I can't keep up with ubuntu-bugs as it is :-/
[04:55] <bradb> InitialBugContacts notes that we'll add a Keywords header, to create Mailman topics for universe, main, etc.
[04:55] <bradb> I haven't implemented it yet, but I can do it quickly enough. Unfortunately, pqm's a pretty thick brick wall to get through today.
[04:57] <seb128> carlos: is https://launchpad.net/people/ubuntu-l10n-fr/+members/<name> returning a "Page not found" known?
[04:57] <Keybuk> bradb: Oh, btw, without a way to search for nicknames I ended up not using them
[04:58] <bradb> Keybuk: ok. will you switch to using them once we have a search and/or URL that works with nicknames?
[04:59] <Keybuk> yeah I guess
[04:59] <Keybuk> I suspect you'll get bored of MoM DoS'ing launchpad once a day <g>
[04:59] <bradb> heh
[05:02] <bradb> kiko: I put an empty merge request in pqm's queue. Not sure what happened to the one you sent.
[05:04] <spacey_ki> hi
[05:04] <carlos> seb128, I'm not aware that such url ever exists....
[05:04] <spacey_ki> got a mail from launchpad about https://launchpad.net/distros/ubuntu/+source/installation-guide/+bug/4637
[05:04] <Ubugtu> Malone bug 4637: "guide (Ubuntu) - Partition sizes wrong in 5.10 Ubuntu Installation Guide " Fix req. for: Ubuntu, Severity: Minor, Assigned to: Nobody, Status: Rejected http://launchpad.net/bugs/4637
[05:04] <spacey_ki> but i'm not subscribed to it
[05:05] <carlos> seb128, the list of members links to people/<name>
[05:05] <spacey_ki> why is that?:P
[05:05] <seb128> carlos: that's the URL I get with the "Launchpad: New member awaiting approval." mails
[05:05] <carlos> hmm
[05:05] <seb128> carlos: I click on the url from  the mail, get this error page, and have to click on 10 links to find where to moderate people
[05:05] <seb128> that's not optimal :)
[05:05] <seb128> should I file a bug?
[05:06] <seb128> "This is the page where you can approve or decline this membership:
[05:06] <seb128> https://launchpad.net/people/ubuntu-l10n-fr/+members/cblanquer"
[05:06] <seb128> that's the mail I just got
[05:07] <carlos> seb128, yes, please, file a bug
[05:07] <carlos> seb128, since when do you have this problem?
[05:07] <seb128> carlos: some weeks
[05:08] <jamesh> spacey_ki: according to the bug activity log, that bug was once assigned to the "ubuntu-doc" team
[05:08] <carlos> I suppose someone changed it and we are missing a test....
[05:08] <spacey_ki> hmm
[05:08] <seb128> carlos: I tend to think that such issue are noticed quickly so I just waited a bit before spending time to bother you guys :p
[05:08] <jamesh> spacey_ki: are you on that team? (or a team that is a member of ubuntu-doc?)
[05:09] <jamesh> "edubuntu documentation" and "wiki team" are listed as members of ubuntu-doc
[05:09] <spacey_ki> must be because of edubuntu documentation then
[05:09] <spacey_ki> ok, that explains
[05:10] <spacey_ki> not really obvious
[05:10] <spacey_ki> :D
[05:11] <spacey_ki> maybe the mail can say: ps. you got this mail because this bug was once assigned to ubuntu documentation team, and you are in edubuntu documentation team, and they are linked, so you get this mail. :p
[05:11] <seb128> carlos: https://launchpad.net/products/rosetta/+bug/28457
[05:11] <Ubugtu> Malone bug 28457: ""New member awaiting approval" URL broken" Fix req. for: rosetta (upstream), Severity: Normal, Assigned to: Nobody, Status: Unconfirmed http://launchpad.net/bugs/28457
[05:14] <jamesh> kiko: do we want http://bugzilla.ubuntu.com/ to redirect, or to just have an explanation of the change?
[05:15] <kiko> I think an explanation may be less traumatic
[05:18] <jamesh> where should we point people to?
[05:18] <kiko> to the various malone pages that the users need to interact with
[05:18] <jamesh> so probably /distros/ubuntu/+bugs
[05:18] <dilys> Merge to devel/launchpad: [trivial]  empty merge to, hopefully, (r2993)
[05:20] <carlos> seb128, thanks
[05:20] <seb128> carlos: np
[05:20] <carlos> seb128, well, if there isn't people complaining... we cannot detect it ;-)
[05:20] <carlos> seb128, well, we can, if we have enough tests ;-)
[05:21] <seb128> carlos: I thought than somebody would complain and I could just be lazy :)
[05:21] <seb128> seems that I'm not the only lazy guy around :p
[05:21] <carlos> seb128, ;-)
[05:32] <jamesh> bradb: so, do you want me to subscribe all the ubuntu bugs to ubuntu-bugs?
[05:33] <bradb> jamesh: Sure, that'd be great.
[05:33] <kiko> please!
[05:33] <kiko> and all launchpad-related bugs, too, jamesh
[05:35] <jamesh> kiko: could you come up with some wording to stick on the bugzilla frontpage?
[05:36] <kiko> jamesh, yes, give me 5 minutes because I'm on the phone with SteveA
[05:36] <jamesh> sure
[05:41] <kiko> Keybuk, would bug rdf help you?
[05:41] <Keybuk> rdf is harder to drive than beautiful soup, so no :p
[05:42] <kiko> jamesh, back
[05:42] <kiko> Keybuk, more stable than html though
[05:43] <Keybuk> if the form changed, it'd break posting as well as getting
[05:43] <Keybuk> so doesn't make much difference
[05:43] <kiko> Keybuk, well, I was suggesting using the email interface.
[05:43] <Keybuk> the email interface doesn't report bug
[05:44] <Keybuk> uh, report back
[05:44] <kiko> so you'd need to  read the rdf, and post mail
[05:44] <kiko> isn't that a nicer way to do it?
[05:44] <Keybuk> not especially
[05:44] <Keybuk> about the same ickyness
[05:44] <Keybuk> xml-rpc is worth the coding effort
[05:45] <kiko> jamesh, how about "Ubuntu Linux has moved to [Malone]  for bug management and reporting. This Bugzilla instance is still available for viewing bugs, but not changing bugs; logins are accordingly disabled." and then a set of <li>s that explain to people how to do the stuff they did in bugzilla in malone, perhaps following the intent of the existing bugzilla links.
[05:46] <kiko> or moved to using Malone
[05:47] <kiko> jamesh?
[05:47] <jamesh> kiko: sounds good
[05:47] <kiko> jamesh, did you pick up my request for updating the launchpad bugs with the bug contacts as well?
[05:49] <kiko> and can we declare the migration done once those are done?
[05:50] <jamesh> kiko: yeah, I haven't done that yet though (it is still chugging through the 20000 ubuntu bugs)
[05:50] <kiko> jamesh, and you managed to update the bug contact, good for you
[05:51] <kiko> 10 times
[05:51] <kiko> jamesh, I was considering having lunch, what do you think about that?
[05:52] <sivang> kiko: are you able to say breifly why steps (1) and (2) of BugzillaImportProcess are needed to be able to migrate ubuntu's main to malone? (from what I recall about gina, I don't understand how these 2 are connected, although I admit I may need to read the bacgkround about (2) to understand)
[05:53] <kiko> sivang, well, you want the source package names to be continually created in launchpad as they are invented on the package side.
[05:53] <jamesh> kiko: https://chinstrap.ubuntu.com/~dsilvers/paste/fileKESakU.html <- does that look good?
[05:53] <kiko> otherwise universe and main people get fucked over when they create new packages.
[05:54] <kiko> jamesh, I think we need to add some sort of header to suggest the <li>s actually refer to malone and are not leftovers. perhaps "<h1>Ubuntu bugs have moved</h1>" and "<h2>Links to Ubuntu bugs in Malone</h2>"
[05:55] <SteveA> kiko: the venue is booked, the dates are set
[05:55] <kiko> SteveA, crack the champagne
[05:56] <SteveA> working days: 13 - 24 March.  location same as DistroSprintLondon2006 on the canonical wiki
[05:56] <kiko> yay
[05:57] <sivang> kiko: ah right. you must have the knowledge about the source packags before you're supposed to file bugs on them. Still, so gina must have been running already for universe right? otherwise we wouldn't have been able to report bugs against packages in universe.
[05:57] <kiko> sivang, no, people complained to me in practice
[05:59] <sivang> kiko: I see, good that you had universe to practice gina on then :-)
[05:59] <kiko> heh
[05:59] <SteveA> i'll send a brief mail to the list
[06:05] <kiko> so jamesh, how's it going?
[06:09] <jamesh> kiko: Znarl's updated the front page, and ubuntu-bugs is subscribed to all the existing bugs
[06:10] <jamesh> I haven't done the LP bugs yet
[06:10] <kiko> jamesh, thanks.
[06:11] <kiko> are you okay with me having lunch for a bit?
[06:11] <kiko> ah, I'll just take my laptop
[06:13] <mantiena-baltix> Hi all
[06:15] <mantiena-baltix> SteveA, labas :)
[06:16] <SteveA> labas mantai
[06:18] <seb128> is it possible to not mail all the member of a team on bug changes by example, but just a list?
[06:18] <jamesh> seb128: yes.  Set an email address for the team
[06:18] <seb128> we already do
[06:19] <seb128> the list is mailed
[06:19] <seb128> and all the members are mailed
[06:19] <jamesh> which team?
[06:19] <seb128> GNOME Team
[06:19] <jamesh> URL?
[06:19] <seb128> https://launchpad.net/people/gnome
[06:20] <jamesh> okay.  The launchpad team is now a subscriber for all bugs filed against products that are part of the launchpad project
[06:20] <jamesh> seb128: there is no email address set for that team
[06:21] <seb128> oh, I though dholbach did that, sorry
[06:21] <jamesh> seb128: you might want to ask dholbach to add a few more people as admins to the team, so they can make changes like that (and add new members)
[06:23] <sivang> jamesh: so this way we get bugmail for new bugs opened, but not for changes in bugs?
[06:23] <kiko> back at this lunch place
[06:23] <kiko> how's it going jamesh?
[06:24] <mantiena-baltix> SteveA, how are you feeling after new year celebration ? ;)
[06:25] <jamesh> kiko: all bugs for products in the LP project now have "launchpad" as a subscriber
[06:25] <jamesh> kiko: we just need to send the mail to ubuntu-announce, and I can go to sleep
[06:25] <kiko> jamesh, I can send the email announcement if you like.
[06:25] <kiko> is there anything I should cover?
[06:25] <seb128_> sorry I got disconnect
[06:25] <seb128_> if somebody said something after "<seb128> maybe a launchpad guy can do that? :p" please say it again :)
[06:25] <kiko> (anything apart from what's on the wikipage?)
[06:25] <kiko> what were you talking about seb128_?
[06:26] <jamesh> I can't think of anything in particular
[06:26] <kiko> jamesh, I'll do it for you then no worries if you like
[06:26] <seb128_> kiko: setting me as admin of the people/gnome team (seems that dholbach is no around atm and I would like to change the list stuff)
[06:27] <kiko> one sec
[06:27] <seb128_> thank you
[06:29] <jamesh> seb128_: note that after the migration, there is now also a "desktop-bugs" team
[06:29] <seb128_> jamesh: right, I've noticed, interesting case :)
[06:29] <kiko> I'll fix seb128 to be an admin of both
[06:29] <seb128_> cool, thanks
[06:30] <seb128_> they kind of overlap
[06:30] <kiko> seb128_, you could merge..
[06:30] <kiko> stub!
[06:30] <stub> Yo
[06:32] <kiko> how's it going man
[06:33] <stub> Just checking in to confirm the Bugzilla migration worked. Looks like it. 28k+ bugs!
[06:33] <bradb> indeed. fti still seems broken though.
[06:33] <bradb> "migration" still not finding bug 6610
[06:33] <bradb> er, "maintained" i mean.
[06:34] <stub> I fixed the triggers (I hope), but didn't rebuild the indexes. So some bugs have invalid indexes. All the newly imported bugs should be fine though.
[06:34] <bradb> ah, ok
[06:34] <stub> I'll knock up a short script to rebuild the indexes without downtime
[06:35] <bradb> awesome, thanks
[06:35] <stub> (Just needs to update every row, but nicely without locking stuff)
[06:36] <mantiena-baltix> SteveA, sleeping ? ;)
[06:38] <sivang> bradb: fti= ?
[06:38] <bradb> full text index
[06:38] <sivang> ah, thanks :)
[06:39] <bradb> kiko: Is there any point in prioritizing an alias email command now, given that it won't really help Keybuk?
[06:43] <Keybuk> kiko: don't suppose we can get your clever Bug#28463 bot into #ubuntu-devel ?
[06:43] <Keybuk> or does that not work anymore?
[06:43] <SteveA> mantiena-baltix: not sleeping.  not in vilnius either.  i'm at a series of company meetings in london.
[06:44] <SteveA> stub: do you still have that patch i did to make medusa fail in a way that pound understands?
[06:44] <stub> Hmm... maybe...
[06:45] <SteveA> i think we should look at this, as apparently a launchpad process had problems today to do with an unclean restart
[06:45] <SteveA> and pound was sometimes sending requests to a b0rked launchpad process
[06:46] <kiko> bradb, I guess not :-(
[06:46] <matsubara> bradb: does that empty merge request worked? I mean, does it reactivated the mirroring of rf on chinstrap?
[06:47] <kiko> Keybuk, Ubugtu does that for you
[06:47] <bradb> matsubara: I hope so, but I think it'll be a little while yet until we find out.
[06:47] <stub> SteveA: I've bounced two emails containing the code back to you. I can't remember how successful we were though.
[06:48] <bradb> matsubara: Ah yes, it looks like it works. The merge mail hit arch-commits, so it's probably doing the chinstrap mirroring now.
[06:48] <stub> SteveA: If I can just to Z3.2 though we can use twisted which might be easier for us to work with?
[06:48] <matsubara> bradb: do you know how long does it take to the mirror thing fully happen?
[06:48] <bradb> matsubara: Too long. :)
[06:49] <bradb> matsubara: Then there's a lag time in it building rocketfuel-built
[06:50] <jamesh> doesn't look like the branch under /home/warthogs/archives has been updated
[06:51] <matsubara> bradb: I see. It seems I'll have to wait a while until my prebuilt mirror here on async gets updated. but no problem. thanks.
[06:51] <bradb> The patch is still sitting in the queue, so it's not done mirroring yet.
[06:53] <jamesh> look at all the karma this guy will get: https://launchpad.net/people/bugzilla-importer/+karma :)
[06:54] <stub> SteveA: We also no longer need server affinity, so we can switch to other load balancing technologies if they work better in these situations. I suspect they would all deal with this situation the same way though :-/
[06:55] <mantiena-baltix> SteveA, do you have some time to help me register Baltix distribution in Launchpad.net ? Currently Baltix uses roundup at akl.lt for bugs and tasks, but I need more features, than roundup can offer, it seems launchpad has most needed features, but I can't register Baltix distro at launchpad - I get an error, than I don't have permissions :(
[06:56] <SteveA> stub: twisted is still flaky with zope3
[06:56] <SteveA> stub: i think we had it working, experimentally
[06:57] <SteveA> mantiena-baltix: i'd love you to be using launchpad for Baltix.
[06:57] <SteveA> kiko: can you help out mantiena-baltix with registering this ubuntu derivative in launchpad?
[07:01] <kiko> SteveA, sure.
[07:01] <kiko> mantiena-baltix, can you give me a few minutes?
[07:01] <kiko> I am eating this delicious aa and the experience will be ruined by web-interaction
[07:01] <SteveA> oh man... i had some aa in montreal
[07:02] <SteveA> but it wasn't the same as it fresh from brazil
[07:04] <seb128> workflow question
[07:04] <kiko> the wonders of aai
[07:04] <kiko> what it can do to a man
[07:04] <sivang> kiko: what is it? :)
[07:04] <kiko> sivang, only google can answer that
[07:04] <seb128> what is the interest to have an upstream task rather than putting a watch on a distro task?
[07:04] <kiko> seb128, okay.
[07:04] <kiko> an upstream task is mainly useful if upstream uses malone
[07:05] <seb128> I'm tempted to just close upstream task
[07:05] <kiko> a watch is useful if upstream uses something else
[07:05] <seb128> and to set a watch on the distro bug
[07:05] <kiko> but
[07:05] <seb128> what I though
[07:05] <kiko> you can have the upstream task linked to a bug watch
[07:05] <seb128> yeah, I do that
[07:05] <kiko> and in that case you can track the upstream work separately
[07:05] <seb128> basically I've the upstream task beeing a dup of the distro one
[07:05] <kiko> that's not entirely correct though
[07:05] <seb128> I set the watch as linked to both
[07:06] <kiko> because you still need to do packaging when the upstream bug closes
[07:06] <seb128> but that's seems just a pure duplicate to me
[07:06] <kiko> each task is an actual task
[07:06] <seb128> yeah, but the watch as the status
[07:06] <seb128> s/as/has/
[07:06] <kiko> so upstream task closes when upstream fixes bug
[07:06] <seb128> it's automatic?
[07:06] <kiko> and your bug closes when you package upstream
[07:06] <kiko> seb128, it will be soon
[07:06] <seb128> hum
[07:06] <seb128> if I link a distro bug to a bugzilla.gnome.bug
[07:07] <seb128> will it be closed automatically when upstream close it?
[07:07] <kiko> then it will close
[07:07] <kiko> right
[07:07] <seb128> DOH
[07:07] <seb128> I just borked all the rhythmbox bugs we have
[07:07] <seb128> grumpf
[07:08] <seb128> BTW why do we have both status
[07:08] <seb128> fixed released and fix commited?
[07:08] <seb128> s/fixed/fix
[07:08] <kiko> fix committed -- fix in RCS
[07:08] <kiko> fix released -- version released with fix
[07:08] <seb128> that's duplication with the upstream task too
[07:08] <kiko> so fix committed is like your pending upload
[07:08] <kiko> how so?
[07:08] <seb128> I've the feeling to have the same information 3 times
[07:08] <seb128> because you have an upstream task
[07:08] <seb128> it's fixed
[07:08] <seb128> that's == fixed released
[07:09] <seb128> no?
[07:09] <kiko> maybe
[07:09] <kiko> do you use upstream releases or cvs/svn tip?
[07:09] <seb128> cvs/svn
[07:09] <kiko> fix committed then
[07:09] <kiko> upstream -> fix committed
[07:09] <kiko> then you package
[07:09] <kiko> do you keep your packages in RCS?
[07:10] <seb128> no
[07:10] <kiko> then you will probably go straight from in progress to fix released
[07:10] <kiko> unless you want to use fix committed to suggest pending upload
[07:10] <seb128> no, upstream task fixed already suggest that
[07:10] <seb128> and the watch already say so too
[07:10] <kiko> the watch and the upstream task when linked should have the same status
[07:11] <kiko> that they don't is a bug
[07:11] <seb128> how often are the watch updated?
[07:11] <kiko> anyway
[07:11] <kiko> I'm walking back to the office
[07:11] <kiko> hmmm
[07:11] <kiko> I think once every few hours
[07:11] <kiko> stub will know
[07:11] <seb128> k
[07:11] <stub> every day at the moment
[07:11] <seb128> thanks for the comments kiko :)
[07:12] <seb128> did you guy adress #6667
[07:12] <seb128> seems not
[07:12] <seb128> that will make GNOME guys unhappy ...
[07:12] <mantiena-baltix> kiko-afk, when you will have time to register Ubuntu-based Baltix distribution at http://launchpad.net/distros/+add ?
[07:13] <seb128> if you DoS bugzilla.gnome daily we are not going to make friends there
[07:13] <SteveA> mantiena-baltix, kiko-afk: i have a small break in the meetings.  i'll do it now
[07:13] <stub> seb128: Worth me switching off the remote bug monitoring code until it is sorted? I don't think anyone has seriously looked at that code since Dave Miller wrote it.
[07:13] <SteveA> mantiena-baltix: what is a one sentence summary of the baltix distro?
[07:14] <seb128> stub: bugzilla.gnome admin asked we fix that before doing the import, so I would say it would be nice to stop it time to sort that yep
[07:14] <SteveA> mantiena-baltix: what is the domain name?
[07:15] <SteveA> mantiena-baltix: also, have you created a team for the distro?
[07:15] <mantiena-baltix> SteveA, for baltix info in english look at http://baltix.akl.lt
[07:15] <bradb> daf: Why did you mark bug 2230 as fixed?
[07:16] <Pak|tO> hello
[07:16] <Pak|tO> some one
[07:16] <bradb> hi Pak|tO
[07:16] <Pak|tO> i dont speak a good english
[07:16] <Pak|tO> :P
[07:16] <SteveA> mantiena-baltix: okay.  do you have a team for members of the distro?
[07:16] <Pak|tO>  i'm portuguese
[07:16] <mantiena-baltix> SteveA, I didn't created baltix-devel team, I thought, that baltix distro should be registered at first ;)
[07:17] <Pak|tO> sorry
[07:17] <bradb> Pak|tO: We have pt_BR speakers in here
[07:17] <daf> bradb: I thought +sources didn't exist
[07:17] <daf> bradb: I fixed for +source
[07:17] <SteveA> mantiena-baltix: i'm asked for a members team when setting the distro up
[07:17] <Pak|tO> ytkx
[07:17] <mantiena-baltix> SteveA, but if I need to create a devel team at first, then I can to this in few minutes ;)
[07:17] <bradb> daf: Yeah, the bug is that +sources doesn't exist :)
[07:17] <Pak|tO>  yi have a question
[07:17] <daf> bradb: is it linked from anywhere?
[07:17] <SteveA> mantiena-baltix: ok
[07:17] <Pak|tO>  aboute ubuntu
[07:17] <Pak|tO>  :s
[07:17] <daf> bradb: is there anything under +sources?
[07:18] <bradb> daf: No, that's the bug.
[07:18] <Pak|tO> (my fuck english... rrr)
[07:18] <daf> bradb: how is a user going to get to +sources?
[07:18] <bradb> It is (or at least very recently was) the most common 404 in Launchpad.
[07:18] <Pak|tO> aaa
[07:18] <daf> bradb: I can see how they might get to +source
[07:18] <Pak|tO> now i'm downloading dapper
[07:19] <bradb> daf: I don't know off-hand if there's a link, but from reading the 404 reports, it was the most common exception in Launchpad.
[07:19] <bradb> daf: If nothing else, one would expect that they should be able to hand-hack it.
[07:19] <daf> if we're still getting 404s for it
[07:19] <daf> then I will add a redirect for +sources
[07:19] <mantiena-baltix> SteveA, so,  should I create a baltix-devel team in launchpad at first ?
[07:19] <SteveA> mantiena-baltix: yes
[07:19] <Pak|tO> but some one can tellme why dapper?
[07:19] <daf> I don't think it's likely any longer that you get to +sources by hand-hacking
[07:19] <daf> e.g. if you go up from https://launchpad.net/distros/ubuntu/+source/nautilus, you get to +source, not +sources
[07:20] <bradb> daf: Sure. But just noting that the bug is that it should present something useful, e.g., a package source and/or package overview, etc.
[07:20] <Keybuk> bradb: malone 28465 ... wtf?!
[07:20] <Ubugtu> Malone bug 28465: "New changes from Debian require merging" Fix req. for: cdebconf (Ubuntu), Severity: Normal, Assigned to: Nobody, Status: Unconfirmed http://launchpad.net/bugs/28465
[07:20] <daf> bradb: this is the fix that Steve and I agreed on
[07:20] <bradb> Keybuk: ?
[07:21] <Keybuk> bradb: "This bug has not yet been reported in Ubuntu" ...
[07:21] <Keybuk> "Fix Requested In: cdebconf (Ubuntu)"
[07:21] <bradb> Keybuk: What URL are you looking at exactly?
[07:21] <Keybuk> https://launchpad.net/distros/ubuntu/+bug/28465
[07:21] <Ubugtu> Malone bug 28465: "New changes from Debian require merging" Fix req. for: Ubuntu, Severity: Normal, Assigned to: Nobody, Status: Unconfirmed http://launchpad.net/bugs/28465
[07:21] <bradb> Keybuk: How did you get there?
[07:22] <Keybuk> from the redirector
[07:22] <Keybuk> or maybe it was just Burgundavia being odd
[07:22] <bradb> Must be Burgundavia
[07:22] <bradb> The redirector takes you to the right page
[07:23] <bradb> Malone's just being stoopid though. It shouldn't give that "not yet reported in Ubuntu" error when it's reported on an Ubuntu task.
[07:24] <mdz> bradb: are you prepared for the incoming feature requests?
[07:24] <bradb> Keybuk: The intended purpose of the "not yet reported in..." message is to make it easy to say "this bug exists in Ubuntu" when, in Malone, it might have only been reported upstream to that point.
[07:25] <bradb> mdz: Sure.
[07:25] <mdz> bradb: do you already have something about being able to add a comment and change the bug status in one step?  I think that may have been part of the work you did around the number of clicks/pages for common operations
[07:26] <bradb> daf: Sure, whatever fix you agreed upon is probably the right one. Do you want take bug 2230 then?
[07:26] <bradb> mdz: I'm landing that today, if pqm lets me.
[07:26] <SteveA> Pak|tO: "dapper" is the code-name for the next ubuntu release.  You can ask questions about that on #ubuntu.
[07:26] <bradb> mdz: The patch is written though.
[07:26] <mdz> bradb: you are my hero
[07:26] <bradb> :P
[07:27] <jbailey> How do I make https://launchpad.net/people/jbailey/+packages actually show the package that I care about?  Do I need to find the package in the distro and subscribe?
[07:28] <bradb> jbailey: What defines a package that you care about?
[07:28] <kiko-fud> jbailey, that's a good question. I don't think there's a UI that lists package bug contacts
[07:28] <jbailey> bradb: glibc at this point. =)
[07:28] <mantiena-baltix> SteveA, what you think, which name would better for a members team? maybe baltix-devel or better would be simply baltix ?
[07:28] <bradb> jbailey: There's bug 6610, if that's what you're getting at.
[07:29] <SteveA> mantiena-baltix: baltix-devel seems good to me
[07:29] <SteveA> you can change the name later
[07:29] <jbailey> bradb: I'm not thinking in general at this point. =)  More that there's a list of packages that looks almost like the list of packages I care about, but is in severe need of tweaking (I would drop initramfs-tools from it)
[07:30] <jbailey> kiko: That might be it, I don't really know.  I'm just trying to figure out whether or not my bugs have made it from bugzilla to malone correctly.
[07:30] <jbailey> Usually in bugz I'd look at bugs that were assigned to me.
[07:31] <mantiena-baltix> SteveA, for ubuntu distro there is ubuntumembers team, then maybe baltixmembers ? ;)
[07:31] <jbailey> Oh, I got confused I see.
[07:31] <bradb> kiko: I should probably priortize the bug contacts report over keywords?
[07:31] <jbailey> I thought that I had clicked on bugs to see that list of packages, apparnetly not.
[07:31] <kiko> bradb, given it's simpler to do, I think so, yes.
[07:31] <bradb> ok.
[07:32] <bradb> That's the only thing I had left, priority-wise, because jamesh added the Cc'd stuff, so I'll start that now.
[07:32] <kiko> great.
[07:33] <SteveA> mantiena-baltix: sure
[07:39] <SteveA> mantiena-baltix: a laukiu...
[07:40] <mantiena-baltix> SteveA, I'm registering baltix-members team, but don't understand what are "Number of days a subscribtion lasts" and "Number of days a renewed subscribtion lasts" :(((
[07:40] <mantiena-baltix> SteveA, maybe I should talk with you in Lithuanian ? It would be easier to me ;)
[07:40] <kiko> mantiena-baltix, if you want subscriptions to expire.
[07:42] <daf> bradb: taken
[07:42] <SteveA> mantiena-baltix: i would try to write, but maybe it would not make sense :-)
[07:42] <bradb> daf: thanks
[07:43] <SteveA> mantiena-baltix: in ubuntu, members of certain ubuntu councils are members for 1 year
[07:43] <mantiena-baltix> kiko, what subscriptions ? There are no explanations what are subscriptions and renewed subscribtions :(
[07:44] <kiko> mantiena-baltix, okay. so people can request membership to your team
[07:45] <kiko> you can /optionally/ allow them to unsubscribe
[07:45] <kiko> sorry
[07:45] <kiko> you can /optionally/ allow them to be automatically unsubscribed after a period of time
[07:45] <kiko> if you don't know what they are, you shouldn't worry too much
[07:47] <mantiena-baltix> kiko, SteveA: I set subscriptions to 999 days and renewed subscribtions to 0 ;)
[07:48] <mantiena-baltix> kiko, SteveA: there are some troubles with registering team - I set email adress to my email -<EMAIL_ADDRESS>but got an error -<EMAIL_ADDRESS>is already taken :(
[07:49] <kiko> mantiena-baltix, if you don't want to, don't set a contact email for the team
[07:49] <mantiena-baltix> maybe this is because I've registered user mantas with email<EMAIL_ADDRESS>in launchpad ?
[07:50] <mantiena-baltix> kiko, I want to set contact email or mailing list email for baltix-members team, I think can use different email -<EMAIL_ADDRESS>;)
[07:51] <kiko> if you don't set a contact email all members will be mailed
[07:54] <mantiena-baltix> kiko, I've read this in new team creation page ;)
[07:55] <mantiena-baltix> SteveA, kiko: so, I've registered baltix-members team, what other steps I need to do for creating new distribution in launchpad ?
[07:55] <SteveA> https://launchpad.net/distros/baltix
[07:56] <SteveA> mantiena-baltix: what is your own name in launchpad?
[07:57] <Keybuk> hmm
[07:57] <Keybuk> how do you merge accounts?
[07:57] <Keybuk> I can't see it
[07:57] <SteveA> https://launchpad.net/people
[07:57] <SteveA> see link in body text
[07:57] <Keybuk> ah, I was looking directly at my dupe
[07:57] <SteveA> we should have "merge accounts" in the RHS of the "site map" for https://launchpad.net/people
[07:58] <Keybuk> hmm
[07:58] <Keybuk> I don't understand
[07:58] <Keybuk> it tells me to login as the duplicated account
[07:58] <Keybuk> then enter the duplicated account
[07:59] <kiko> no
[07:59] <kiko> log in as yourself
[07:59] <kiko> say what account is the dupe
[07:59] <kiko> it will generate an email
[07:59] <kiko> you follow that
[07:59] <kiko> presto
[07:59] <SteveA>  To merge two Launchpad accounts, you must be logged in with access to the e-mail address registered in the duplicated account.
[07:59] <SteveA> the "with" as a conjunction is confusing
[07:59] <Keybuk> that text *SO* needs fixing
[07:59] <SteveA> it should say "you must be logged in, and you must have access to the e-mail ..."
[08:00] <Keybuk> it should say who you should be logged in *as*
[08:00] <Keybuk> and it certainly shouldn't give me OOPS-13B315. :p
[08:00] <SteveA> indeed
[08:00] <SteveA> Keybuk: file bug please
[08:01] <Keybuk> ok
[08:01] <mantiena-baltix> SteveA, mantas ;)
[08:01] <Keybuk> so can I get that merge done manually?
[08:01] <Keybuk> because I can't actually access any of the migrated bugs :)
[08:01] <sivang> Keybuk: would you CC me on this bug report? (for the text change, that is ;-)
[08:01] <SteveA> https://launchpad.net/distros/baltix/
[08:01] <SteveA> you are now the "registrant"
[08:02] <SteveA> Keybuk: yes, mail the launchpad list with the OOPS id
[08:02] <SteveA> and stu will look at it tomorrow i expect
[08:02] <SteveA> or next working day
[08:02] <SteveA> or whatever
[08:03] <Keybuk> SteveA: filed a bug with it
[08:03] <Keybuk> sivang: you have no account, apparently
[08:03] <Keybuk> at least, searching for "sivang" gives me nothing
[08:03] <Keybuk> ah, sivan
[08:03] <Keybuk> that works
[08:04] <Keybuk> SteveA: uhhhhhh
[08:05] <Keybuk> it's got rid of the account I was trying to merge
[08:05] <Keybuk> but hasn't merged it
[08:05] <Keybuk> heeeeeelp!
[08:05] <sivang> Keybuk: thanks, yes , when I noticed I can have my name without the surename specifier, I went for it :)
[08:06] <mantiena-baltix> SteveA, than you very much
[08:06] <Keybuk> oh, maybe it did merge it
[08:06] <seb128> kiko: ping?
[08:07] <mantiena-baltix> I have some troubles with adding packages to the distribution. For example baltix has live-installer package, which doesn't exist in ubuntu, but is registered at lauchpad (http://lauchpad.net/products/live-installer )
[08:14] <Keybuk> https://launchpad.net/people/keybuk/+packages
[08:14] <Keybuk> ^ 0 Bugs in every column
[08:14] <Keybuk> (also the ordering seems manic)
[08:15] <mantiena-baltix> SteveA, s/than/thank
[08:15] <Keybuk> should Ubuntu's Release Date *really* be "When it's done" ?!
[08:15] <Keybuk> shouldn't that be "every 6 months"
[08:17] <SteveA_> kiko: is the bugzilla migration all done?
[08:17] <SteveA_> kiko: with emails etc. too?
[08:21] <mantiena-baltix> SteveA, I have some troubles with adding packages to the distribution. For example baltix has live-installer package, which doesn't exist in ubuntu, but is registered at lauchpad (http://lauchpad.net/products/live-installer )
[08:21] <mantiena-baltix> but I don't find I way how to add baltix to launchpad
[08:22] <SteveA_> mantiena-baltix: sorry, i can't help out right now
[08:22] <SteveA_> are you on the launchpad-users list?
[08:22] <SteveA_> that's a good place to ask such questions, if no one is available on irc
[08:22] <bradb> Kamion: ping
[08:24] <mantiena-baltix> SteveA, ok,  thanks for all help
[08:36] <cprov> bradb: hey aparently the kiko's empty PQM request didn't work, isn't it ? chinstrap/RF still at 2976 .
[08:37] <bradb> cprov: kiko's request never hit pqm. My empty merge request has been being processed for the last few hours.
[08:37] <bradb> Which means, I think, that's it's synching with chinstrap currently.
[08:38] <bradb> I've got a big patch I need to land right now too.
[08:38] <cprov> bradb: ok, let's wait ... again
[08:42] <bradb> I'm having to knowingly write myself into conflicts on a new branch to make progress.
[08:47] <Sero> hello :)
[08:47] <sivang> hi Sero :)
[08:49] <Sero> do you know if ubuntulinux.org can ship 2000 ubuntu cds?
[08:49] <Sero> or i must confirm order?
[08:51] <sivang> I think such a big order should be approved by Canonical,
[08:52] <sivang> I suggest emailing launchpad-users about this and someone will get back to you soon.
[08:52] <sivang> (I suspect ti won't happen before next week thought)
[08:53] <sivang> Sero: also, wait a another sec and I will see if I can give you some email contact to email as well
[08:53] <Sero> ok :)
[08:54] <Sero> I'm promoting linux in Warsaw (capital city of Poland)
[08:54] <Sero> in short time people from other cities should contact with you :)
[08:55] <sivang> very cool :) you're planning some event for the discs giveaway?
[08:55] <Sero> yes
[08:55] <Sero> in few cities in one day
[08:56] <sivang> cool :)
[08:56] <Sero> it's 3-th linux meeting. i'm making it every year
[08:57] <Sero> it's for begginers
[08:58] <matsubara> Sero: I think if you order the cds on the shipit website, with a justification someone from canonical might contact you. Just place the order.
[08:58] <Sero> ok, thx :)
[08:59] <sivang> Sero: yes, you might also email<EMAIL_ADDRESS>in accordance with your order , you will probably need to provide some reason for the big amount :)
[09:00] <sivang> Sero: sorry, that is<EMAIL_ADDRESS>[09:02] <sivang> matsubara: do you know about utilities/launchpad-database-setup ?
[09:04] <matsubara> sivang: unfortunately, no.
[09:05] <sivang> matsubara: np, thanks anyway.
[09:21] <kiko> is pqm hung, I wonder, bradb
[09:22] <bradb> At this point, it hasn't taken long enough for me to think that, sadly.
[09:22] <kiko> that is sad indeed
[09:22] <bradb> I've seen my request sit at #1 for about six hours before.
[09:22] <bradb> Right now, it's "only" about four.
[09:56] <kiko> pqm, pqm, wtf is up with you
[09:56] <kiko> BITCH
[10:01] <seb128> how do I get the malone equivalent of a bug number from bugzilla?
[10:02] <seb128> ie: bugzilla.ubuntu.com is now ....
[10:03] <kiko> http://lists.ubuntu.com/archives/ubuntu-devel-announce/2006-January/000051.html
[10:03] <kiko> The Malone bug IDs will differ from the existing Bugzilla bug IDs, but
[10:03] <kiko> it will be easy to find the bugs by their old ID using the following
[10:03] <kiko> URL:
[10:03] <kiko>   https://launchpad.net/malone/bugtrackers/ubuntu-bugzilla/$BUGZILLA_ID
[10:03] <seb128> ah, right, I knew I read it somewhere
[10:03] <seb128> thank you :)
[10:03] <kiko> enjoy!
[10:03] <seb128> thanks :)
[10:03] <seb128> (would be nice to have a banner saying that on bugzilla)
[10:04] <kiko> yeah, we should do that
[10:04] <kiko> would be nice if you could post to ubuntu-bugzilla..
[10:05] <kiko> and get redirected
[10:05] <kiko> hmph
[10:05] <seb128> no need to post
[10:05] <seb128> but I've a lot of GNOME bugs pointing to bugzilla.ubuntu.com
[10:05] <seb128> and upstream will not go to read the announce mail for sure
[10:05] <seb128> so if there is no easy way to jump to malone the will just give up probably
[10:06] <seb128> s/the/they
[10:06] <kiko> good point
[10:10] <sivang> kiko: you've got mail :)
[10:11] <kiko> saw it
[10:38] <kiko> seb128, see privmsg
[10:39] <seb128> grraaa, stupid freenode registration
[10:46] <LarstiQ> quite
[10:52] <kiko> nha nha nha pqm
[10:52] <kiko> lifeless, pqm wedgie?
[11:01] <kiko> matsubara, dinner at my place tonight?
[11:01] <kiko> 9:30/10pm
[11:01] <kiko> bring asbestos
[11:01] <kiko> (jdahlin is cooking)
[11:02] <Amaranth> I seem to have two accounts on launchpad: amaranth and alleykat. I no longer have access to the<EMAIL_ADDRESS>email address so I can't automatically merge the amaranth account into the alleykat account. Is there anything else I can do?
[11:04] <matsubara> kiko: ok, what is asbestos?
[11:04] <matsubara> kiko: I look for it on wikipedia, it seems to be a kind of mineral or a city of canada
[11:04] <Amaranth> nevermind, i logged into amaranth and merged them the other way
[11:04] <kiko> Amaranth, yes, I'll email stuart so he can fix this for you.
[11:04] <kiko> ah, ok.
[11:05] <kiko> Amaranth, change your preferred email address, while you're at it
[11:05] <sivang> night all, have a nice dinner :)
[11:05] <Amaranth> i thought it was from the bugzilla move, but i guess not
[11:05] <kiko> matsubara, dict asbestos
[11:05] <Amaranth> kiko: i did, thanks anyway though :)
[11:05] <kiko> sure.
[11:06] <matsubara> kiko: now I see what you meant.
[11:13] <dilys> Merge to devel/launchpad: [trivial]  empty merge to, hopefully, (r2994)
[11:14] <matsubara> finally!
[11:14] <kiko> I told elmo to kill pqm
[11:15] <matsubara> kiko: oh
[11:17] <kiko> asked him
[11:17] <kiko> sorry, that sounded all wrong
[11:17] <kiko> I asked elmo if pqm was hung and he said it was, and that it was best to kill it.
[11:20] <matsubara> hm, no problem then. the next commit probably will trigger the update rf to chinstrap, right?
[11:20] <kiko> hopefully
[11:20] <matsubara> great!
[11:26] <matsubara> kiko: i'm going too, see you all later.
[11:26] <matsubara> kiko: gym tonight?
[11:26] <kiko> I'm too hurt
[11:26] <matsubara> kiko: pussy
[11:26] <kiko> yeah yeah
[11:26] <matsubara> kiko: well see you later then.
[11:26] <kiko> laters


[14:24] <nhandler> Looks like we have a meeting scheduled for tonight. Did we set the time based on UTC? If so, I should update the calendar and I should be able to make it (if I've done my conversions correct)


[09:28] <gnuoy> jamespage, do you think it makes sense to add functionality to the quantum-gateway charm to configure the IP, gateway etc of the ext-port ?
[11:15] <Roconda> Hey, can anyone point me in the right direction with JuJu? Looking for a solution to use juju on multiple servers with lxc(similar to multiple local env.). Lets say I´ve got multiple local JuJu enviroments with lxc, how do they communicate with each other?
[11:17] <marcoceppi> Roconda: They don't at the moment. We have an item on the roadmap to allow for "cross-environment relations" it's not implemented yet
[11:19] <marcoceppi> Roconda: we have limited contanier support for deployed servers/services
[11:20] <Roconda> marcoceppi: what do you recommend me, based on my situation?
[11:20] <Roconda> marcoceppi: good to know this issue is something being worked on :-)
[11:20] <marcoceppi> Roconda: so you can create LXCs in deployed environments and co-locate/create more dense services
[11:22] <Roconda> marcoceppi: using JuJu of without?
[11:23] <marcoceppi> Roconda: so containers is a great way to achieve what you want to do, and there is support for this currently, however there are still issues with this solution as there are networking issues
[11:27] <Roconda> marcoceppi: Okay, I guess I will use lxc at the moment and keep an eye on the cross-env. relation. Once cross-env. works I can migrate to JuJu
[11:28] <marcoceppi> Roconda: if you're not already, subscribe to the juju mailing list and watch the [ANN] emails
[11:28] <marcoceppi> Roconda: https://lists.ubuntu.com/mailman/listinfo/juju\
[11:28] <Roconda> marcoceppi: Thanks! Will do. Thanks for your help
[11:33] <marcoceppi> Roconda: while I don't have exact dates, we're looking to address these two features (and many others) within the next 6 months
[11:39] <Roconda> marcoceppi: Ah, in that case I´ll currently use the local environment so I can easily migrate to the cross-environment. I case I do need to scale out I could migrate to Amazon. The reason why I would like to use LXC is about costs. Working on a startup so I can´t afford to run many servers on amazon atm.
[12:04] <marcoceppi> Roconda: there are more affordable cloud providers that Juju supports available. Last time I checked HP Cloud was pretty low in cost compared to AWS
[15:29] <kurt_> jcastro: ping
[15:53] <jcsackett> sinzui: so we're hitting the request limit on the askubuntu API, thus no items.
[15:53] <sinzui> yay!
[15:53] <jcsackett> sinzui: there's a way to get more requests, requiring auth fun. thought we could avoid it, but evidently even once a day is too often.
[15:54] <sinzui> We disable staging and give prod a chance to do its job
[15:54]  * jcsackett nods
[15:54] <jcsackett> that's a thought.
[15:55] <jcsackett> we'll disable it on staging, see if prod picks it up tomorrow, and i'll work on the better version of api querying.
[15:55] <sinzui> lets do that for now. We saw it work on staging. We can discuss this with charmers next week
[15:55]  * jcsackett nods
[15:58] <jcsackett> sinzui: disabling on staging is done, and a card has been added.
[15:58] <sinzui> thank you
[16:44] <gary_poster> paulczar, last night's release of the GUI should have fixes for the bugs you reported.  please let me know if you encounter other issues.
[16:44]  * gary_poster working on announcements
[16:46] <paulczar> yessir appears to have fixed my issues with the gui
[16:46] <paulczar> now I have bug with juju-deployer :)
[16:46] <paulczar> https://bugs.launchpad.net/juju-deployer/+bug/1241721
[16:46] <_mup_> Bug #1241721: juju-deployer never finishes <juju-deployer:New> <https://launchpad.net/bugs/1241721>
[16:46] <gary_poster> paulczar, :-P looking
[16:46] <paulczar> it's still in bug-state ...so I can dig out extra debug info if you want anything
[16:46] <gary_poster> paulczar, plus small internal "yay" for gui ;-)
[16:50] <gary_poster> paulczar, hazmat probably is person to investigate eventually.  Out of curiosity though, do I understand correctly that, according to status and gui, you have all expected services but no relations?
[16:50] <paulczar> looks like rabbit is in pending state
[16:50] <gary_poster> huh
[16:51] <paulczar> so that might be holding it up
[16:51] <gary_poster> that smells more like a juju issue, yeah :-/
[16:51] <hazmat> odd.. still deployr should timeout w error
[16:51] <paulczar> oh I found it!
[16:51] <paulczar>   "4":
[16:51] <paulczar>     agent-state-info: '(error: invalid URL "http://cloud-images.ubuntu.com/releases/streams/v1/index.sjson"
[16:51] <paulczar>       not found)'
[16:51] <paulczar> I'll add the whole juju status
[16:52] <paulczar> added as a comment
[16:52] <paulczar> but that url works fine for me
[16:55] <gary_poster> paulczar, I'm fishing for help for you...
[16:55] <paulczar> thanks :)
[17:05] <paulczar> finally hit some sort of timeout and juju-deployer continued through
[17:05] <paulczar> but obviously still a failed deploy
[17:06] <gary_poster> paulczar, I guess that's good, in that you can probably work around it after the deployment.  So far everyone in the juju-dev pool I asked were at their EoD.
[17:08] <paulczar> yeah, just going to suck if I submit a charm contest entry which can't follow the contest instructions
[17:08] <paulczar> will need big walls of text in the readme :)
[17:19] <marcoceppi> paulczar: 1.16.0 ?
[17:24] <paulczar> yessir
[17:24] <paulczar> appears to be intermittant
[17:25] <paulczar> I ran again and it went through
[17:25] <paulczar> so guessing its not error handling well when a URL doesn't respond briefly
[17:27] <paulczar> the juju-gui export doesn't seem to export which services are exposed.  is this on purpose? or should I file bug ?
[17:30] <gary_poster> paulczar, hm.  that sounds like a bug, yeah, assuming normal deployer formats support this. :-/ thank you
[17:30] <gary_poster> should be easy to do, but inconvenient timing
[17:31] <paulczar> I'll test through again to make sure ... I didn't miss setting it
[17:31] <paulczar> then will file
[17:31] <gary_poster> ack
[17:59] <adam_g> is it possible to configure the network used by the local provider?
[18:24] <marcoceppi> adam_g: not that I know of at this time
[18:25] <adam_g> that stinks
[18:40] <paulczar> in my experience if you can get the local provider to work at all you should be happy :)
[18:52] <adam_g> paulczar, its working good for me.. maybe too good. i have a local provider running on my local system and a remote system, but would like to be able to address them both
[18:54] <paulczar> mine doesn't seem to be able to get working ssh keys in the lxc containers ... so I can't juju debug-log or juju ssh or anything
[18:56] <adam_g> paulczar, oh, maybe you're hitting this? https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1236577
[18:56] <_mup_> Bug #1236577: container's /home/ubuntu/ spawns with incorrect permissions, preventing SSH access <theme-oil> <lxc (Ubuntu):Fix Released> <https://launchpad.net/bugs/1236577>
[18:56] <adam_g> paulczar, i had the same issue
[18:58] <paulczar> it says they fixed ...  did you have to pull something from a master branch?   or was it fixed through to the apt-repos ?
[19:00] <adam_g> paulczar, it was fixed in LXC, not juju
[20:10] <sidnei> hazmat: patch landed in lxc, so progress
[20:10] <hazmat> sidnei, awesome
[20:11] <ahasenack> is there a way to use, say, the "ubuntu" charm, but on saucy?
[20:11] <ahasenack> the charm seems to exist only in the precise namespace
[20:12] <sidnei> ahasenack: if you check it out locally, put into a saucy directory in your local repo, then --repository=... local:ubuntu?
[20:13] <ahasenack> that I didn't try yet
[20:13] <ahasenack> I was looking for command-line options I may have missed
[20:16] <ahasenack> weird
[20:16] <ahasenack> I had to use this:
[20:16] <ahasenack> root@server-1e8400be-2e1c-469a-b794-62a5c587da47:~# juju deploy  --to 2 --repository $(pwd)/charms local:saucy/ubuntu ubuntu-saucy-container
[20:16] <ahasenack> without the saucy bit in local:saucy/ubuntu it would still try precise
[20:16] <ahasenack> I have charms/saucy/ubuntu/resto-of-the-charm
[20:17] <sidnei> ahasenack: probably from default-series in the environments.yaml defaulting to precise
[20:17] <ahasenack> could be. There was no default-series under the "local" environment though, only the others, so i assumed it didn't apply
[20:17] <ahasenack> since local will use whatever I'm running
[20:18] <ahasenack> and indeed, the bootstrap node is saucy
[20:18] <sidnei> i think that was the case in pyjuju
[20:18] <ahasenack> hm, I wanted to relate landscape-client to this one, but doesn't work, also because landscape-client only exists in the precise namespace
[20:19] <ahasenack> bummer, not friendly to non-precise workloads
[20:20] <sidnei> file a bug! i think this could well be a command-line option
[20:21] <ahasenack> the question is if all charms are supposed to work on all series
[20:21] <ahasenack> probably not
[20:29] <sidnei> nope
[20:31] <Nik_> does anyone know if juju clients newer than 0.6.1 (precise) would be backwards compatible with agents running on machines running precise. Since I can't easily move up the release for juju (using MAAS), I wonder if I can upgrade the clients for deploy --to functionality and some bugfixes
[20:36] <cotton> how does os x juju work.. does it create containers directly inside OS X?  or does it require a linux VM for an LXC host..
[20:58] <sarnold> cotton: there are a variety of "providers" that actually speak to whatever "cloud" backend you have. it might be aws or azure or openstack or "local" (lxc, linux-only) or "null" (bad name, hope that changes, that uses ssh)
[20:59] <cotton> ah ok
[20:59] <sarnold> cotton: the ssh-based provider may be able to host workloads on OS X alright, but I'm not sure how far that has been tested.
[20:59] <sarnold> cotton: using the juju frontend on OS X ought to be well-tested, or at least intends to be well tested. :)
[21:00] <cotton> so i can run juju on my mac via brew, then control a 'local' lxc cloud inside an ubuntu vm also?
[21:01] <cotton> also, does juju have charms that take care of HA clusters?  aka corosync/drbd/etc
[21:01] <marcoceppi> cotton: yes, so for the local provider on Mac/Windows, we utilize Vagrant to spin up a VM and run a special Ubuntu image inside that
[21:01] <cotton> yea ok i see HAcluster http://d.pr/i/8QEH
[21:01] <cotton> ah ok
[21:01] <cotton> cool
[21:01] <marcoceppi> cotton: so you need to vagrant up/vagrant ssh, then run juju commands inside the VM
[21:01] <marcoceppi> cotton: it's not a perfect story yet, just a stop gap :)
[21:02] <cotton> ok hah
[21:03] <marcoceppi> cotton: but outside of the local provider, all other providers/commands work on OSX with the native OSX juju client from brew
[21:03] <cotton> nice thanks
[21:08] <sarnold> marcoceppi: ha! you've got vagrant support going already? damn you guys are busy :)
[21:08] <marcoceppi> sarnold: the other way around
[21:08] <sarnold> marcoceppi: ha! vagrant has juju support already? damn those guys are busy! :)
[21:09] <marcoceppi> sarnold: we have a juju vagrant image which has local provider dependecies. So you can up a vagrant instance and get juju all installed witha  deployed local environment and the gui
[21:09] <marcoceppi> sarnold: hah!
[21:09] <sarnold> marcoceppi: that's pretty cool :D