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.

Resolved by D10142

Resolved by D10225

With the above patch, I volunteer to maintain this one. Long live Neovim stuff! :)

I don't really want to maintain this anymore since no one seems to use it anyways. I say we deprecate it.

I will maintain this Package

I'm willing to maintain this, as I use this quite regularly. See the linked revision for an update to the latest version.

Or you can use github latest release selenium-3.141.59 https://github.com/SeleniumHQ/selenium/releases

Opened D10142. We have to wait for python-selenium to get 4.0.0 out of alpha.

This package has been marked by a Core Team member for planned deprecation. In this case, Planned Deprecation means that this package will be removed from our repository in the event no individual comes forward to maintain this package. Such Planned Deprecation will occur no less than 30 days from the adding of this tag.

This package has been marked by a Core Team member for planned deprecation. In this case, Planned Deprecation means that this package will be removed from our repository in the event no individual comes forward to maintain this package. Such Planned Deprecation will occur no less than 30 days from the adding of this tag.

This package has been marked by a Core Team member for planned deprecation. In this case, Planned Deprecation means that this package will be removed from our repository in the event no individual comes forward to maintain this package. Such Planned Deprecation will occur no less than 30 days from the adding of this tag.

This package has been marked by a Core Team member for planned deprecation. In this case, Planned Deprecation means that this package will be removed from our repository in the event no individual comes forward to maintain this package. Such Planned Deprecation will occur no less than 30 days from the adding of this tag.