Gabriel Wicki <[email protected]> writes: > what is the fastest/most efficient/easiest way to find a commit breaking > some package? how do you do it? do you just guess and then half the > difference log(n) times until you find the commit? > > i am writing some how-tos for our contributing chapter and/or cookbook > and am interested in your wisdom!
The data service can display the build status for a package over time, and give information on what commit ranges that corresponds to, e.g. https://data.guix.gnu.org/repository/1/branch/master/package/hello/output-history?output=out&system=aarch64-linux&target=none This is only helpful when the breaking change causes the package to fail to build though, although it could reduce the number of commits you need to check when bisecting even if the change doesn't cause the package to break.
signature.asc
Description: PGP signature
