Hi guys, I am ok with retiring the mailx package so s-nail can become the primary
supplier of the mailx command.
On Mon, Dec 11, 2023 at 1:05 PM Jonathan Wakely <jwakely@xxxxxxxxxx> wrote:
On Mon, 11 Dec 2023 at 12:03, Jonathan Wakely <jwakely@xxxxxxxxxx> wrote:
>
> On Fri, 8 Dec 2023 at 18:47, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote:
> >
> > On Fri, 2023-12-08 at 10:38 -0800, Kevin Fenzi wrote:
> > > I'm definitely in favor. I hit this broken step a while back myself. ;(
> > >
> > > Hopefully the current maintainers are on board with this?
> >
> > Yeah, honestly, I'm not sure a Change is the right way to go about
> > this, it seems like it could just be handled between maintainers.
> > nforro - who maintains mailx - has not committed to it for two years,
> > but is very active on other packages (adding him to CC). If he is OK
> > with the change, I would think you could just go ahead and do it (have
> > nforro retire mailx) without needing to go through the Change process.
>
> I CC'd him (and tkorbar) on the first mail in this thread, and I only
> started this thread after emailing them directly to discuss it (I
> probably should have mentioned that I'd already run it by them).
> Nikola suggested in that private discussion that retiring mailx was
> probably the way to go, so I started this thread.
>
> > If you file a Change, I think all that will happen is that a lot more
> > bureaucracy will happen before somebody says "hey, we'd better ask
> > nforro about this" anyway. :D
>
> I think he's already on board with the change, and I think everybody
> would be happier to Just Do It without a change proposal. I just
> wanted to start a discussion and make sure the right process was
> followed.
... and of course to check that nobody would object, on the grounds
that they need the crufty mailx for some reason.
> It sounds like I'm not the only person to waste time scratching my
> head at the heirloom-mailx fossil, and so we should just retire it!
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
