Ticket #44143

Msys2: Sometimes outdated .gmo files from earlier build used

Open Date: 2022-03-18 14:04 Last Update: 2022-03-21 12:59

Reporter:
Owner:
Type:
Status:
Closed
Component:
MileStone:
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
Fixed
File:
2

Details

Seen with S3_0 msys2 snapshot build: Latest translation updates were not working in the build. We are supposedly making complete builds (i.e., start with an empty build dir), but the gettext stuff creates .gmo files to the source directory, and those are not cleared between builds. I suspect we can sometimes end up using .gmo from an earlier build.

Ticket History (3/8 Histories)

2022-03-18 14:04 Updated by: cazfi
  • New Ticket "Msys2: Sometimes outdated .gmo files from earlier build used" created
2022-03-18 14:10 Updated by: cazfi
Comment

It's somewhat likely that this is a regression introduced by #43891 - now not regenerating translation files early enough from the point of view of this ticket. That would mean this is a regression since 3.0.0 -> 3.0.1 blocker?

2022-03-18 14:53 Updated by: cazfi
2022-03-18 20:12 Updated by: cazfi
Comment

Apperently the 'make install' step in msys2 Makefile does not produce translation files at all, nor does it error if they are not available for installing. If they are not present, it just does not install them. I've not seen such problems on linux, with the 'make install' as the only step to take.

So, we will need to have update-po back before make install, to produce .gmo files. Maybe we can 'git checkout' po-files after it, to avoid #43891 ? Going to test that.

2022-03-19 15:55 Updated by: cazfi
  • Owner Update from (None) to cazfi
  • Resolution Update from None to Accepted
Comment
2022-03-21 12:59 Updated by: cazfi
  • Status Update from Open to Closed
  • Resolution Update from Accepted to Fixed

Edit

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » Login