How to install mysql80-server v 8.0.29 ?

  • Thread starter Thread starter olegspecialist
  • Start date Start date
Many words about money, little action. Tired admins give instructions on what to do, I'll do it myself.
 
Congratulations!!!!
1651642188069.png
 
You are super admins. Not installed. Is it called work?

1651642361509.png
 
joneum@ said:
Hello,

I am the maintainer of the MySQL ports.
I don't know if you are aware that we do all this voluntarily?

I have a job that I do during the week.
I have a family that I also enjoy spending time with.
I have other hobbies than sitting at the PC.

I spent 6 hours today to test the update for MySQL 5.7 carefully, so that no one has problems after the release.
I got up at 8am, had breakfast with my family, and after that I took care of FreeBSD. That took about 6 hours.

Now I went shopping and am back at the PC to look at the update for MySQL 8.0. In the past so much was changed with each update that it took days until the port with the new version is ready to be released. This will probably cost me the rest of the weekend.

How has your weekend been so far?

I always get a lot of emails when there is a new update for MySQL. Very many people write with an eMail address from a company. I am happy to see that a lot of companies are using FreeBSD and MySQL.
When I answer that I do all this in my spare time and I would be happy if they support my work with PayPal or Patreon, I don't get any answer anymore. Strange ......
Click to expand...
You have worked hard. If you are free, update MySQL 8.0.30. Many people are looking forward to it. Thank you！
 
I upgraded from FreeBSD 13.0 to 13.1, MySQL8 server disappeared and now I can't install it again.

According to freshports, there's no available version for i386, is it possible for someone to make the package available?

In the meantime, I did a snapshot before upgrading, I will be using a working version.

Thank you
 
Karbust said:
According to freshports, there's no available version for i386, is it possible for someone to make the package available?
Click to expand...
No. It's broken.
Code: 
BROKEN_i386=	--yplg_out: protoc-gen-yplg: Plugin killed by signal 11.
 
Karbust said:
I upgraded from FreeBSD 13.0 to 13.1, MySQL8 server disappeared and now I can't install it again.

According to freshports, there's no available version for i386, is it possible for someone to make the package available?

In the meantime, I did a snapshot before upgrading, I will be using a working version.

Thank you
Click to expand...
Since you are new here a maybe stupid question:
Is there a specific reason you are running i386 (32bit) and not the imho better supported amd64 (64Bit)?
 
elgrande said:
Since you are new here a maybe stupid question:
Is there a specific reason you are running i386 (32bit) and not the imho better supported amd64 (64Bit)?
Click to expand...
Yes, I don't have the necessary knowledge to convert the full application to a 64bit version (and respective libs), nor the know-how to build 32bit apps on 64bit OS (I heard there are ways).

But, for now, I'm gonna keep using the VM pre-upgrading (thanks snapshots).
 
None of the upgrades I did from 13.0 to 13.1 required any changes to installed ports/packages, but maybe i386 is different? Doesn't help you (sorry) but curious why it happened in your case.
 
richardtoohey2 said:
None of the upgrades I did from 13.0 to 13.1 required any changes to installed ports/packages, but maybe i386 is different? Doesn't help you (sorry) but curious why it happened in your case.
Click to expand...
Because MySQL 8 is broken on FreeBSD i386, I didn't notice any other package missing, just this one...
 
Karbust said:
Yes, I don't have the necessary knowledge to convert the full application to a 64bit version (and respective libs), nor the know-how to build 32bit apps on 64bit OS (I heard there are ways).
Click to expand...

The app has 32bit binary libs included?
For "normal" stuff, I'd expect it to just simply compile on amd64. Just talking about this, because I have the impression amd64 is the _much_ wider spread and better supported platform and people seldomly use i386 nowadays.
 
Karbust said:
Because MySQL 8 is broken on FreeBSD i386, I didn't notice any other package missing, just this one...
Click to expand...
But how did the OS upgrade change your installed packages? It‘s a bit off-topic but the OS upgrade was kernel upgrade, reboot, userland upgrade, reboot - job done.

My understanding is that it wouldn’t affect ports/packages at all, so curious as to how this process made a package disappear when you did it. I’ve got a few machines left to upgrade so want to be sure my understanding is correct or fix it if it’s wrong.

Going from 12.x to 13.x would have needed package/port changes but I didn’t think a minor version upgrade would.
 
Karbust said:
I don't have the necessary knowledge to convert the full application to a 64bit version (and respective libs), nor the know-how to build 32bit apps on 64bit OS (I heard there are ways).
Click to expand...
Leave the application on the 32 bit server, only move the database to a separate 64 bit machine. And also realize that you can run a 32 bit application on a 64 bit OS. That's what the COMPAT_FREEBSD32 kernel option is for and the accompanied /usr/lib32 libraries. This is for binary compatibility.

i386 (32 bit) has been 'demoted' to Tier 2. So the best way forward would of course be to fix the application itself. Do you have access to the source code? Then just build it on a 64 bit system, if the application has been written properly this really shouldn't be much of an issue. If it's been incorrectly written (code assumes 32 bit) then you would need to fix that code.

In either case, the quickest solution is just to migrate the database to its own machine. Then you can keep the application itself running on the 32 bit machine.
 
Hello richard :-)

I386 is broken since the last update. I had been looking for a solution for a while but didn't find one. Currently I am focusing on the update for 8.0.30.
Actually I would be now on the legendary Wacken konzert, but since I have flu (no Corona ^^) I have just time to take care of the update.
Whether the problem with i386 is fixed then, I can not promise.
As other people said, i396 architecture is now a kind of "exotic", which is only fixed if the solution is simple and fast to find.
Personally, I hope that i386 will soon no longer exist.

Cheers
Jochen
 
SirDice said:
Leave the application on the 32 bit server, only move the database to a separate 64 bit machine. And also realize that you can run a 32 bit application on a 64 bit OS. That's what the COMPAT_FREEBSD32 kernel option is for and the accompanied /usr/lib32 libraries. This is for binary compatibility.

i386 (32 bit) has been 'demoted' to Tier 2. So the best way forward would of course be to fix the application itself. Do you have access to the source code? Then just build it on a 64 bit system, if the application has been written properly this really shouldn't be much of an issue. If it's been incorrectly written (code assumes 32 bit) then you would need to fix that code.

In either case, the quickest solution is just to migrate the database to its own machine. Then you can keep the application itself running on the 32 bit machine.
Click to expand...
I compile and run the app in i386 in development, on live server it runs on amd64.

I'm already attempting a migration for amd64 (mostly datatypes, already using external libs from pkg): https://forums.freebsd.org/threads/moving-from-32-bit-to-64-bit.49630/
 
You must log in or register to reply here.
Back
Top