Re: Should we retire the mailx package?
I've opened [1], please take a look. After it is merged, I'll start the package retirement process for mailx. Thanks, Nikola [1] https://src.fedoraproject.org/rpms/s-nail/pull-request/3 -- ___ 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
Re: Should we retire the mailx package?
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 wrote: > On Mon, 11 Dec 2023 at 12:03, Jonathan Wakely wrote: > > > > On Fri, 8 Dec 2023 at 18:47, Adam Williamson > 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@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 > -- ___ 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
Re: Should we retire the mailx package?
On Mon, 11 Dec 2023 at 12:03, Jonathan Wakely wrote: > > On Fri, 8 Dec 2023 at 18:47, Adam Williamson > 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@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
Re: Should we retire the mailx package?
On Fri, 8 Dec 2023 at 18:47, Adam Williamson 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. 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@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
Re: Should we retire the mailx package?
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. 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 -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org https://www.happyassassin.net -- ___ 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
Re: Should we retire the mailx package?
I'm definitely in favor. I hit this broken step a while back myself. ;( Hopefully the current maintainers are on board with this? kevin signature.asc Description: PGP signature -- ___ 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
Re: Should we retire the mailx package?
On Fri, 2023-12-08 at 13:18 -0500, Neal Gompa wrote:
> >
> > Can we retire the mailx package, and then update s-nail with:
> >
> > Provides: mailx = %{version}-%{release}
> >
> > (this would work fine because mailx is at 12.5 and s-nail forked
> > from
> > that and is now at 14.9, so upgrading would be straightforward)
> >
> > Should I submit a self-contained change proposal to do this?
>
> Yes, please!
I'm also +1 for this proposal. When I came back to Fedora after some
dalliance with Debian (a few years ago now), the difference in mailx
implementations caused me some heartburn. And then I found s-nail and
it was fine. But it was not clear (then) that they were compatible. I
was just looking for something simple to send something via SMTP from
the command line.
thanks,
--
Martin Jackson
--
___
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
Re: Should we retire the mailx package?
On Fri, Dec 8, 2023 at 12:34 PM Jonathan Wakely
wrote:
>
> Today I learned (the hard way) that Fedora's mailx package (aka
> Heirloom mailx) is ancient and buggy. Upstream has been dead for over
> a decade and features documented in its man page don't work. The good
> news is that Fedora (and RHEL and CentOS) already have s-nail, which
> was forked from it ages ago and is still actively developed. They both
> provide the POSIX mailx command, configurable via
> /etc/alternatives/mailx, and support almost the same options/config
> etc.
>
> But 'dnf install mailx' gives you the bad version, and 'dnf search
> mailx' doesn't show s-nail at all. So unless you happen to know s-nail
> exists, or spend a while googling to see if Heirloom mailx is still
> maintained, you'll never learn about the good one.
>
> Is there any reason to keep both packages, when one is old and buggy
> and the other is an improved version of the same thing?
>
> Can we retire the mailx package, and then update s-nail with:
>
> Provides: mailx = %{version}-%{release}
>
> (this would work fine because mailx is at 12.5 and s-nail forked from
> that and is now at 14.9, so upgrading would be straightforward)
>
> Should I submit a self-contained change proposal to do this?
Yes, please!
--
真実はいつも一つ！/ Always, there's only one truth!
--
___
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
Should we retire the mailx package?
Today I learned (the hard way) that Fedora's mailx package (aka
Heirloom mailx) is ancient and buggy. Upstream has been dead for over
a decade and features documented in its man page don't work. The good
news is that Fedora (and RHEL and CentOS) already have s-nail, which
was forked from it ages ago and is still actively developed. They both
provide the POSIX mailx command, configurable via
/etc/alternatives/mailx, and support almost the same options/config
etc.
But 'dnf install mailx' gives you the bad version, and 'dnf search
mailx' doesn't show s-nail at all. So unless you happen to know s-nail
exists, or spend a while googling to see if Heirloom mailx is still
maintained, you'll never learn about the good one.
Is there any reason to keep both packages, when one is old and buggy
and the other is an improved version of the same thing?
Can we retire the mailx package, and then update s-nail with:
Provides: mailx = %{version}-%{release}
(this would work fine because mailx is at 12.5 and s-nail forked from
that and is now at 14.9, so upgrading would be straightforward)
Should I submit a self-contained change proposal to do this?
--
___
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
