On 31 October 2017 at 16:51, Jaroslaw Staniek <stan...@kde.org> wrote: > On 31 October 2017 at 17:27, Jonathan Riddell <j...@jriddell.org> wrote: >> There's some fancy stuff in the translations extraction script for kproperty >> >> https://cgit.kde.org/kproperty.git/tree/src/Messages.sh >> >> This breaks the Neon builds which try to parse those Messages.sh files >> to download translations >> https://build.neon.kde.org/job/xenial_unstable_calligra_kproperty_src/89/console >> > > Hi Jonathan, > I've found it less intrusive than removing git history by moving cpp > files around. The review is here: https://phabricator.kde.org/D8230. > > I wonder how the shell scripts are parsed, what are the assumptions. > In the neon link releaseme only shows me internal backtrace. > Maybe we can add metadata that you can support instead of parsing scripts.
releaseme needs the name of the .pot files spelled out, can I change it to make it explicitly call them? http://embra.edinburghlinux.co.uk/~jr/tmp/DIFF >> And I'm not sure scripty is happy with it either, there's no >> kpropertycore_qt.pot or kpropertywidgets_qt.pot >> >> https://websvn.kde.org/branches/stable/l10n-kf5/templates/messages/extragear-libs/ > > IIRC there are no translations because the lib has not been approved > via kdereview yet. I'm talking nonsense the files are there. Jonathan
