On Tue, Mar 25, 2025, at 7:51 PM, Michael J Gruber wrote:
> Adam Williamson venit, vidit, dixit 2025-03-25 17:07:25:
>> On Tue, 2025-03-25 at 15:34 +0100, Michael J Gruber wrote:
>> > Am Di., 25. März 2025 um 15:20 Uhr schrieb Miro Hrončok 
>> > <mhron...@redhat.com>:
>> > > 
>> > > On 25. 03. 25 15:16, Neal Gompa wrote:
>> > > > On Tue, Mar 25, 2025 at 10:07 AM Benson Muite
>> > > > <benson_mu...@emailplus.org> wrote:
>> > > > > 
>> > > > > Aspell was deprecated with the reason that it is no longer under 
>> > > > > active development:
>> > > > > https://fedoraproject.org/wiki/Changes/AspellDeprecation
>> > > > > 
>> > > > > However, it is undergoing maintenance and improvements:
>> > > > > https://github.com/GNUAspell/aspell
>> > > > > 
>> > > > >   Is there a way to un-deprecate a deprecated package?
>> > > > > 
>> > > > 
>> > > > You need to make a new Change proposal for it.
>> > > I don't think that should be required.
>> > > 
>> > > If you maintain the package, drop the deprecated() provides.
>> > > 
>> > > If you don't, talk to the maintainer.
>> > > 
>> > 
>> > "Retired Fedora packages (rawhide branch retired) require a re-review
>> > if they are retired for more than eight weeks or if there is no
>> > previous review of the package. Submit a review request (a new
>> > bugzilla ticket) and have the package approved by a reviewer as if it
>> > were new to Fedora."
>> > 
>> > https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#:~:text=To%20unretire%20a%20EPEL%20branch,the%20link%20to%20re%2Dreview.
>> 
>> A review request is not a Change proposal, they're entirely separate
>> things.
>
> Yes, sure.
>
> And no, I didn't say they are.
>
>> But yes, if it's been retired for more than eight weeks, a new
>> review request is required before it can be re-activated.
>
> That is what I quoted above including the reference.
>
> Also, you left out the part where I noticed that neither change proposal
> nor package review are required here since the package hasn't even been
> retired yet.
>
> Now on to the really hard question you left un-answered:
>
>> Also, is undeprecation = precation? I'm asking out of precaution, obviously.
>
> That, plus whether aspell is worth undeprecating.
>

enchant still uses it:
https://src.fedoraproject.org/rpms/enchant2/blob/rawhide/f/enchant2.spec

Trying to rebuild to see if hunspell can be used instead to allow novelwriter 
to build:
https://bugzilla.redhat.com/show_bug.cgi?id=2354830

At present it fails:
https://download.copr.fedorainfracloud.org/results/fed500/novelwriter/fedora-rawhide-x86_64/08819537-novelwriter/builder-live.log.gz

Other dependencies on f41 are limited:
eiskaltdcpp-qt
enchant-aspell
kf5-sonnet-aspel
perl-Text-Aspell
php-pspel
recoll
yagf

-- 
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to