Bug#867623: heirloom-mailx is not an alternative for /usr/bin/mailx

2019-02-18 Thread Adrian Zaugg
On Thu, 20 Jul 2017 15:41:50 +0200 Steffen Nurpmeso wrote: > |Oy. I gather, then, that s-nail cannot be an alternative unless some > |sort of political settlement is brokered, which may never happen. Alas. > > That was my impression at least. Of course this MUA is still very > restricted,

Bug#867623: heirloom-mailx is not an alternative for /usr/bin/mailx

2017-07-20 Thread Steffen Nurpmeso
Norman Ramsey wrote: |>|Sorry, I think I misunderstand something. I would think that |>|participation in update-alternatives would be a packaging issue, not |>|an upstream issue. And I don't see a connection to custom headers... |> |> It was my understanding that we

Bug#867623: heirloom-mailx is not an alternative for /usr/bin/mailx

2017-07-19 Thread Norman Ramsey
> |Sorry, I think I misunderstand something. I would think that > |participation in update-alternatives would be a packaging issue, not > |an upstream issue. And I don't see a connection to custom headers... > > It was my understanding that we have been removed as an > alternative

Bug#867623: heirloom-mailx is not an alternative for /usr/bin/mailx

2017-07-19 Thread Steffen Nurpmeso
Norman Ramsey wrote: |> Norman Ramsey wrote: |> ... |>|I expected /usr/bin/heirloom-mailx to be an alternative on this menu. |>| |>|This is possibly the same bug as 858080, but I don't know enough |>|Debian jargon to know for sure. |> |> The just

Bug#867623: heirloom-mailx is not an alternative for /usr/bin/mailx

2017-07-18 Thread Norman Ramsey
> Norman Ramsey wrote: > |I upgraded from jessie to stretch, and I expected to continue using > |heirloom-mailx as my implementation of mailx. But my system was > |somehow switched to bsd-mailx. Worse, update-alternatives is not > |capable of changing back: > ...

Bug#867623: heirloom-mailx is not an alternative for /usr/bin/mailx

2017-07-17 Thread Steffen Nurpmeso
Norman Ramsey wrote: |I upgraded from jessie to stretch, and I expected to continue using |heirloom-mailx as my implementation of mailx. But my system was |somehow switched to bsd-mailx. Worse, update-alternatives is not |capable of changing back: ... |I expected

Bug#867623: heirloom-mailx is not an alternative for /usr/bin/mailx

2017-07-07 Thread Norman Ramsey
Package: heirloom-mailx Version: 14.8.16-1 Severity: normal Dear Maintainer, I upgraded from jessie to stretch, and I expected to continue using heirloom-mailx as my implementation of mailx. But my system was somehow switched to bsd-mailx. Worse, update-alternatives is not capable of changing