Your message dated Tue, 15 Sep 2020 22:31:53 +0200
with message-id <a7f3e484-7b89-12f8-5d0f-d30f5ccc4...@debian.org>
and subject line Re: Bug#947979: enchant -> enchant-2 transition: Time to purge
enchant(1)?
has caused the Debian Bug report #947979,
regarding transition: enchant-2
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 ow...@bugs.debian.org
immediately.)
--
947979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: enchant-2
Severity: wishlist
Version: 2.2.7+repack1-1
X-Debbugs-CC: pr...@debian.org
Since enchant 1.x is not really maintained by upstream, it might be
reasonable to request a (manual) transition from enchant1 to enchant2
after enchant-2 enters Testing.
This issue might not be suitable to be submitted as a bug against
enchant-2 package; please feel free to properly reassign it. At least
this will make the maintainers for both enchant and enchant-2 to be
aware of it.
--
Best,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Hi,
On 03-09-2020 16:25, Boyuan Yang wrote:
> Now, according to
> https://release.debian.org/transitions/html/enchant-2.html , package
> xenur ( https://tracker.debian.org/pkg/xneur ) is the last package that
> (build-)depends on enchant(1). This package has been under FTBFS status
> due to GCC-10 since July and was removed in Testing.
All enchant(1) stuff has been removed from testing (several weeks ago),
so this bug can be closed.
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
