Hi
On 10-06-18 15:51, James McCoy wrote:
> Is there any work being planned/done to help ensure the versions tested
> are what's expected?
Yup. See ¹ if your extremely interested.
> A fix has been merged into upstream lua-nvim and a release should be
> happening once some technicalities are worke
On Wed, Jun 06, 2018 at 02:19:35PM +0200, Paul Gevers wrote:
> Unfortunately we did have that mirror issue and the regression went
> unnoticed.
Is there any work being planned/done to help ensure the versions tested
are what's expected?
> You as the lua-nvim maintainer
I'm not actually the lua-n
Hi James,
On 06-06-18 13:59, James McCoy wrote:
> On Sat, Jun 02, 2018 at 08:44:26PM +0200, Paul Gevers wrote:
>> Recently your autopkgtest¹ started failing due to a new version of
>> libuv1.
>
> So, a library change causes one of its users to break and the user is
> what gets the bug? Why is th
On Sat, Jun 02, 2018 at 08:44:26PM +0200, Paul Gevers wrote:
> Recently your autopkgtest¹ started failing due to a new version of
> libuv1.
So, a library change causes one of its users to break and the user is
what gets the bug? Why is this not a bug against the library?
Cheers,
--
James
GPG Ke
Source: lua-nvim
Version: 0.0.1-26-3
User: debian...@lists.debian.org
Usertags: needs-update
Dear maintainers,
Recently your autopkgtest¹ started failing due to a new version of
libuv1. Unfortunately the autopkgtest integration with the migration
software didn't catch this (the mirror that *was*
5 matches
Mail list logo
