Re: [Apertium-stuff] Changes on apertium-apy

[Tino Didriksen]

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:

> I am begging the moderator for this conversation. Please unsubscribe me
> from this list. Or please tell me how to.
>
> --
> Ram
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Changes on apertium-apy

[Sushain Cherivirala]

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 automatic publishing to PyPi
when apertium-apy has a new version pushed. Looks like there's a guide
.
I might give it a shot this weekend if I have a chance.

On Tue, Dec 14, 2021 at 5:30 AM Xavi Ivars  wrote:

> 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, I've added another Github Action that will build and push to the
> GitHub Container Registry, and I'll do the same to push "apertium/base".
>
> I'll wait for Sushain's answer to also push those images to Docker Hub
>
>
>
> Missatge de Xavi Ivars  del dia dj., 9 de des. 2021
> a les 23:02:
>
>> 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 didn't want to allow merges with
>> tests failing.
>>
>> I'd love if those of you who have more expertise on Apy could take a look
>> at this:
>>
>> https://github.com/apertium/apertium-apy/pull/184
>>
>> Other things I've seen not properly working on that repo:
>> - Pushes to dockerhub
>> - Pushes to Pypi?
>> - Not sure if with my changes I broke the code coverage check
>>
>> If there are no objections, I'll probably merge it in the next couple of
>> days. Even if this is just an starting point, it should be already better
>> than what we had (no checks running at all)
>> --
>> < Xavi Ivars >
>> < http://xavi.ivars.me >
>>
>
>
> --
> < Xavi Ivars >
> < http://xavi.ivars.me >
>
___
Apertium-stuff mailing list
Apertium-stuff@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Re: [Apertium-stuff] Changes on apertium-apy

[Kevin Brubeck Unhammer]

> 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
https://lists.sourceforge.net/lists/listinfo/apertium-stuff