Bug#861141: enchant: New upstream release (1.6.1)

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#861141: enchant: New upstream release (1.6.1)

Laurent Bigonville-5
Source: enchant
Version: 1.6.0-11
Severity: wishlist

Hi,

It seems that the upstream website has moved to
https://abiword.github.io/enchant/

There is a new release there:

1.6.1 (February 6, 2017)
------------------------

Improvements to the enchant-ispell front-end, which is now a working ispell replacement.
Unit tests run on all platforms.
Various bug fixes and code clean-up.

Would be a good idea to package it I guess.

Regards,

Laurent Bigonville

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Reply | Threaded
Open this post in threaded view
|

Bug#861141: enchant: New upstream release (2.1.0)

Timo Jyrinki-5
There are also new 2.0.0 and 2.1.0 releases now, Enchant being actively
developed again.

Reply | Threaded
Open this post in threaded view
|

Bug#861141: enchant: New upstream release (2.1.0)

Tim Lunn-2
In reply to this post by Laurent Bigonville-5
Since version 2.1.3 enchant 2 has support for parallel installation.

Given the API/ABI breaks it would probably be best to package this as a
separate enchant2 source package


NEWS:

2.1.3 (November 26, 2017)
--------------------------

This release adds support for parallel installation with other major
versions of Enchant, and fixes a crash in the Voikko provider when it has no
supported languages.

Reply | Threaded
Open this post in threaded view
|

Bug#861141: WIP 2.2.3 debdiff

Tim-9
In reply to this post by Laurent Bigonville-5
I am attaching a WIP debdiff for enchant2 as a new source package.

The current gnulib in Debian is too old to build this. the included
bootstrap script from enchant pulls gnulib from git which works and
builds but not really a suitable solution for packaging.


Either gnulib package needs to be updated or upstream could include a
snapshot of gnulib in their tarballs?



enchant2.debdiff (23K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#861141: enchant: New upstream release (2.1.0)

Laurent Bigonville-3
In reply to this post by Timo Jyrinki-5
On Tue, 5 Sep 2017 13:12:25 +0300 Timo Jyrinki <[hidden email]> wrote:
 > There are also new 2.0.0 and 2.1.0 releases now, Enchant being actively
 > developed again.

What's are the plans for enchant?

I see that enchant 2.1.2 has been packaged in experimental.

The transition involves quite some packages
(https://release.debian.org/transitions/html/auto-enchant.html), Timo
did you try to do an archive rebuild? to see existing packages can use
version 2 of the library? do you know if the porting effort is big?

Any reasons why libenchant2 has Breaks/Replaces with libenchant1c2a and
are not co-installable?

Reply | Threaded
Open this post in threaded view
|

Bug#861141: enchant: New upstream release (2.1.0)

Timo Jyrinki-4
2018-04-18 18:42 GMT+03:00 Laurent Bigonville <[hidden email]>:
> On Tue, 5 Sep 2017 13:12:25 +0300 Timo Jyrinki <[hidden email]> wrote:
>> There are also new 2.0.0 and 2.1.0 releases now, Enchant being actively
>> developed again.
>
> What's are the plans for enchant?

I think no plans (time/resources) known at the moment, but the path
would be clear for someone to pursuit. Prach made enchant LowNMU so
it'd be easier now for anyone to hop in.

> I see that enchant 2.1.2 has been packaged in experimental.
>
> The transition involves quite some packages
> (https://release.debian.org/transitions/html/auto-enchant.html), Timo did
> you try to do an archive rebuild? to see existing packages can use version 2
> of the library? do you know if the porting effort is big?

I only tested rebuilding some and reported on debian-devel
https://lists.debian.org/debian-devel/2018/01/msg00178.html

> Any reasons why libenchant2 has Breaks/Replaces with libenchant1c2a and are
> not co-installable?

That was probably just before it became possible to package enchant2
as a separate source package for parallel installation, and it should
now be allowed.

So the path forward would be to use Tim's excellent enchant2 work, but
before that a newer snapshot of the gnulib [1] should be packaged.

[1] https://tracker.debian.org/pkg/gnulib

-Timo