For reference, what projects are doing: https://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=1ae6a7be8abab4b13520679f42c6cc8e2fb57d05
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/po/POTFILES.skip?id=66c3b673e32b7d055349a2a96ca2c2dfbbfc03ba https://git.gnome.org/browse/gnome-control- center/commit/po/POTFILES.skip?id=5e0db6aaeb0e88161a0bb76fac5293c4dec22ed1 https://cgit.freedesktop.org/geoclue/commit/po/POTFILES.skip?id=ece2a872c1b944cf24bd631d907c3b7cfcb484a9 ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to intltool in Ubuntu. https://bugs.launchpad.net/bugs/1117944 Title: intltool confused by separate build-dir Status in intltool: New Status in intltool package in Ubuntu: New Bug description: systemd uses 'intltool-update -m' from intltoolize in its 'make check'. $(top_srcdir)/po/POTFILES.skip contains the name of a generated file (src/core/org.freedesktop.systemd1.policy.in), which will be generated as $(top_builddir)/src/core/org.freedesktop.systemd1.policy.in. If $(builddir)==$(srcdir) than everything works fine. When they are different, there's no way to instruct intltool-update to skip the file. Since the name of the build directory is not known and can be arbitrary, there should be a way to instruct intltool-update to ignore files relative to the $(top_builddir), or something like that. One option would be to turn the file list into a list of globs (**/src/core/org.freedesktop.systemd1.policy.in would work perfectly in our case). To manage notifications about this bug go to: https://bugs.launchpad.net/intltool/+bug/1117944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp