 Latest Lunar ISO fails to install see bug https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2008685
[08:30] -ubot93:#lubuntu-devel- Launchpad bug 2008685 in calamares (Ubuntu) "Installation failed: Boost python error in job'automirror'" [Undecided, New]
[08:34] <arraybolt3> I saw some lsb_release related stuff happening elsewhere that had broken and then unbroken debootstrap. So this might just be transient.
[08:34] <arraybolt3> I'm going to bed, but I should be able to look into it further tomorrow.
[08:34] <guiverc> thanks @Leokolb
[11:40] <tsimonq2> Agreed that it's probably transient, could certainly need swapping with lsb-release-minimal
[14:56] <tsimonq2> guiverc, Leopold https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml-settings/32420/5
[15:03] <tsimonq2> Anyone want to take on https://bugs.launchpad.net/~lubuntu-packaging/+packagebugs and making sure it's up to date?
 A quick glance shows some of those should be dropped. It seems logical there are some that need to be added too.
[16:41] <arraybolt3> To-do item "* Migrate everything else other than the Git repos from Phab to Gitea" I think I'm going to try and tackle the Wiki today. We're almost ready to discard Phab and this will be a major step toward that.
[16:43] <arraybolt3> The question is, to automate or not to automate. I guess it will depend on whether or not Phab's Wiki syntax is compatible with Markdown (I think it is?).
[16:44] <arraybolt3> tsimonq2: One hurdle I'm thinking of with the Wiki is that I *think* we'll lose all access control - anyone with access to the Wiki repo has access to all of it. I think we can probably live with that though.
[16:56] <arraybolt3> OK so the Wiki format is **not** compatible. And writing a converter is probably going to be more work than just manually moving everything one page at a time.
[16:56] <arraybolt3> So I'll move things one page at a time.
[16:58] <arraybolt3> teward: (or to whoever else has access): Mind adding me to the Documentation Team on Phabricator? I can't view the source of individual Wiki documents without being able to "edit" them and having access to that source is very valuable for Wiki migration. Otherwise I have to recreate all the formatting from scratch >_<
 I do think we need to be careful with the security of some pages. So, off the cuff I am not sure what the best approach is.
 I can add you to the doc team though.
[17:01] <arraybolt3> Hmm. I guess it would probably be better to start with only the public pages. Chrome's Incognito mode can help me with that.
[17:02] <arraybolt3> I know Gitea has a Wiki mechanism which I'm using, not sure how its access control works though.
 The Gitea wiki is per repo I think so it is a little strange for our usecase.
[17:03] <arraybolt3> I just have a repo named "lubuntu-wiki-experimental" that I'm using for experimenting with it.
[17:03] <arraybolt3> So we just have one repo that acts as the system-wide Wiki.
[17:04] <arraybolt3> (That's what I thought was the plan before anyway.)
[17:04] <arraybolt3> I figure I can test things out there and then if we like how its shaping up (or how it ended up looking once finished), we can rename the repo.
 That might work, we could further segment that for the various teams so we can manage access  that way.
[17:07] <arraybolt3> That seems like a good idea.
[17:07]  * arraybolt3 wonders if Gitea can make private repos
[17:08] <arraybolt3> Yep, it can.
 Hmm, maybe I can't add you to the Documentation Team.
 I'm missing that lever I guess.
 I added you to the wiki team though.
[17:11] <arraybolt3> Hmm, the "Edit Document" button is still greyed out, but thanks for trying!
 I could add Aaron to the doc team on phab.. (re @kc2bez: Hmm, maybe I can't add you to the Documentation Team.)
[17:46] <arraybolt3> @Leokolb: Thank you!
[18:10] <teward> just saw leo handled that :)
[18:10] <teward> *goes back to his FT job*
 Thanks @Leokolb
[23:15] <arraybolt3> OK one major hurdle I'm realizing with the Wiki is that Gitea doesn't support nested Wiki pages.
[23:16] <arraybolt3> Or at least it doesn't appear to.
[23:17] <arraybolt3> Hmm.
[23:18] <arraybolt3> Perhaps we need a dedicated Wiki system. We're intending on setting up a task system anyway (some alternative to Trello?) which is something Phab used to do, so maybe we need to splinter Phab into Gitea, Taiga or whatever we're using for task tracking, and a Wiki system.
[23:18] <arraybolt3> What else does Phab do...
[23:19] <arraybolt3> At least looking at the home page, that looks like it.
[23:20] <arraybolt3> I might experiment with some in my LXD container and see what I can get going.
[23:21] <arraybolt3> DokuWiki looks too old-school IMO.
[23:22] <arraybolt3> MediaWiki might be overkill. And MoinMoin is already known to be a mess.
[23:29] <kc2bez[m]> WkiJS looks nice but I am not sure how nice it is to work with. MediaWiki isn't terrible I have used that before.
[23:29] <arraybolt3> So far I'm looking for something that supports Markdown and access control lists. MediaWiki's syntax is crazy from what I've seen, but other things don't seem to support good ACLs that I can tell.
[23:30] <arraybolt3> (I don't know if MediaWiki supports ACLs, actually, I got things confused. DokuWiki supports ACLs, not sure what else does.)
[23:31] <arraybolt3> Wiki.js looks hopeful.
[23:31] <arraybolt3> Tar, they want me to use Docker. I'm kinda scared of breaking my container :P
[23:33] <kc2bez[m]> If it is LXD you will need security nesting 
[23:33] <arraybolt3> Yeah. Maybe I should try to set it up locally and then mess with it in the cloud later.
[23:34]  * arraybolt3 is not even close to a sysadmin and is rapidly feeling very out of my league
[23:46] <arraybolt3> OK, I'll be unavailable for the next hour or somewhere around there, maybe longer. Doing an OS reinstall on my primary laptop.
[23:47] <arraybolt3> Be back hopefully soon!
[23:47] <arraybolt3> Currently in the process of flashing the ISO to a drive.