notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
This referral link gives you 10% off a account and gives me a discount on my Fastmail account.

Get notified when packages are built

A new feature has been added. FreshPorts already tracks package built by the FreeBSD project. This information is displayed on each port page. You can now get an email when FreshPorts notices a new package is available for something on one of your watch lists. However, you must opt into that. Click on Report Subscriptions on the right, and New Package Notification box, and click on Update.

Finally, under Watch Lists, click on ABI Package Subscriptions to select your ABI (e.g. FreeBSD:14:amd64) & package set (latest/quarterly) combination for a given watch list. This is what FreshPorts will look for.

non port: databases/mysql56-server/files/

Number of commits found: 2

Friday, 30 Jun 2023
01:40 Muhammad Moinur Rahman (bofh) search for other commits by this committer
databases/mysql56-*: Sunset

2023-06-30 databases/mysql56-*: Upstream support ended in February 2021

Approved by:	portmgr (blanket)
commit hash: 1fb68a4d5483cd0ac802a916d240def524eabce7 commit hash: 1fb68a4d5483cd0ac802a916d240def524eabce7 commit hash: 1fb68a4d5483cd0ac802a916d240def524eabce7 commit hash: 1fb68a4d5483cd0ac802a916d240def524eabce7 1fb68a4
Tuesday, 28 Apr 2020
21:08 joneum search for other commits by this committer
databases/mysql56-{client, server}: Update to latest release 5.6.48

- InnoDB: A tablespace import operation that failed due to the source and
destination tables being defined with different DATA DIRECTORY clauses reported
an insufficiently descriptive schema mismatch error. Moreover, if a .cfg file
was not present, the same operation would raise an assertion failure. A more
informative error message is now reported in both cases before the import
operation is terminated due to the data directory mismatch.

- InnoDB: Updating certain InnoDB system variables that take string values
raised invalid read errors during Valgrind testing.

- Replication: In the event of an unplanned disconnection of a replication slave
from the master, the reference to the master's dump thread might not be removed
from the list of registered slaves, in which case statements that accessed the
list of slaves would fail. The issue has now been fixed

- Replication: With the settings binlog_format=MIXED,
tx_isolation=READ-COMMITTED, and binlog_row_image=FULL, an INSERT ... SELECT
query involving a transactional storage engine omitted any columns with a null
value from the row image written to the binary log. This happened because when
processing INSERT ... SELECT statements, the columns were marked for inserts
before the binary logging format was selected. The issue has now been fixed.

More Infos:

MFH:		2020Q2
Security:	21d59ea3-8559-11ea-a5e2-d4c9ef517024 (MySQL - Server)
Security:	622b5c47-855b-11ea-a5e2-d4c9ef517024 (MySQL - Client)
Sponsored by:	Netzkommune GmbH
Original commitRevision:533270 

Number of commits found: 2