Interesting find: backupninja.
May 29 2018
May 23 2018
Well boards are a nice way of viewing things because they can kind of give you a better overview of what's going on for a particular arena. We could certainly have an urgent column on the boards, but that's silly since there's already color coding on the boards to indicate status. Note, too, that tags are synonymous with projects, so in order to have an urgent tag, we'd need to have an urgent project. Since each project can only have one board (but each task can have multiple projects/tags), that would mean we end up with an urgent board which just seems silly.
May 22 2018
Sure. I'll probably ask around the Tootverse to confirm this is the
best. I don't love Ruby, but that is Mastodon, after all.
If you RTFM (where M = README), you find they have a hosted instance but
the code's all there to run your own.
Remarkup can do some weird things, especially with long links and line breaks just FYI.
I've never bothered to do this but
here is one
option I'm aware of.
And just to put it down on paper, we set:
If this works, we did it!
May 21 2018
Testing outgoing mails for @teward 🙄
We should be back up and running for outgoing. While we work on configuring incoming, there will be some brief postfix restarts but nothing that should affect outgoing emails.
Got the reply from Canonical and all is well. Thomas will be replacing sendmail with postfix, so we'll have a temporary downtime starting in about 5 minutes. I announced to the lubuntu-devel list.
Yeah AFAIK that's what needs to happen. Or we could create an "urgent/security" column, but that seems messier.
I think creating a task would be ideal. Maybe we even create a separate security board for it?
To further confirm: works fine in Cosmic with it as is.
Just to put it down on paper, we don't have python2.7 in Bionic. Since python is always supposed to refer to python2, python just fails. obamenu doesn't have python3 compatibility, however, so it fails, too. In order to make this work you have two options:
May 20 2018
It's actually fairly well documented.
I will note that agaida suggested it is coming soon.
How many repos like this are we going to have this problem with, though? If the number is small, I wouldn't bother with the headache, but if that's how you want to spend your Sunday… ☺
What would be the value of adding that additional level of complication?
If 0.13 lxqt-about is anything like 0.12, no, it lacks the right info. Can I throw in a request for lsb_release info, at least for Debian distros?
Well, obviously we need space to put stuff, so where do we get that? For any significant amount of storage, we would need to pay for it.
May 18 2018
I got Thomas Ward access to the the site and he's going to look into setting up the MTA. He's going to need to work with Canonical to make this happen. He's already made contact but they need to look into it some more so it's kind of blocked by them for the time being.
May 17 2018
I'm gonna leave this unassigned. I think like some of the other infrastructure things we have in Meta, it'll be first come first serve.
Done. sil2100 said they'd release it.
Since we didn't have any takers, you got any other ideas @tsimonq2 ?
Did I not just see you make a merge request suggesting otherwise?
May 16 2018
Added to the CC agenda for tomorrow.
Sadly I don't have a freaking clue. Maybe a message to the list asking them what it would take? XD I'll see if the CC has any ideas.
Oh in other words just going into the live environment no matter what? Sure, yes. JFDI IMHO.
Closed then, but feel free to make a new task to collect potential testcase improvements if you had some particular ideas.
alejdg on #canonical-sysadmin just told me they'd take a look at it and try to update.
Tested and confirmed working.
I'm not sure I know exactly what you mean. Screenshot? Meanwhile, I think at least getting us up to speed with the way things have been done is crucial.
Why would these not just be added to the testcases?
As long as that doesn't mean LXLE sending more of their support our direction, I'm game. :)
@tsimonq2 I honestly haven't thought about it any further but we need to do something.
Unfortunately it's not fixed, or rather we have a new problem, which is that we now have two sessions: LXQt and OpenBox. The latter is the default you would expect (kind of like how FluxBox is) and the former requires you to enter a WM. If you choose OpenBox, you end up without a panel which kind of sucks.
May 15 2018
Nope. 1.10.6-1 is already in there. Neener neener.
lubuntu-meta 0.94.1 now in proposed. Needs verification.
Merge proposal. Finish i t up, bud. ☺
Pinged SRU vanguard (arges, rbasak) and Simon just did so with infinity and slangasek, too.
May 13 2018
May 11 2018
Jan 4 2018
Yep. You should have received a copy of that I would have thought.
Dec 27 2017
Dropped the whole LVM/encryption thing, at least from this task. If there are issues with those, that should be a separate task.
OAuth1 is the way to go: it's supported by Phabricator (see Twitter, BitBucket, JIRA providers) and Ubuntu SSO (though they don't guarantee they won't drop it).
Started discussion on how to best deal with this, as it's a problem ultimately affecting every image.
Dec 8 2017
Sorry about the delay. I have now confirmed the following installs as of today:
Dec 5 2017
Dropped a message on the Phabricator community support forum (which, in an example of poor dogfooding, is not Phabricator but Discourse). Hopefully someone will have some sort of solution.
Unfortunately it looks like the request for OpenID auth was denied but I'll see if I can find some more information as that's a little old.
Nov 28 2017
Here's the Discourse plugin and it is indeed using OpenID.
Everything's archived and the wolf and I have been removed. It's up to @tsimonq2 to completely kill it.
Supposedly the contact for Ubuntu One (login.ubuntu.com) is firstname.lastname@example.org. Just dropped them an email.