meson: 1.0.0: `dist` targed does not check is po/POTFILES.in is up-to-date

Describe the bug On building just released gnome-disk-utility found that gnome-disk-utility-update-po fails because po/POTFILES.in is not up-to-date. https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/283 With GNU automake make dist-check is noit only forming dist tar ball but is checkig is it possible to build everything of such tar ball.

To Reproduce

git clone https://gitlab.gnome.org/GNOME/gnome-disk-utility/
cd gnome-disk-utility
meson setup --buildtype=plain build
meson dist build
meson gnome-disk-utility-update-po -C build

Expected behavior dist targed thould try to veryfi generated dist tart ball. Eventually shpuld be provided like with automake sist-check targe which part should be as well <project>-update-po.

system parameters

Is this a cross build or just a plain native build (for the same computer)? Native
what operating system (e.g. MacOS Catalina, Windows 10, CentOS 8.0, Ubuntu 18.04, etc.) Linux x86_64
what Python version are you using e.g. 3.8.0 3.8.16
what meson --version 1.0.0
what ninja --version if it’s a Ninja build 1.11.1

About this issue

Original URL
State: closed
Created a year ago
Comments: 22 (12 by maintainers)

Most upvoted comments

No. Again, the timestamps embedded as POT-Creation-Date are updated every time, regardless of whether anything else changed.

If it is true that is another gettext issue.

I gave it a try, and it is true, POT-Creation-Date change every time update-po target is rebuild. I think this could be worked around in Meson by comparing old and new po file, and it the only diff is that line it could leave the file untouched. Googling for that issue I found many projects that does that already:

If we do that, then I think it makes sense to run update-po as dist script.

xclaesse on Feb 15, 2023