Ticket #45725

Refresh mysql.m4 from upstream

Open Date: 2022-09-26 07:42 Last Update: 2023-04-01 00:41

Reporter:
Owner:
Type:
Status:
Closed
Component:
MileStone:
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
Fixed
File:
1

Details

Our mysql.m4 is based on ancient upstream version (or not-so-good upstream between us and autoconf archive - refresh directly from the archive)

Ticket History (3/7 Histories)

2022-09-26 07:42 Updated by: cazfi
  • New Ticket "Refresh mysql.m4 from upstream" created
2022-12-03 21:49 Updated by: cazfi
2023-01-31 11:17 Updated by: cazfi
2023-03-23 08:51 Updated by: cazfi
Comment

Splitting this one, to get it started. There's a challenge that our copy of the file is based on older version than any related site (there has been multiple homes for it over the years) has history for. Let's make this ticket about simply establishing a baseline of the file -> something that we say to match known upstream version, with our own modifications. New ticket ( #47652 ) is about then applying/porting upstream updates on top of that.

2023-03-23 09:23 Updated by: cazfi
  • Owner Update from (None) to cazfi
  • Resolution Update from None to Accepted
Comment

Patch to establish initial baseline by documenting upstream, and including upstream header as closely matching our version as possible (from the time the file moved from now defunct home to a new location - our copy is some version from that old home)

No functional changes as this touches comments only.

2023-04-01 00:41 Updated by: cazfi
  • Status Update from Open to Closed
  • Resolution Update from Accepted to Fixed

Edit

Please login to add comment to this ticket » Login