Please find instructions here. I make this call now as I am on the verge of providing an RC ISO. The most recent beta ISO is stored there.

The most urgent translation work is on the files auto (which gathers messages from the "functions" script superseding the "auto" script), rc.S (modified from the one in a Slackware installer) and the HandBook.

Questions and remarks welcome in this thread and other communication channels mentioned in Support.

I will include in the next ISO all translations of auto and rc.S at least 80% translated, but if you miss the next train don't worry: I will provide a new ISO as soon as a new locale meets these requirements. Folks having installed using the first RC ISO will not have to reinstall when a new one or a stable one is published, using slapt-get or gslapt will be enough as for any package update showing in the ChangeLog.

PS For folks worried by a thread about Slint in this Slackware forum, I promise not to do that again. At least until next time.

...thus I tag this thread as [SOLVED]. Nevertheless, If you want to help version 15.0 become the best Slint release ever, please read: TESTING If you had no idea what to do this week end, now you know

The installer is available in English, Dutch, French, Greek, Italian, Portuguese, Swedish, huge thanks to our translators!

The documentation inside the installer is also translated: just typing "doc" during installation displays the relevant information extracted from the HandBook in the w3m pager/web browser, in the language in use, with a fallback to English.

In the installed system, typing "slint-doc" displays the full HandBook in the locale set in $LANG, in w3m in console mode, in Firefox in a graphical environment.

Cheers!

Doing an install to a vm right now. Other than me only making my usual 30G disk instead of 50G and the error below the install is working fine so far.

Tried using the doc command but it gave the following error:
edit:
1. Installer did not pick up an ip during the initial install, but did the second time. Tried to replicate the issue by deleting the dhcp entry first then 2nd, changing the MAC address. Could not replicate the original issue but after the MAC address change was the first time the installer was able to guess the time zone and ask me to confirm. Brand new VM did not replicate it either.

2. Also did not see this error the first time as I chose to show packages being installed. I was paying a bit more attention the second time but it scrolled by too quickly. I turned that off the 3rd time through.

1 members found this post helpful.

Thanks for your report!

Well, actually the partition for / in the system just installed has a size of 7.7G (file system btrfs) or 15G (file system ext4). But I set a minimum of 50G in the /sbin/functions script of the installer line #32:
GCOUNT=50
I am puzzled you could install in 30G. Did you find the above line and edited the script setting a lower value to GCOUNT?
Shame on me, I typed doc in all languages but English when testing! This is true indeed, this file is missing.
This kind of thing is hard to diagnose. You checked the integrity of the ISO with sha256sum, right?

I forgot to mention in TESTING that at end of installation all installation files and logs are stored in the directory /var/log/INSTALLER in the installed system and also in the compressed archive /var/log/INSTALLER.xz that can be sent by email to help diagnose installation issues.

2. Also did not see this error the first time as I chose to show packages being installed. I was paying a bit more attention the second time but it scrolled by too quickly. I turned that off the 3rd time through.

Weird. I did not encounter this issue in my tests, and just checked having mounted the ISO that this package is correct.

EDIT: file TESTING updated.

1 members found this post helpful.

It didn't let me install, meant that it was my mistake but it would be a common expectation for someone installing to a VM based on the size of the iso I think.

I didn't before, but it matches.
Good to know, I'll email you the archive. Wish I had that from the very first try.

Nothing specific about the os-prober errors but looking at /var/log/INSTALLER/tmp/PKGLISTS/loginstall the following is probably where the error is coming from.

1 members found this post helpful.

Hi,

as installation of the package os-prober fetched from a remote mirror failed, it was installed from the ISO as shows var/log/INSTALLER/tmp/PKGLISTS/loginstall so your installation is complete.

As it happens I made a call fort testing on the Slint forum hosted by Salix and this issue was also observed by Hugo Carvalho : https://forum.salixos.org/viewtopic....&t=8432#p48084, to which I answered this: I am still investigating this possible download issue, will report my findings.

Cheers

1 members found this post helpful.

I confirm the download issue, which currently makes the installer unable to install from remote repositories and fixed it locally. Meanwhile I have mentioned this issue and a workaround in TESTING. I will keep this file updated, using it as very basic bug tracker.

This ChangeLog mentions fixes applied, when just updating packages is enough to solve issues.

1 members found this post helpful.

Follow up: slint64-5.0rc2.iso is available here. All reported issues and bugs should be fixed or closed. Installation can be done in English, Dutch, French, Greek, Italian, Portuguese and Swedish, including the internal documentation you get typing "doc" during installation, and the full HandBook is available off line in the same languages in an installed Slint system typing "slint-doc", thanks to our translators.

Next task for me is to rewrite the Slint website, fully static and updated for Slint 15.0, including access to the HandBook in all its translated versions. When done I will officially release Slint 15.0.

Translations in not yet available languages are still welcome, and as soon as available will be included both in the website and in a new ISO.

Hi Didier,

Found one little issue with the choice of desktops. Try hitting enter without typing in a choice, it's not obvious how to reset the prompt. Might want to add a note that ctrl-d will reset the loop.

None of the other install prompts have that issue.

Cheers

1 members found this post helpful.

Hi fourtysixandtwo,

thanks for the heads-up.

In this case I will just reset the loop directly, clearing the screen then re-displaying this:

1 members found this post helpful.