Thanks Evgeni for the quick response. It's gratifying to see a debian
maintainer so alert and responsive.
This may *possibly* be what some folks say is _my bad_, so let me add
some details, that I didn't realize until after I hit 'send'.
On 2017-07-21 13:32, Evgeni Golov wrote:
> On Fri, Jul 21, 2017 at 07:02:50AM -0400, Boruch Baum wrote:
> > Upon upgrading `mutt' from the stable to testing repositories, mutt
> > ceased to function, offering the following error message:
>
> There is no mutt 1.7.2-1 in testing. Did you mean upgrading
> jessie→stretch?
I meant upgrading from 1.5.xx to 1.7.2-1.
This next indented section is tangential, but important:
My bug report may be valid for debian, or not. The main problem with
my report is that it was intended to be sent to your ?evil? or at
least "more-challenged" twin, the devuan project. I am running their
version of 'stable' which has mutt 1.5.xxx and upgraded to their
'testing' version 1.7.2-1.
Their package `reportbug' in their stable repository sends bug reports
to debian, not devuan (aaargh!). I have since upgraded to their
'testing' version, and filed a bug report against their 'stable'
version, but I see that even their 'testing' version is flawed in that
it seems to always send reports to BOTH devuan and debian (aaargh!).
So, I will file another bug report (manually) to them.
It might be a good idea if you could join me in complaining to the
devuan folks. For me this is embarassing, but really, I wasn't
expecting this incompetence.
> mutt has a dependency on libnotmuch4, libnotmuch4 has a dependency on
> libxapian30, mutt is not using any xapian directly AFAIK.
This issue is that libnotmuch4 links to a whole lot of xapian symbols
that will be undefined until the correct version of the xapian library
is installed.
> so we might discuss this as being a not-strong-enough dep between
> libnotmuch4 and libxapian30, but not a serios bug in mutt.
Agreed. Can you re-assign it, or should I re-file, or should we drop
this? There is still the possibility that this really isn't a debian
issue at all, but a devuan one, but its something easy to check.
Apologies again,
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
