[05:51] <vagrantc> so, when you use an lp: address, say "bzr branch lp:epoptes", it resolves to bzr+ssh://.../epoptes ... but what about for anonymous logins?
[05:54] <wgrant> vagrantc: If you haven't run 'bzr lp-login' (or have removed the username setting from ~/.bazaar/bazaar.conf and ~/.bazaar/authentication.conf) it resolves to HTTP instead.
[05:55] <vagrantc> there's no anonymous https access?
[05:57] <wgrant> vagrantc: There's anonymous HTTPS for git, but not for bzr at the moment.
[05:58] <vagrantc> wgrant: ok, that's good to know. didn't even know launchpad had git support.
[05:58] <vagrantc> thanks!
[07:35] <alkisg> Hi, I'd like to start using git instead of bzr for my "epoptes" project on launchpad, do automatic translation imports support pushing to git?
[08:21] <wgrant> alkisg: Translations doesn't have direct support for Git at the moment. You can in some cases import using LP's git->bzr imports, but there's no built-in way to do the other direction today.
[08:22] <wgrant> It's a simple cronjob to run yourself, though. Ask LP to export to some arbitrary bzr branch, then have a script that just replaces the files in the git repo with the latest copy from bzr.
[08:48] <alkisg> wgrant: so I can setup translations to read the templates from git, then push to bzr, and the only custom thing is then from bzr translations to git upstream?
[08:59] <wgrant> alkisg: Translations can't import directly from git, but LP can import git repositories into bzr repositories as long as you don't use submodules or gpg signatures, and then import translations from there.
[09:07] <alkisg> Gotcha, thank you very much :)
[09:07] <alkisg> (again :))
[16:17] <teward> I see that there's a "Processors:" item now on PPA edit pages, is that something new available to every user?  (I see armhf is still admin-only enablement, but I see ppc64el now)
[16:19] <teward> nevermind, i think it's answered elsewhere, i just dno't pay attention to all my IRC chans :)
[16:21] <cjwatson> http://blog.launchpad.net/ppa/ppas-for-ppc64el
[18:36] <fingers> how do I find package "libmecab2v5" on launchpad ?
[18:37] <fingers> oh... found it
[18:37] <fingers> https://launchpad.net/ubuntu/+source/mecab
[18:37] <fingers> just under a different name
[18:38] <teward> fingers: package name and source package name can differ
[18:38] <teward> where libmecab2v5 is a built package, from the mecab source code
[18:38] <fingers> is this where I can file a bug report?
[18:38] <teward> yes
[18:39] <teward> but also if libmecab2v5 exists on your system, `ubuntu-bug libmecab2v5` is also a way to file the bug report (it should be able to determine the source package automatically)
[18:40] <fingers> ok I filed a bug report
[18:40] <fingers> https://bugs.launchpad.net/ubuntu/+source/mecab/+bug/1539213
[18:41] <teward> that's misfiled
[18:41] <fingers> libmecab2v5 was renamed &/OR removed in ubuntu 16.04 xenial xerus
[18:41] <fingers> therefor mysql-server wont install
[18:41] <teward> fingers: i don't think mysql-server is mysql-community-server
[18:41] <teward> but not 100% certain
[18:42] <fingers> ah yes I meant mysql-community-server
[18:42] <fingers> which is in the repo http://repo.mysql.com/
[18:42] <teward> that's not a launchpad bug then
[18:43] <fingers> I filed a bug report on mysql
[18:43] <fingers> some idiot deleted it
[18:43] <fingers> http://bugs.mysql.com/bug.php?id=79798
[18:43] <fingers> the bug is in fact that the package libmecab2v5 was renamed &/OR removed in ubuntu 16.04 xenial xerus
[18:44] <fingers> as you can clearly see in my bug report apt-get output
[18:44] <teward> it's not an Ubuntu bug then, so therefore it doesn't belong in a bug on Launchpad
[18:44] <dobey> it's not an ubuntu bug
[18:44] <teward> mysql has to fix their repository packages' dependencies
[18:44] <teward> dobey: indeed (invalid already by my hand)
[18:44] <fingers> and they wont
[18:44] <fingers> because they are idiots
[18:44] <dobey> you're trying to install something from mysql on a version of ubuntu that isn't released, which i'm sure they don't support yet, because it's not released
[18:44] <teward> ^ that
[18:45] <dobey> don't call people names, please
[18:45] <fingers> its a fair assesment because the bug was clearly shown in my report
[18:45] <fingers> and they deleted my bug report
[18:46] <dobey> well obviously it's not deleted; i can see it just fine
[18:46] <fingers> Umesh Umesh said and I quote "it works fine on 15.10"
[18:46] <dobey> yes
[18:46] <dobey> which it does
[18:46] <fingers> but I am not running 15.10 I am running 16.04
[18:46] <dobey> but it's still not an ubuntu problem
[18:47] <fingers> it is........ because 16.04 xenial xerus which is under devel
[18:47] <dobey> your problem is that mysql.com doesn't provide support for 16.04 which is not yet released
[18:47] <fingers> has renamed or removed libmecab2v5
[18:48] <teward> fingers: no, it's *NOT* an ubuntu problem
[18:48] <teward> read my post to the mysql bug
[18:48] <teward> mysql has to fix the depends for the 16.04 version of the package
[18:49] <fingers> are you Umesh Umesh ?
[18:49] <teward> because the issue is in the mysql-community-server package, NOT Ubuntu
[18:49] <dobey> well the package has a Replaces: too
[18:49] <dobey> so it should just work, but *shrug*
[18:49] <dobey> i don't know what the mysql upstream package builds are like
[18:49] <fingers> teward are you Umesh Umesh ?
[18:50] <teward> fingers: whois helps you know, read my name, im' the one who posted on the bug today
[18:50] <teward> and you can stop about this here, it's not an Ubuntu issue
[18:50] <fingers> why was libmecab2v5 renamed or removed in 16.04
[18:50] <fingers> no one has answered that question
[18:50] <dobey> and even if it was an ubuntu issue, #ubuntu is the channel for help on ubuntu
[18:50] <dobey> this channel is for help on launchpad.net itself
[18:51] <dobey> read the changelog
[18:51] <dobey> it clearly states
[18:51] <fingers> oh....... found it
[18:51] <fingers> http://packages.ubuntu.com/xenial/libmecab2v5
[18:51] <fingers> this is now a "Virtual Package"
[18:52] <fingers> they dropped the v5 now its just libmecab2
[18:52] <fingers> so mysql has to update its depends
[18:52] <fingers> *shrugs*
[18:53] <fingers> if you navigate to
[18:53] <fingers> http://packages.ubuntu.com/xenial/libmecab2
[18:53] <fingers> and look on the side for "bug reports" it links to launchpad
[18:53] <fingers> go figure........
[18:53] <dobey> yes, launchpad is the site where ubuntu hosts it's bug
[18:54] <fingers> anyways fuck it... I am done with all this bullshit
[18:54] <dobey> launchpad however is not the site that provides technical support for ubuntu
[18:54] <dobey> well, at least that's over with i guess
[18:59] <teward> dobey: for now (i have a nagging feeling they or someone else like them will be back)
[18:59] <teward> anyways... *goes off to poke his PPAs*
[21:06] <nacc> anyone else noticing some latency from lp's autobuilds? normally the transition from end of build to published and available is ~10 minutes. But my last one is sitting at 39 minutes still. And a build I just submitted was niether accepted/rejected via email, although dput reported no errors?
[21:14] <cjwatson> nacc: Some non-critical jobs are currently disabled to make way for a database schema change.
[21:14] <cjwatson> nacc: (At least, I requested such a deployment earlier today, and I infer from logs that it's in progress)
[21:14] <nacc> cjwatson: ah! ok ... sigh, that hurts my php7 transition work, but i can workaround it locally! thanks!
[21:14] <cjwatson> nacc: It shouldn't take too much longer.
[21:14] <nacc> cjwatson: np, i can pass debs to sbuild to at least have everything staged for when it's back