mi-hol

This script would enable to resolve OS issues outside of OMV's control easily Benefits: - remove the pressure for getting an issue resolved via forum posts - protect user's time...

@ryecoaaron there is no expectation about fixing apt issues. the referred forum post is to support the expected benefit "protect user's time invested to configure OMV"

> I don't think fixing apt issue by re-installing OMV is the correct approach well you are invited to post a solution for this specific issue but generally "Fix any...

> all those problems have prevented me from implementing a feature that is broken from the start. @votdev Now with this revised statement it would make sense to delete https://github.com/openmediavault/openmediavault/issues/102#issuecomment-388629332...

From above reply I understand that the current documentation regarding /etc/openmediavault/config.xml is not fully correct "What is the file /etc/openmediavault/config.xml for? It is the database configuration store file for openmediavault....

@votdev this issue is currently in Backlog for 6.x but from the conversation above I'd assume the assignment to be wrong. Could you please review & update gh project assignment...

Maybe following the [rules of "semantic versioning"](https://semver.org/spec/v2.0.0.html) would have a greated benefit for the user community than adding a date. For example adding "conflicts" to prevent installation on a desktop...

> stated in the release candidate blog post well semver has the rule to flag "A pre-release version indicates that the version is unstable and might not satisfy the intended...

Can this be closed?

Currently its only labeled to affect 4.x which is EOL Assuming it doesn't affect 5.x, why would there be an interest to keep it as open?