Re: Time to back-patch libxml deprecation fixes?
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2024-04-15T23:30:46Z
Lists: pgsql-hackers
On Mon, Apr 15, 2024 at 07:14:22PM -0400, Tom Lane wrote: > I could switch the animal to use -Wno-deprecated-declarations in the > back branches, but I'd rather not. I think the right answer is to > back-patch Michael's 65c5864d7 (xml2: Replace deprecated routines with > recommended ones). We speculated about that at the time (see e.g., > 400928b83) but didn't pull the trigger. I think 65c5864d7 has now > baked long enough that it'd be safe to back-patch. Yeah, I saw the failure with indri this morning while screening the buildfarm, and was going to send a message about that. Backpatching 65c5864d7 would be the right answer to that, agreed, and that should be rather straight-forward. Note however the presence of xml_is_well_formed in the back-branches, where there is an extra xmlParseMemory that needs to be switched to xmlReadMemory but that's a simple switch. Would you prefer if I do it? -- Michael
Commits
-
xml2: Replace deprecated routines with recommended ones
- 4b0e5d601291 12.19 landed
- bb418aeee270 13.15 landed
- 6fa5e67e832b 14.12 landed
- 689ba4f1c406 15.7 landed
- 7c93f31dee5f 16.3 landed