[19:44] Had legacy launchpad ID 'hartbx` created ~15 years ago. Tried to log in last week and it forced me to create a new UbuntuOne ID. Now all launchpad login attempts fail (multiple browsers, multiple machines, after clearing cache; login to other UbuntuOne services works). For example: [19:44] Oops! [19:44] Sorry, something just went wrong in Launchpad. [19:44] We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience. [19:44] If you can't login, join us on #launchpad IRC channel at irc.libera.chat, e-mail us or visit our feedback page. [19:44] If you report this as a bug, please include the error ID below, preferably by copying and pasting it rather than by taking a screenshot. [19:44] (Error ID: OOPS-d70fe2c4f40eca8c34248d1f9a894ac8) [19:50] hart: drop an email to feedback@launchpad.net with that OOPS ID included, someone should be able to sort that for you [19:51] Will do; thank you! [20:58] Is https://staging.launchpad.net/ still supported? I am interested in evaluating it for a package I am currently maintaining on GitHub. [20:59] When I try to sign-in/register, it takes me to an Ubuntu One login and gives me an error when I attempt to use my normal account. [21:00] Login to launchpad.net itself is working for me. [21:14] penguin359: Why do you want to use the staging instance of LP? That looks more like a test environment for the development and testing of Launchpad itself. [21:14] Is there some reason normal Launchpad won't just work? [21:19] I did not want to clutter up launchpad.net with an extra dummy project in the case I decide to not move from github.com. [21:19] I am mainly considering since this is a package I am currently maintaining a personal PPA for and thought it might be better to have it all in one spot. [21:21] This is essentially a backport of a package without going through all the bureaucratics of the formal Ubuntu Backports at this time.