Re: stable/2.22 has branched; master is 2.23.0

[Jonas Hahnfeld]

Am Montag, den 26.10.2020, 19:21 +0100 schrieb Jean-Charles Malahieude:
> Le 21/10/2020 à 20:12, Jonas Hahnfeld a écrit :
> > Am Mittwoch, den 21.10.2020, 20:01 +0200 schrieb Jean-Charles
> > Malahieude:
> > > since I'm trying to understand why
> > > snippets get translated in 2.21.7 on lilypond.org but not on my box
> > > (I've updated about 250 fr/texidocs and wanted to check how they appear)
> > > and check-translation gives me some strange messages like
> > > 
> > > warning: fr/essay/engraving.itely: 128 fatal: path
> > > 'Documentation/user/engraving.itely' does not exist in
> > > 'e9e5be535bfffbd50f33dfce3a8ee47b39e42bb5'
> > > 
> > > despite the fact I'm sure I was up to date with
> > > d75b86de1363084c28cebde4eea5fe56a657975a on 2020/09/12.
> > 
> > I get the same and see that commit hash in some French manuals, but the
> > canonical repo doesn't contain it. Maybe it was rebased to another
> > hash?
> > 
> 
> Found it: MR344 end MR347 touched both the original and translated 
> versions. I suspect this has deeply disturbed (or upset) 
> check-translation; I don't remember having seen such thing after 
> update-snippets.py or update-with-convert-ly.sh were run.

Yes, that !347 is quoted in commit d75b86de13 which introduced the
above commit hash. As you were running translation-status in commit
a2f89036bc, I suspected a rebase issue which would have kept the old
commit hash for some time in your local repository.

Of course, all of that doesn't matter after updating the commit hashes
to some value that allows translation-status to succeed ;-)

Jonas

signature.asc
Description: This is a digitally signed message part