Am Sonntag, den 19.04.2020, 22:16 +0200 schrieb David Kastrup: > pkx1...@posteo.net > writes: > > > Hello, > > > > On 19/04/2020 17:53, David Kastrup wrote: > > > v.villen...@gmail.com > > > writes: > > > > > > > On 2020/04/11 09:44:26, Valentin Villenave wrote: > > > > > What could be the cause? > > > > > > > > So, pushed as > > > > https://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=0cfef7069e86f85ad392f5c4bc63f6c4801aa2c9 > > > > > > > > > > > > V. > > > > > > > > https://codereview.appspot.com/557640051/ > > > > > > > > > > Breaks my patchy again. Whose patchy was comfortable moving it from > > > staging to master? > > > > > > > Mine. > > Ok, by now it has been determined that the breakage on my system likely > depends on a particular fontconfig version. However, there are a few > other problems with that regtest that should likely show with Guile-2 > (sometimes?). I'll revert for now so that master builds for everyone > again. That does not preclude a fixed variant to make it into master at > a later point of time.
To avoid this from happening again, can we please have the rule that whoever reverts a commit or backs it out of staging is to provide guidance on what's actually wrong? My feeling is that we could have had this analysis last week already.
signature.asc
Description: This is a digitally signed message part
