Re: [Buildroot] [PATCH 2025.02.x] package/postgresql: security bump to v17.11
Raphaël Mélotte via buildroot <[email protected]>
| Newsgroups | net.busybox.buildroot |
|---|---|
| Message-ID | <[email protected]> |
Hi Peter, On 8/18/26 11:18 AM, Peter Korsgaard wrote: > > > Assisted-by: Claude:claude-sonnet-5 > > We don't really use assisted-by tags in Buildroot. Did you really reach > out to a LLM to change a 10 to an 11? > A bit more than that but yes, I used it to: - Bump the package version - Fetch the new tarball hash - Download the new tarball - Check for changes in the copyright file - Generate the commit title - Build the list of CVEs fixed in this release based on the release notes - Generate the commit message from the list Even though it's not a daunting task, in this case building the list of CVEs is probably the one that's the hardest to do in a generic way. The CVEs are mentioned in the release notes ([1]) but they are scattered across the text which means, short of copy-pasting them one by one, a bit of scripting specific to this page is needed to retrieve them all. They are also available from a news post in a way that's easier to use ([2]), but from that post I don't find it immediately clear whether all 28 CVEs affected each release mentioned, or only some of them. So I wanted to see if Claude could help me in this case and it did. Of course I still hand-checked the result, as I would do regardless of how the change was produced. Since I used an LLM to help me, I preferred to make it explicit in the commit message. I could mention it in a free-form instead of using a tag, but since this tag exists elsewhere I thought why not use it instead. Kind regards, Raphaël [1]: https://www.postgresql.org/docs/release/17.11/ [2]: https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/ _______________________________________________ buildroot mailing list [email protected] https://lists.buildroot.org/mailman/listinfo/buildroot