Hi,
Using a Debian based image will generate more efforts from our side, as the
system is already running on CentOS 8. Furthermore, I don’t think we’ll have an
updated version of gettext in Debian repository (did not check yet).
We have another issue with the actual image: it’s based on CentOS 8,
The branch 'tracker-3.3' was created pointing to:
5ac6e36... Merge branch 'wip/carlosg/doc-updates' into 'master'
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
The branch 'tracker-miners-3.3' was created pointing to:
d6f6b4c... Merge branch 'wip/carlosg/status-output-fix' into 'master'
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-i18n
Le 24.04.22 à 09:57, Guillaume Bernard a écrit :
Hi,
Using a Debian based image will generate more efforts from our side, as the
system is already running on CentOS 8.
I don't think this is the real issue. D-L was running on Debian during
years without problem. But AFAIK GNOME sysadmin prefer
Hi,
What I meant is that, by using Fedora instead of Debian, we will use the same
packages and we can reuse almost 80% of the Dockerfile that we currently use. I
suppose we can only change the source Docker image and adjust a few things.
Ok, good news, I did not checked before saying that, as I s
Reading through the linked issues, nobody has bisected gettext yet to
identify what changed. That's probably the next step towards getting
this fixed.
Michael
___
gnome-i18n mailing list
gnome-i18n@gnome.org
https://mail.gnome.org/mailman/listinf
Le 24.04.22 à 23:47, Michael Catanzaro a écrit :
Reading through the linked issues, nobody has bisected gettext yet to
identify what changed. That's probably the next step towards getting
this fixed.
I don't agree with that, we really need a full gettext 0.21 version, not
a patched 0.19.x v
