Closed omame closed 2 months ago
mariadb
, like a lot of other packages, will get automatically updated by our bot as soon as there is a new version.
Looking at the autobump logs, the bot does not want to open another pull request as someone is already working on mariadb
right now: https://github.com/Homebrew/homebrew-core/pull/174249
This prevents duplicate work or conflicts. In an ideal world a pull request like the above should not stay open forever and not block updates to be done.
brew livecheck mariadb
tells me that the latest version is 11.5.2
, not 11.4.3
. So we should update to that version.
I think at this point you can open a new pull request manually to do the update if that's ok for you.
brew livecheck mariadb
tells me that the latest version is11.5.2
, not11.4.3
. So we should update to that version.
Specifically mariadb
should track rolling release (thus 11.5.2) but there should also be a new mariadb@11.4
since it is an LTS maintained until May 2029.
Looking at the autobump logs, the bot does not want to open another pull request as someone is already working on mariadb right now: https://github.com/Homebrew/homebrew-core/pull/174249
Ah, I missed that. Thanks for the pointer.
In an ideal world a pull request like the above should not stay open forever and not block updates to be done.
Agreed. It's a tricky one to solve though.
I think at this point you can open a new pull request manually to do the update if that's ok for you.
I may, but I need to test that nothing will break in my instance during the upgrade. It'll require a little more time than a simple patch version bump.
Specifically
mariadb
should track rolling release (thus 11.5.2) but there should also be a newmariadb@11.4
since it is an LTS maintained until May 2029.
Indeed, I was also surprised by that. Perhaps it's worth pursuing this option rather then the above? It should be just a copy of the current formula into mariadb@11.4
with some adjustments, right?
@omame Are there any updates on this matter? I’m eagerly awaiting this update because there’s currently a bug that causes irreversible damage to the cluster every time MariaDB is restarted, and the fix for that is in 11.4.3
In theory, there is a brew feature where users who installed via mariadb@11.4
should remain on that version (but may need to brew link mariadb@11.4
afterward? maybe uninstalling/unlinking mariadb
? haven't tested feature myself).
As for me, I’m happy to migrate to the 11.5 rolling release :)
Thanks @cho-m. https://github.com/Homebrew/homebrew-core/pull/181935 answers my question and I'm learning some brew development with it.
I could switch to mariadb@11.4 and 11.4.3 got installed. Unfortunately the bug that brought me here in first place is still present, but that's an issue with mariadb, not homebrew.
I think we're done here.
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
Mariadb has published a new set of patch releases. These should fix an issue with innodb corruption that users are experiencing.
I tried to use
bump-formula-pr
to bump from 11.4.2 to 11.4.3 but I received an error message stating that mariadb is managed by autobump. Thing is, I couldn't see any PRs for mariadb 11.4.3, even though I can see others being handled just fine.Maybe something is broken in autobump for mariadb?
What happened (include all command output)?
What did you expect to happen?
To be able to bump the mariadb version.
Step-by-step reproduction instructions (by running
brew
commands)