Same as I replied to you 2 weeks ago, you can unsubscribe via:
https://sourceforge.net/projects/apertium/lists/apertium-stuff/unsubscribe
In addition, every email from the list has a footer with links to this
information.
-- Tino Didriksen
On Wed, 15 Dec 2021 at 07:51, Ramansh Sharma wrote:
This is awesome. Thank you for setting it up, Xavi!
I set up some Docker Hub based automation when I first created the
repository but I'm not surprised that it's bitrotten. It was never
particularly stable. I suspect GH Actions will be far superior.
A great extension here would be to set up
> Please unsubscribe me from this list. Or please tell me how to.
https://sourceforge.net/projects/apertium/lists/apertium-stuff/unsubscribe
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
I am begging the moderator for this conversation. Please unsubscribe me
from this list. Or please tell me how to.
--
Ram
On Wed, Dec 15, 2021 at 2:03 AM Xavi Ivars wrote:
> And, in the meantime, here you have updated images for apertium/base and
> apertium/apy. They'll build on any commit to
And, in the meantime, here you have updated images for apertium/base and
apertium/apy. They'll build on any commit to master, plus once a week
apertium/base
To use them, the same way as it's done with Docker Hub images
docker pull ghcr.io/apertium/apy:latest
Missatge de Xavi Ivars del dia
While looking back at this, I realized it's been more than 7 months that we
haven't published any image to DockerHub, to the point that using
apertium/apy:latest as a base image may not work in some cases (due to
using a quite old debian version, being oldstable instead of stable now).
For now,
Hi all,
I've been doing a bit of cleanup on apertium-apy, and realized that Travis
hasn't been working for a while.
To solve for it, I did an initial integration with GithubActions.
I haven't spend too much time on it (Tino mentioned on IRC he's working on
a better CI for all modules) but I
