From yury at shurup.com Thu Aug 8 08:51:32 2024 From: yury at shurup.com (Yury V. Zaytsev) Date: Thu, 8 Aug 2024 10:51:32 +0200 (CEST) Subject: [mc-devel] Help testing release candidate / mc-4.8.32-rc1 Message-ID: Hi there, TLDR; I would appreciate if you could please test the following tarball on your systems and report any blocker regressions as compared to the previous 4.8.31 release: https://midnight-commander.org/nopaste/tarball/mc-4.8.32-pre1.tar.xz $ sha256sum mc-4.8.32-pre1.tar.xz 18b4d195963eaca64b99e1be61060e8f4d5cfc3854abfeb3ca70d3af87f60871 I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 40 VM, which I'm also going to use to build the final release in about a week from now (or earlier) if nothing serious comes up. Many thanks! -- Sincerely yours, Yury V. Zaytsev From dhmartina at yahoo.es Thu Aug 8 18:08:41 2024 From: dhmartina at yahoo.es (=?UTF-8?Q?David_Mart=c3=adn?=) Date: Thu, 8 Aug 2024 20:08:41 +0200 Subject: [mc-devel] Help testing release candidate / mc-4.8.32-rc1 In-Reply-To: References: Message-ID: <2ddace8c-010e-df2a-111a-1f561cc779a2@yahoo.es> Ubuntu server / kubuntu 24.04LTS recently installed with stock dist libraries. No compilation errors? and seems to run fine. Just a couple of glib2 deprecation warnings: Making all in tty make[3]: Entering directory '/home/dmartin/git/mc-4.8.32-pre1/lib/tty' ? CC?????? color-internal.lo ? CC?????? color.lo ? CC?????? key.lo ? CC?????? keyxdef.lo ? CC?????? mouse.lo ? CC?????? tty-internal.lo ? CC?????? tty.lo ? CC?????? win.lo ? CC?????? x11conn.lo x11conn.c: In function 'x11_available': x11conn.c:140:5: warning: 'g_module_build_path' is deprecated [-Wdeprecated-declarations] ? 140 |???? x11_module_fname = g_module_build_path (NULL, "X11"); ????? |???? ^~~~~~~~~~~~~~~~ In file included from x11conn.c:37: /usr/include/glib-2.0/gmodule.h:142:23: note: declared here ? 142 | gchar*??????????????? g_module_build_path (const gchar? *directory, ????? |?????????????????????? ^~~~~~~~~~~~~~~~~~~ ? CC?????? color-slang.lo ? CC?????? tty-slang.lo ? CCLD???? libmctty.la make[3]: Leaving directory '/home/dmartin/git/mc-4.8.32-pre1/lib/tty' David El 8/8/24 a las 10:51, Yury V. Zaytsev via mc-devel escribi?: > Hi there, > > TLDR; I would appreciate if you could please test the following > tarball on your systems and report any blocker regressions as compared > to the previous 4.8.31 release: > > https://midnight-commander.org/nopaste/tarball/mc-4.8.32-pre1.tar.xz > > $ sha256sum mc-4.8.32-pre1.tar.xz > 18b4d195963eaca64b99e1be61060e8f4d5cfc3854abfeb3ca70d3af87f60871 > > I've built this tarball out of the latest master with translations > from Transifex pulled in on a fresh Fedora 40 VM, which I'm also going > to use to build the final release in about a week from now (or > earlier) if nothing serious comes up. > > Many thanks! > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yury at shurup.com Fri Aug 9 05:40:34 2024 From: yury at shurup.com (Yury V. Zaytsev) Date: Fri, 9 Aug 2024 07:40:34 +0200 Subject: [mc-devel] Help testing release candidate / mc-4.8.32-rc1 In-Reply-To: <2ddace8c-010e-df2a-111a-1f561cc779a2@yahoo.es> References: <2ddace8c-010e-df2a-111a-1f561cc779a2@yahoo.es> Message-ID: <1003BA82-4990-4A56-8E5A-84FB56A48713@shurup.com> Hi David, Thanks for testing! The patch for the deprecation warning is attached. I fixed a similar one in aspell, but unfortunately the CI doesn't work yet, and I'm compiling on MacOS, so I didn't get the X11 one. I hope the translators can take a closer look at the translations. Due to a lot of code movement, POT has changed quite a bit, but not in terms of new strings. So hopefully it's mostly about marking some strings as not fuzzy. If this helps, I can wait another week before pulling in the updated translations... All the best, Yury -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-x11-fix-Wdeprecated-declarations-for-g_module_build_.patch Type: application/octet-stream Size: 1462 bytes Desc: not available URL: -------------- next part -------------- > On 8. Aug 2024, at 20:08, David Mart?n via mc-devel wrote: > > Ubuntu server / kubuntu 24.04LTS recently installed with stock dist libraries. > No compilation errors and seems to run fine. Just a couple of glib2 deprecation warnings: > Making all in tty > make[3]: Entering directory '/home/dmartin/git/mc-4.8.32-pre1/lib/tty' > CC color-internal.lo > CC color.lo > CC key.lo > CC keyxdef.lo > CC mouse.lo > CC tty-internal.lo > CC tty.lo > CC win.lo > CC x11conn.lo > x11conn.c: In function 'x11_available': > x11conn.c:140:5: warning: 'g_module_build_path' is deprecated [-Wdeprecated-declarations] > 140 | x11_module_fname = g_module_build_path (NULL, "X11"); > | ^~~~~~~~~~~~~~~~ > In file included from x11conn.c:37: > /usr/include/glib-2.0/gmodule.h:142:23: note: declared here > 142 | gchar* g_module_build_path (const gchar *directory, > | ^~~~~~~~~~~~~~~~~~~ > CC color-slang.lo > CC tty-slang.lo > CCLD libmctty.la > make[3]: Leaving directory '/home/dmartin/git/mc-4.8.32-pre1/lib/tty' > David > El 8/8/24 a las 10:51, Yury V. Zaytsev via mc-devel escribi?: >> Hi there, >> >> TLDR; I would appreciate if you could please test the following tarball on your systems and report any blocker regressions as compared to the previous 4.8.31 release: >> >> https://midnight-commander.org/nopaste/tarball/mc-4.8.32-pre1.tar.xz >> >> $ sha256sum mc-4.8.32-pre1.tar.xz >> 18b4d195963eaca64b99e1be61060e8f4d5cfc3854abfeb3ca70d3af87f60871 >> >> I've built this tarball out of the latest master with translations from Transifex pulled in on a fresh Fedora 40 VM, which I'm also going to use to build the final release in about a week from now (or earlier) if nothing serious comes up. >> >> Many thanks! >> > -- > mc-devel mailing list > mc-devel at lists.midnight-commander.org > https://lists.midnight-commander.org/mailman/listinfo/mc-devel From krekhov.dev at mail.ru Fri Aug 16 21:22:51 2024 From: krekhov.dev at mail.ru (Kirill Rekhov) Date: Sat, 17 Aug 2024 00:22:51 +0300 Subject: [mc-devel] Request to Use HTTPS for Improved Security on Midnight Commander FTP. Message-ID: <20240816212251.yz27bdmxs2ywaous@kory-laptop> Hello, are there any administrators of http://ftp.midnight-commander.org/ here? I was looking at the output of the `lintian` utility of the `mc` package in Debian, and I noticed the following: -> debian-watch-uses-insecure-uri [debian/watch] The `debian/watch` file of the `mc-4.8.31` package looks like this: version=3 http://ftp.midnight-commander.org/mc-([\d\.]+)\.tar\.xz An insecure connection (HTTP) is used, no HTTPS. I want to point out: 1. HTTPS ensures that the data has not been modified in transit. This is especially important for packets, to ensure that they have not been tampered with or modified. 2. HTTPS ensures that you are connecting to the real server, and not some fake site. This helps prevent man-in-the-middle (MITM) attacks. 3. Although the packages may be publicly available, using HTTPS prevents monitoring and tracking of exactly which packages you download. This protects your privacy. Could you use HTTPS? It's more secure. --- Kirill Rekhov From yury at shurup.com Sat Aug 17 05:44:49 2024 From: yury at shurup.com (Yury V. Zaytsev) Date: Sat, 17 Aug 2024 07:44:49 +0200 Subject: [mc-devel] Request to Use HTTPS for Improved Security on Midnight Commander FTP. In-Reply-To: <20240816212251.yz27bdmxs2ywaous@kory-laptop> References: <20240816212251.yz27bdmxs2ywaous@kory-laptop> Message-ID: Hi Kirill, Unfortunately this is not something we can control. We use the OSU OSL mirroring system and it still doesn't support HTTPS for custom mirror domains. In fact, you can access it with HTTPS, but the server will present a certificate for the wrong domain name (*.osuosl.org): https://ftp.midnight-commander.org I don't know if this is better for Debian. Alternatively, you can use the shared mirror tree, but there is no guarantee that the name will not change in the future, which is why projects usually have their own subdomains: https://ftp.osuosl.org/pub/midnightcommander/ I asked them half a decade ago what their plans were, and they said they'd like to fix this eventually, but right now they have other priorities. I asked again this summer (RT ticket #33475) and the answer was pretty much the same. Maybe you can help get this fixed on their end. No idea if they are able to accept contributions to their infrastructure... All the best, Yury > On 16. Aug 2024, at 23:22, Kirill Rekhov via mc-devel wrote: > > Hello, are there any administrators of http://ftp.midnight-commander.org/ here? I was looking at the > output of the `lintian` utility of the `mc` package in Debian, and I noticed the following: > > -> debian-watch-uses-insecure-uri [debian/watch] > > The `debian/watch` file of the `mc-4.8.31` package looks like this: > version=3 > http://ftp.midnight-commander.org/mc-([\d\.]+)\.tar\.xz > > An insecure connection (HTTP) is used, no HTTPS. I want to point out: > > 1. HTTPS ensures that the data has not been modified in transit. This is especially important for > packets, to ensure that they have not been tampered with or modified. > > 2. HTTPS ensures that you are connecting to the real server, and not some fake site. This helps > prevent man-in-the-middle (MITM) attacks. > > 3. Although the packages may be publicly available, using HTTPS prevents monitoring and tracking of > exactly which packages you download. This protects your privacy. > > Could you use HTTPS? It's more secure. > > --- > Kirill Rekhov > -- > mc-devel mailing list > mc-devel at lists.midnight-commander.org > https://lists.midnight-commander.org/mailman/listinfo/mc-devel From yury at shurup.com Fri Aug 23 18:00:43 2024 From: yury at shurup.com (Yury V. Zaytsev) Date: Fri, 23 Aug 2024 20:00:43 +0200 (CEST) Subject: [mc-devel] Midnight Commander 4.8.32 released Message-ID: <15bcd6e8-acd1-f259-cdbb-a25cbcbb3b7@shurup.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, I am pleased to announce the immediate availability of mc-4.8.32, a maintenance and bugfix release of Midnight Commander! The main feature of this release is the implementation of nanosecond timestamps for non-Linux systems (macOS, BSD, AIX, Solaris) and related build fixes. Otherwise, as usual, there are a few other minor improvements and a number of bug fixes. In particular, we've made further updates to mc.ext.ini to fix the remaining escaping issues. As always, if you have local overrides, please check your regex patterns. For a detailed list of changes since the last release, please refer to the release notes. An update is recommended to take advantage of these improvements! Download page: http://ftp.midnight-commander.org/?C=N;O=D Release notes: http://www.midnight-commander.org/wiki/NEWS-4.8.32 I would like to thank Andrew Borodin for his tireless maintenance work, as well as all of our contributors, including translators. A special shout out goes to the great folks at JetBrains for providing me with a CLion license for the development work I did on this release. This IDE has come a very long way since I first tried it almost 10 years ago (sic!), and it's support for C projects has really made working on mc fun again for an old Python afficionado like me! Enjoy this new release and have a nice rest of the year! Z. - -- Sincerely yours, Yury V. Zaytsev -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJmyM5RAAoJEPci7nm8u+DvHQcP/2AwifSBgC8M4admN0TTAMGH qy8tsGQtC4KXSlKA5LpbnZ6jLUnkCYqIoW5MXxign1KE6jF8CXmeiI28KQ8NLs8C NF2EGgTkSb7aPOuTliQTMcFiw7LjahAfpzMYYqVHdLz5eVaE+iwHLS1OMi8OwveD P+ojQDvxtVvOJ2F74khjv6hpCsWoWPViFvLYgpNji5ORg01s/nAoF4T2y1VYGGmr Bnw6zcQVLPq6gfrQw/LnR0IyeGmtygEkooZidQFfIzBMkdFvUOtD5Nk1OyY5QQW6 eXl33Kf5FJ/bZR29BQEttbVr7h8R0Ypwso2Aa0POZF4QED87gZt592lKpFOCwjiB F0T1TF5WoWJcXCMCf5GsPjmOor61e+Q7/eyREdBIv6DwPh+1bY4Y+PTSqecLRZ9P ZLjWvxhfwL6IiHh2ns17rjQj4zNIkqnQKdtukw/NqJmoNYIVAOQZzZd03FRwbyPv CEPh3U31HNXBn7HDAJPSsNIws9MSx+1uQvteIfdhGe3eeMsj7rh9Yf/iB8VJA12V Lz+kF2jsQ9dyRfchBJZ40ulDPR1hnRlThShc/uNd3lR1R7CwGRJeUVQQSVn3C2OF y8mowf06JEClucrd+6sLrhakjNn+gvy1XsPu0vkjnRSDgziayIwJpDzE2AzyfDB2 wM2Gw66BImsevSn/J3SO =WR/S -----END PGP SIGNATURE-----