> > https://tests.reproducible-builds.org/debian/rbuild/forky/amd64/ycmd_0+20240823+git8b61f19+ds-3.rbuild.log.gz > > > > Is this the Unicode 16 issue you refer to? > > Maybe there is a missing versioned build-depends somewhere? > > Sorry, yes, that is the issue (in reverse as the tests check for > specific attributes of those characters and they changed in 16). > > I thought unicode-data was already in testing… my bad. It now is through, > so the next try (sheduling it myself failed with HTTP 500) should work. > > I wanted to check if I can make the test work with both unicode > versions, but that turned out too hard for practically no gain, > so I didn't but forgot about bumping the version… noted for next time.
Thanks for your quick reply. Don't worry too much. Actually, this happens all the time, and I'm always in doubt about reporting it or not, because most of the time it fixes itself by just waiting a little for the build-dependencies to migrate to testing. I guess that a time-based approach (for example, waiting a month before reporting any kind of FTBFS in testing) would probably work here. Thanks.
