=== Spads_ is now known as Spads === NikitaKonovalov2 is now known as NikitaKonovalov === bdx_ is now known as bdx === nesthib_ is now known as nesthib === chrisccoulson_ is now known as chrisccoulson === [HeOS] is now known as HeOS [11:47] Greetings, I've got a question about projects in relation to jujucharms and how launchpad is setup to warehouse charms which seems like a very specific tier of preconditions that have to be met in order for anything to work in here... [11:48] I've got a charm project that exists in a user namespace, but anytime you attempt to file bugs, it states that the package doesn't exist in the jujucharms collection. If i remember correctly this is due to how charms work in launchpad, that only a promulgated charm gets this via aliases [11:48] is there a way i can alias a project? As the new charm store is decoupled from launchpad, and its entirely reasonable to want bug tracking on a package that only exists in a users namespace [11:54] Not really, I'm afraid. The best you can do is add a bit of text that points people to some top-level project that you use for bug tracking (perhaps only for bug tracking). [11:55] But it's not clear that the charms distro still makes sense in the new world, in which case aliases are irrelevant. [11:55] eg. you'd file bugs against https://launchpad.net/postgresql-charm rather than https://launchpad.net/charms/+source/postgresql [11:55] The latter was a hack that was meant to be replaced three years ago anyway. [11:55] lazyPower: Why do the branches need to stay under https://launchpad.net/charms? === gkadam is now known as Guest18444 [12:42] wgrant well, it doesnt now that you've said that [12:42] i agree === Guest18444 is now known as gkadam === beuno_ is now known as beuno [14:37] As there's nothing in the topic... Issues with launchpad atm? === Guest36907 is now known as karstensrage === cjwatson changed the topic of #launchpad to: Firefighting: one haproxy frontend failed | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [14:41] sysadmins are investigating [15:27] topic says "one haproxy frontend failed", did it also break ppa builds? [15:27] they're stalled [15:27] tjaalton: We stopped buildd-manager for the duration to avoid compounding the damage. [15:27] tjaalton: Should be back up soon. [15:28] ok, cool [15:28] Turns out the buildd-manager really doesn't like half its librarian uploads failing. [15:28] heh [15:37] is it safe to assume this CA error is related to the haproxy being angry [15:37] http://pastebin.com/raw/bV3hNJf1 [15:40] giovino: How long ago was that? [15:40] giovino: Both frontends look OK to me at the moment. [15:40] let me test again [15:41] i’m seeing it right now on a this [15:41] Description: Ubuntu 14.04.4 LTS [15:41] it could me just me in theory… ?? i didn’t test too much as i noticed there were many issues with launchpad… [15:43] here’s the full output [15:43] http://pastebin.com/raw/hzYxistt [15:44] same error on os x box from same Internet connection [15:45] same error on ubuntu box in AWS too [15:45] probably not just me :) [15:47] giovino: http://paste.ubuntu.com/15832590/ [15:48] hmm how could i see it on three different boxes two different networks? [15:49] giovino: Perhaps they all happen to have very out of date CA certificates? [15:49] I don't know, but it doesn't look like a Launchpad problem to me [15:49] os x too? [15:49] hmm ok [15:50] Oh, hmm, I see it from another network [15:50] good.. i’m not insane === cjwatson changed the topic of #launchpad to: Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [15:54] tjaalton: should be better now [15:54] (and your earlier upload was reprocessed) [15:54] cjwatson: cool, thanks [15:55] giovino: still looking, but I think this is unrelated to the outage [15:56] ok.. i’ll do some reserach too.. how it first popped up for me is ansible yelled at me when it was trying to add and ppa [15:56] my guess something has changed.. the first thing i did was to look to see if lanuchpad has a new ssl cert which it does not appear it does [15:58] giovino: can you find an HTTPS site that *does* work on the affected systems? [15:59] 'cos on mine I get the same on slashdot.org, sourceforge.net, reddit.com, microsoft.com [15:59] which rather suggests it's a local problem [15:59] hmm .. github.com throws same error too [16:01] yea ok.. letting launchpad.net off the hook.. i suspect we’ve (the internet) have some other issue === Spads_ is now known as Spads [16:40] something wrong with the publisher still? [16:41] tjaalton: please can you give details if you have a problem [16:41] it's not fun to have to guess :) [16:41] cjwatson: sorry :) https://launchpad.net/~freeipa/+archive/ubuntu/ppa/+packages opendnssec has been trying to get published for some time [16:43] There does seem to be something wrong there; let me see. [16:43] I did upload -1.5 quickly after 1.4 when things were somewhat offline, then deleted those and uploaded 1.6 which then built [16:44] dunno if that has something to do with it [16:44] No. [16:44] The publisher has been globally stuck since the nutmeg outage. [16:45] ahah, ok :) [16:53] tjaalton: Should recover soon. [16:53] cjwatson: cool, thanks! === TRB143_ is now known as TRB143 === JanC_ is now known as JanC [23:02] LP is really slow syncing with debian [23:03] 18h since I uploaded sssd point-release there [23:04] tomorrow maybe.. [23:08] tjaalton: Debian may be having dak issues; all the mirrors I see are about 20 hours [23:08] old [23:08] http://ftp.debian.org/debian/dists/sid/main/source/