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



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.




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]