Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.devel > #78982

Re: [stretch] mc-4.8.18 broken, but fixed mc-4.8.19 released 5 March

From Felix Miata <mrmazda@earthlink.net>
Newsgroups linux.debian.devel
Subject Re: [stretch] mc-4.8.18 broken, but fixed mc-4.8.19 released 5 March
Date 2017-04-02 22:20 +0200
Message-ID <trU8F-5eX-5@gated-at.bofh.it> (permalink)
References (1 earlier) <toA6v-48t-35@gated-at.bofh.it> <trbuW-12o-9@gated-at.bofh.it> <trbEC-15S-7@gated-at.bofh.it> <trchk-1yJ-9@gated-at.bofh.it> <trT2W-4yO-19@gated-at.bofh.it>
Organization less than infinite

Show all headers | View raw


Wouter Verhelst composed on 2017-04-02 20:59 (UTC+0200):

> On Fri, Mar 31, 2017 at 05:24:53PM -0400, Felix Miata wrote:

>> Andrey Rahmatullin composed on 2017-04-01 01:49 (UTC+0500):

>>> On Fri, Mar 31, 2017 at 04:30:28PM -0400, Felix Miata wrote:

>>>> Andrey Rahmatullin composed on 2017-03-24 21:18 (UTC+0500):

>>>> > Start with reporting this bug at our BTS.
>>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858808

> (You got the version number wrong; I fixed that for you)

???

According to https://midnight-commander.org/ the current broken version is 
4.8.18, same as the app reports in its help screen. Filing a report from a 
different machine there's no good way to know whatever additions the package 
management system may have tacked on, or is there?

>>> As the bug severity is normal this won't be included in stretch, see
>>> https://release.debian.org/stretch/freeze_policy.html
>>> If you say it's broken maybe you've chosen a wrong severity?

>> The right severity doesn't exist: nuisance; for 5 years, because Stretch
>> will be LTS. MC doesn't have an alpha, beta, final release program, so its
>> bug fixes always have to wait for another release unless someone backports.

> Yes, but that's obviously not how Debian works. If you want to get this
> fix into Stretch, you have to convince the release managers and/or the
> Debian maintainer for mc that the bug is problematic enough that either
> backporting the fix for that bug, or updating the package to the new
> version, is worth it in spite of our release policy.

How does one go about that?

> Whether that is the case for this particular bug isn't entirely clear.
> This is a pretty annoying issue; but from reading the bug report that
> you filed upstream, it doesn't feel like it's something that occurs in
> the default configuration.
If you mean by "default configuration" a new installation and no previously 
saved settings rather than an upgrade, the bug is not apparent. However, after 
update from <4.8.18 to 4.8.18, the "default configuration" is to use the saved 
settings, which is why this bug manifests. The valid saved setting is improperly 
applied *every* time mc is started, not just on a first use.

> It requires a judgement call, which is for
> the maintainer and/or the release managers to make.-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Back to linux.debian.devel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

[stretch] mc-4.8.18 broken, but fixed mc-4.8.19 released 5 March Felix Miata <mrmazda@earthlink.net> - 2017-03-24 17:00 +0100
  Re: [stretch] mc-4.8.18 broken, but fixed mc-4.8.19 released 5 March Andrey Rahmatullin <wrar@debian.org> - 2017-03-24 17:20 +0100
    Re: [stretch] mc-4.8.18 broken, but fixed mc-4.8.19 released 5 March Felix Miata <mrmazda@earthlink.net> - 2017-03-31 22:40 +0200
      Re: [stretch] mc-4.8.18 broken, but fixed mc-4.8.19 released 5 March Andrey Rahmatullin <wrar@debian.org> - 2017-03-31 22:50 +0200
        Re: [stretch] mc-4.8.18 broken, but fixed mc-4.8.19 released 5 March Felix Miata <mrmazda@earthlink.net> - 2017-03-31 23:30 +0200
          Re: [stretch] mc-4.8.18 broken, but fixed mc-4.8.19 released 5 March Wouter Verhelst <wouter@debian.org> - 2017-04-02 21:10 +0200
            Re: [stretch] mc-4.8.18 broken, but fixed mc-4.8.19 released 5 March Felix Miata <mrmazda@earthlink.net> - 2017-04-02 22:20 +0200
              Re: [stretch] mc-4.8.18 broken, but fixed mc-4.8.19 released 5 March Wouter Verhelst <wouter@debian.org> - 2017-04-02 23:10 +0200
                Re: [stretch] mc-4.8.18 broken, but fixed mc-4.8.19 released 5 March Felix Miata <mrmazda@earthlink.net> - 2017-04-03 11:10 +0200

csiph-web