Ticket #45725

Refresh mysql.m4 from upstream

Date d'ouverture: 2022-09-26 07:42 Dernière mise à jour: 2023-04-01 00:41

Rapporteur:
Propriétaire:
Type:
État:
Atteints
Composant:
Priorité:
5 - moyen
Sévérité:
5 - moyen
Résolution:
Fixed
Fichier:
1

Détails

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
Commentaire

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
  • Propriétaire Update from (Aucun) to cazfi
  • Résolution Update from Aucun to Accepted
Commentaire

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
  • État Update from Ouvert to Atteints
  • Résolution Update from Accepted to Fixed

Modifier

Please login to add comment to this ticket » Connexion