Clean rundeps

Packages planned for deprecation

- python-jsonrpc-server		Replaced with python-lsp-jsonrpc
- python-language-server	Replaced with python-lsp-server
- python-pyls-black		Replaced with python-lsp-black
- python3-jedi			Replaced with python-jedi
- python3-jedi-dbginfo		Replaced with python-jedi-dbginfo

Update to 3.1.2.

Update to 3.1.1.

Update to 3.0.4.

Fancy double quotes in description.

Needs to be validated again >:(

Update to 3.0.3.

LGTM, thx

LGTM, thanks!

Replace qt5-base-docs

Upstream solus-sc PR.

I'm marking this as needing a new maintainer, as the prior maintainer no longer actively contributes and someone with an intimate knowledge of lxc / lxd should be maintaining and using this.

Re-inclusion will need to go through our standard package request process.

Hey, I will maintain this package

I think you are overestimating the amount of people that actively read the blog or our blog posts. We had people coming in months after our infrastructure migration blog posts saying they couldn't reach the old package repository. There is no good mechanism at this time of guaranteeing someone sees an RFC. Either way, this task needs to stay on topic. If someone is interested in becoming a maintainer for this package, at the very least a new patch on top of our existing repo will need to be provided.

Thanks. I think it's the sort of thing that could have done with being covered in a [section of a] blog post.

@Schteve I agree that it's not ideal atm, but you could e.g. select "Watch Project" here: https://dev.getsol.us/project/profile/32/

I only noticed that this was deprecated after it had been removed from my system, likewise with newsboat.

This package has now been deprecated from the repository. Should you wish for it to return, please be mindful that it and its deprecated ruby dependencies will need to be updated and maintained.

As no maintainer has come forth, closing as wontfix and deprecating from the repository. Re-inclusion will need to go through our standard package request process.

As no maintainer has come forth, closing as wontfix and deprecating from the repository. Re-inclusion will need to go through our standard package request process.

As no maintainer has come forth, closing as wontfix and deprecating from the repository. Re-inclusion will need to go through our standard package request process.

As no maintainer has come forth, closing as wontfix and deprecating from the repository. Re-inclusion will need to go through our standard package request process.

As no maintainer has come forth, closing as wontfix and deprecating from the repository. Re-inclusion will need to go through our standard package request process.

As no maintainer has come forth, closing as wontfix and deprecating from the repository. Re-inclusion will need to go through our standard package request process.

As no maintainer has come forth, closing as wontfix and deprecating from the repository. Re-inclusion will need to go through our standard package request process.

As no maintainer has come forth, closing as wontfix and deprecating from the repository. Re-inclusion will need to go through our standard package request process.

As no maintainer has come forth, closing as wontfix and deprecating from the repository. Re-inclusion will need to go through our standard package request process.

Closing due to a maintainer not stepping up to provide and address any issues with patches.