Greg, Mathieu Othacehe 写道: > The update is already present on core-updates branch, Sorry for the duplicate work! How were you to've known this, you ask? $ guix refresh --list-dependent PACKAGE or ‘-l’ for short will list the number of rebuilds that a hash change in PACKAGE would trigger. If it's higher than 300, the patch belongs on the ‘staging’ or ‘core-updates’ branches instead of ‘master’. The exact numbers are in the ‘Submitting Patches’ section of the Guix manual. In practice, it's not always clear-cut. A patch that rebuilds fewer than 300 packages but includes IceCat, Ungoogled Chromium, and LibreOffice probably belongs on ‘staging’ regardless. A patch that rebuilds 350 (fast-building) Perl packages might be OK for master. It's good practice to include the branch name (e.g., ‘[PATCH core-updates]’) when submitting patches not suitable for master. Kind regards, T G-R