Re: Help testing the pre-release of mc-4.8.18

[Andrey Gursky]

Hi,

On Thu, 29 Sep 2016 21:39:11 +0200 (CEST)
"Yury V. Zaytsev"  wrote:

> On Tue, 27 Sep 2016, Paul Marwick wrote:
> 
> > I can't say I was having any major problems with 4.8.17, though there 
> > was a second release from the Arch maintainer a few days ago with a 
> > couple of patches applied.
> 
> I'm very grateful to the distro maintainers for adding patches to address 
> our screw-ups which have got uncovered after the release, but ideally 
> there should be simply less of those in my opinion.

I also appreciate the work of distro maintainers.

Regarding screw-ups. Yury, what do you think about issuing release
candidate versions of MC? This is a convenient way to get MC to be
tested in Distros on a regular basis (not git snapshots) (provided
maintainers update their packages in a timely manner). This is what,
e.g. Debian Experimental and Sid (unstable) are for, isn't it?

Additionally are these 4.8.x releases really only bug-fix releases? I
mean, if there would be at least one (and indeed there are some) commit
like refactor/rework/code-cleanup/... then it would be better to go
forward to 4.9.x and so on. The goal is to make .x really only small
bug-fix releases, while fixes, that going towards (even if only code)
improvements, aren't plain bug-fix releases anymore and should be
marked with a minor version increment, not a patch one. Then you
wouldn't need release candidates for true small/critical bug-fix
releases, though they are still possible.

> > I've built the package and have it running. So far, its working just 
> > fine. Are there any specific problems you would like checked? I use fish 
> > a lot (both within my own network and for remote work on customer 
> > sites), I use the editor and viewer and I make a great deal of use of 
> > the VFS support.
> 
> Thank you for your feedback! This sounds good.
> 
> I'm particularly worried about builds on platforms that we aren't 
> regularly using ourselves (non-Linux), like FreeBSD, Solaris, etc.

I'd like to propose to start/continue specifying where MC is supported.
I believe MC can be truly supported only on systems, that MC developers
are on, e.g. GNU/Linux (Debian, Fedora, OpenSUSE, Gentoo, Arch,..). Of
course this doesn't mean all others are out of care. I'd suggest to add
them into a "known to work on" / "not officially supported" section.
This means one doesn't have to worry to break something on such systems
anymore, just because MC cannot be tested there by MC developers (even
if there would be already existing tests). Once users of such system
find a bug, then this could be handled.

Saying, these systems are so important that we cannot risk to break
them (while having no access) seems contradictory IMHO. And it would
mean MC will be only cleanuped but no actual development will take
place?

> Anyways, so far it appears that there doesn't seem to be any serious 
> regressions, so we'll probably release 4.8.18 in the days to come...

Regards,
Andrey
___
mc mailing list
https://mail.gnome.org/mailman/listinfo/mc

Re: Help testing the pre-release of mc-4.8.18

[Yury V. Zaytsev]

On Tue, 27 Sep 2016, Paul Marwick wrote:

I can't say I was having any major problems with 4.8.17, though there 
was a second release from the Arch maintainer a few days ago with a 
couple of patches applied.


I'm very grateful to the distro maintainers for adding patches to address 
our screw-ups which have got uncovered after the release, but ideally 
there should be simply less of those in my opinion.


I've built the package and have it running. So far, its working just 
fine. Are there any specific problems you would like checked? I use fish 
a lot (both within my own network and for remote work on customer 
sites), I use the editor and viewer and I make a great deal of use of 
the VFS support.


Thank you for your feedback! This sounds good.

I'm particularly worried about builds on platforms that we aren't 
regularly using ourselves (non-Linux), like FreeBSD, Solaris, etc.


Anyways, so far it appears that there doesn't seem to be any serious 
regressions, so we'll probably release 4.8.18 in the days to come...


--
Sincerely yours,
Yury V. Zaytsev
___
mc mailing list
https://mail.gnome.org/mailman/listinfo/mc

Re: Help testing the pre-release of mc-4.8.18

[Paul Marwick]

Yury V. Zaytsev wrote:

Hi there,

TLDR; we would appreciate if you could test the following tarball on
your systems and report any blocker regressions as compared to 4.8.17:

http://www.midnight-commander.org/nopaste/tarball/mc-4.8.17-122-g6822251.tar.xz

$ sha256sum mc-4.8.17-122-g6822251.tar.xz
e9a4a418d9d551b4a58fffa907c001a5eb84d2fe2e490d221f99c1d1642fecbd

A longer explanation: we're thinking of making another bugfix release
next week or so to push out the changes accumulated in master so far.


I can't say I was having any major problems with 4.8.17, though there 
was a second release from the Arch maintainer a few days ago with a 
couple of patches applied.




However, I find it very unsatisfying that we've been getting an influx
of reports concerning some really annoying regressions right after the
releases in the past, so, this time around, I propose that distro
maintainers and regular users check the pre-release tarball beforehand
and report FTBFSs & regressions if any, such that this time (hopefully)
we'll break out of this vicious cycle.

I've built this tarball out of the latest master with translations from
Transifex pulled in on the same VM where I build regular releases.

Many thanks!

I've built the package and have it running. So far, its working just 
fine. Are there any specific problems you would like checked? I use fish 
a lot (both within my own network and for remote work on customer 
sites), I use the editor and viewer and I make a great deal of use of 
the VFS support.


If anyone is interested, I've built an Arch package for it (though I had 
to rename it to 4.8.18 to get it through the Arch makepkg rules. Anyone 
who wants to try the Arch build, drop me an email.


Paul.


___
mc mailing list
https://mail.gnome.org/mailman/listinfo/mc

Re: Help testing the pre-release of mc-4.8.18

[Yury V. Zaytsev]

On Mon, 26 Sep 2016, Andrey Tataranovich wrote:


I think that must have the same underlying reason as this ticket:

http://www.midnight-commander.org/ticket/3406

... do you have the same issue with 4.8.17, i.e. is this a regression, 
or an old bug? In any case, I've just tried it, and for me it works 
fine.


I'm sorry. I have rechecked and find that cyrillic names do not lead to 
this issue but a broken symlink that points to currently unavailable 
location.


Try to create broken symlink and view this directory via SFTP.


Okay, so that's really the old #3406 bug...

I couldn't find any ticket re. zoo listing on the Trac. Could you 
please make one with a reproducer? If it's not a regression, this won't 
be a priority, but it would be nice to fix it for the next release.


I have created ticket for this issue: 
https://www.midnight-commander.org/ticket/3696


Thank you very much! One day, we'll get to it. Hopefully.

--
Sincerely yours,
Yury V. Zaytsev
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel

Re: Help testing the pre-release of mc-4.8.18

[Andrey Tataranovich]

On Mon, 26 Sep 2016 13:17:36 +0200 (CEST)
"Yury V. Zaytsev"  wrote:

> Hi Andrey,
> 
> Thank you for testing!
> 
> On Mon, 26 Sep 2016, Andrey Tataranovich wrote:
> 
> > Have found "SFTP Protocol error (-31)" when entering directory with 
> > cyrillic names in it. But after error MC show correct directory
> > listing.  
> 
> I think that must have the same underlying reason as this ticket:
> 
> http://www.midnight-commander.org/ticket/3406
> 
> ... do you have the same issue with 4.8.17, i.e. is this a
> regression, or an old bug? In any case, I've just tried it, and for
> me it works fine.

I'm sorry. I have rechecked and find that cyrillic names do not lead to
this issue but a broken symlink that points to currently unavailable
location.

Try to create broken symlink and view this directory via SFTP.

> > Checked multiple archive formats and noticed that zoo archive
> > listing is broken (was already broken in 4.8.17).  
> 
> I couldn't find any ticket re. zoo listing on the Trac. Could you
> please make one with a reproducer? If it's not a regression, this
> won't be a priority, but it would be nice to fix it for the next
> release.

I have created ticket for this issue:
https://www.midnight-commander.org/ticket/3696

-- 
WBR, Andrey Tataranovich
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel

Re: Help testing the pre-release of mc-4.8.18

[Yury V. Zaytsev]

Hi Andrey,

Thank you for testing!

On Mon, 26 Sep 2016, Andrey Tataranovich wrote:

Have found "SFTP Protocol error (-31)" when entering directory with 
cyrillic names in it. But after error MC show correct directory listing.


I think that must have the same underlying reason as this ticket:

http://www.midnight-commander.org/ticket/3406

... do you have the same issue with 4.8.17, i.e. is this a regression, or 
an old bug? In any case, I've just tried it, and for me it works fine.


Checked multiple archive formats and noticed that zoo archive listing is 
broken (was already broken in 4.8.17).


I couldn't find any ticket re. zoo listing on the Trac. Could you please 
make one with a reproducer? If it's not a regression, this won't be a 
priority, but it would be nice to fix it for the next release.


--
Sincerely yours,
Yury V. Zaytsev
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel

Re: Help testing the pre-release of mc-4.8.18

[Andrey Tataranovich]

On Sun, 25 Sep 2016 20:43:46 +0200
"Yury V. Zaytsev"  wrote:

> TLDR; we would appreciate if you could test the following tarball on
> your systems and report any blocker regressions as compared to 4.8.17:
> 
> http://www.midnight-commander.org/nopaste/tarball/mc-4.8.17-122-g6822251.tar.xz
> 
> $ sha256sum mc-4.8.17-122-g6822251.tar.xz
> e9a4a418d9d551b4a58fffa907c001a5eb84d2fe2e490d221f99c1d1642fecbd

Have found "SFTP Protocol error (-31)" when entering directory with
cyrillic names in it. But after error MC show correct directory
listing.

Checked multiple archive formats and noticed that zoo archive
listing is broken (was already broken in 4.8.17).

-- 
WBR, Andrey Tataranovich
___
mc-devel mailing list
https://mail.gnome.org/mailman/listinfo/mc-devel