Bug#1028132: marked as done (transition: hunspell)
Your message dated Sun, 16 Jul 2023 18:56:47 +0200
with message-id <ZLQhTwJAHGmtNYAg@ramacher.at>
and subject line Re: Bug#1028132: now ready
has caused the Debian Bug report #1028132,
regarding transition: hunspell
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1028132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028132
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: hunspell
- From: Rene Engelhard <rene@debian.org>
- Date: Sat, 7 Jan 2023 16:45:35 +0100
- Message-id: <Y7mTn2wI+LOex/La@rene-engelhard.de>
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
Blocks: -1 by 1028124
Hi,
not a real transition but given that it involves Breaks: and a
dependency bump with shlibs.local...
hunspell 1.7.2 changed some *internal* headers. Unfortunately it broke
hunspell-ko (fixed in 1.7.2+really1.7.2-4) and r-cran-hunspells test.
r-cran-hunspell included a copy of those internal headers and thus
breaks when built against the newer ones. (And I assume will do so when
built against the new ones against the old one.)
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028124 for the
gory details.
I added Breaks: to hunspell 1.7.2+really1.7.2-5 and added a shlibs.local
to my proposed solution to #1028124
Changes in hunspell 1.7.2 according to upstream github announcement:
--- snip ---
Crash fixes, code clean-up in ~200 commits
tdf#136306 don't accept/suggest typos as 3-or-more-word compound words
Prepare optional spelling mode of LibreOffice to not accept/suggest not dictionary-based words as compound words (#517)
Merge in weblate translations
--- snip ---
Regards,
Rene
--- End Message ---
--- Begin Message ---
- To: Rene Engelhard <rene@debian.org>, 1028132-done@bugs.debian.org
- Subject: Re: Bug#1028132: now ready
- From: Sebastian Ramacher <sramacher@debian.org>
- Date: Sun, 16 Jul 2023 18:56:47 +0200
- Message-id: <ZLQhTwJAHGmtNYAg@ramacher.at>
- In-reply-to: <a0f0f823-714c-c12a-9154-2cf7cc0406b3@debian.org>
- References: <Y7mTn2wI+LOex/La@rene-engelhard.de> <ddc152e0-6976-7772-9c0c-7ce16940d9ed@debian.org> <ZJoN/36fYCsfWAjR@ramacher.at> <Y7mTn2wI+LOex/La@rene-engelhard.de> <a0f0f823-714c-c12a-9154-2cf7cc0406b3@debian.org>
On 2023-06-27 06:31:28 +0200, Rene Engelhard wrote:
> Hi,
>
> Am 27.06.23 um 00:15 schrieb Sebastian Ramacher:
> > On 2023-06-18 13:57:01 +0200, Rene Engelhard wrote:
> > > Hi,
> > >
> > > hunspell-dict-ko was fixed/worked around the issue (0.7.94-1) so we can do
> > > this now.
> > >
> > > As said it's a no-op for anything except r-cran-hunspell which also is
> > > prepared in experimental together with hunspell itself.
> > >
> > > I might add a libhunspell-private-dev package later when I figured out how
> > > to best prevent this by adding a strict dependency there instead of
> > > hardcoding it... But even without that it's better to not have a copy of
> > > private headers in r-cran-hunspell.
> > >
> > > Can I upload to unstable?
> > Please go ahead
>
> Uploaded, thanks.
hunspell migrated.
Cheers
--
Sebastian Ramacher
--- End Message ---
Reply to: