rakudo / rakudo.org

Code for rakudo.org website
https://rakudo.org/
Artistic License 2.0
8 stars 18 forks source link

latest release does not show on release page #72

Closed ToddAndMargo closed 2 years ago

ToddAndMargo commented 3 years ago

Hi All,

https://rakudo.org/downloads/star/

shows the latest release as 2021.04

https://rakudo.org/latest/star/win

Downloads

rakudo-star-2020.05.1-01-win-x86_64-(JIT).msi

Please update your web site.

Many thanks, -T

patrickbkr commented 3 years ago

Currently we are in need of people to take over maintaining the Star Bundle.

As there was up until recently no one there who could create the MSI files, only the Star Bundle Source release happened. That is what you are observing. The latest source release is 2021.04 (that also shown on https://rakudo.org/star/), while the latest MSI is 2020.05. So it's actually not a matter of updating the website, but of re-starting to create Star Bundles in the first place.

Things are starting to move again, so please bear with us a little longer.

Out of curiosity, are you explicitly interested in the Star Bundle or in an MSI installer? I ask, because I'm currently working on providing MSI installers for the monthly Rakudo release.

ToddAndMargo commented 3 years ago

On 7/6/21 2:28 PM, Patrick Böker wrote:

Currently we are in need of people to take over maintaining the Star Bundle.

As there was up until recently no one there who could create the MSI files, only the Star Bundle Source release happened. That is what you are observing. The latest source release is 2021.04 (that also shown on https://rakudo.org/star/ https://rakudo.org/star/), while the latest MSI is 2020.05. So it's actually not a matter of updating the website, but of re-starting to create Star Bundles in the first place.

Things are starting to move again https://github.com/rakudo/rakudo/issues/4001, so please bear with us a little longer.

Out of curiosity, are you explicitly interested in the Star Bundle or in an MSI installer? I ask, because I'm currently working on providing MSI installers for the monthly Rakudo release.

Hi Patrick,

The MSI installer.

:-)

-T

patrickbkr commented 2 years ago

Closing, as the reason for the situation is clear.

patrickbkr commented 2 years ago

@ToddAndMargo I just wrapped up my work on the new MSI installer. Do you mind giving it a test and provide feedback? Here is the link for the 2021.06 MSI file: https://rooster.uber.space/patcloud/index.php/s/SZjxqrZXdG6xpnZ/download

ToddAndMargo commented 2 years ago

On 7/9/21 12:52 PM, Patrick Böker wrote:

@ToddAndMargo https://github.com/ToddAndMargo I just wrapped up my work on the new MSI installer. Do you mind giving it a test and provide feedback? Here is the link for the 2021.06 MSI file: https://rooster.uber.space/patcloud/index.php/s/SZjxqrZXdG6xpnZ/download

https://rooster.uber.space/patcloud/index.php/s/SZjxqrZXdG6xpnZ/download

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/rakudo/rakudo.org/issues/72#issuecomment-877420750, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGN3ROC6DLHV6LUVGVGAQLTW5HOTANCNFSM47YQH67Q.

Hi Patrick,

Test bed: Host: Fedora 34 Xfce 4.14 qemu-kvm-5.2.0-8.fc34.x86_64

Virtual machine:
    Windows 11 (not a typo of 10)
      Installed from ISO 22000.51_amd64_x64
      upgraded from ISO to 22000.65_x64

    ISO's created from script on
        https://uupdump.net/

Raku: Git-2.32.0.2-64-bit.exe

Removed:
    RakudoStar-2020.05.1.01-win-x86_64-(JIT).msi

Installed:
    rakudo-moar-2021.06-01-win-x86_64-msvc.msi

1) Not tested: if the msi would properly remove the old install. (A real annoyance to troubleshoot.)

Things I noticed:

2) Raku was moved from C:\rakudo to C:\Program Files\Rakudo\bin

If this is not on purpose, please fix.

Also, the install path should be customizable.

And the name got changed from Rakudo.exe to Raku.exe

I had to update my shortcuts.

3) Zef could not unlock repo.lock (or create it) as a standard user

K:\windows\NtUtil>zef install Getopt::Long ===> Searching for: Getopt::Long ===> Updating fez mirror: http://360.zef.pm/ ===> Updated fez mirror: http://360.zef.pm/ ===> Updating cpan mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/cpan1.json ===> Updated cpan mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/cpan1.json ===> Updating p6c mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/p6c1.json ===> Updated p6c mirror: https://raw.githubusercontent.com/ugexe/Perl6-ecosystems/master/p6c1.json ===> Testing: Getopt::Long:ver<0.3.3> ===> Testing [OK] for Getopt::Long:ver<0.3.3> ===> Installing: Getopt::Long:ver<0.3.3> ===> Install [FAIL] for Getopt::Long:ver<0.3.3>: Failed to open file C:\Program Files\Rakudo\share\perl6\site\repo.lock: Permission denied Failed to open file C:\Program Files\Rakudo\share\perl6\site\repo.lock: Permission denied

Rerunning the command as Administrator worked.

4) These two programs worked:

K:\windows\NtUtil>"C:\Program Files\Rakudo\bin\perl6.exe" InetConnectTest.pl6 Unable to ping Google's DNS server (8.8.8.8) Perhaps you need to restart the firewall?

The above happened because I disconnect my internet connection to test the program.

K:\windows\NtUtil>"C:\Program Files\Rakudo\bin\perl6.exe" CobianWrapper.pl6 --help Welcome to CobianWrapper.pl6

CobianWrapper.pl6 usage:

CobianWrapper.pl6 --backup_path Drive letter or partition label plus path to backup directory. for a label, surround the label with square brackets []. Note: the backup directory name must end in a 1 --rotates --nokill nokill will disable the killing of programs known to be Shadow Copy (VSS) unfriendly --debug --help

Defaults: --backup_path [BACKUP]\MyDocsBackup\backup1 --rotates 2

   --nokill       False
   --debug        False
   --help         False

For example C:\rakudo\bin\raku C:\NtUtil\CobianWrapper.pl6 --rotates 6 --backup_path A:\MyDocsBackup\n\backup1 C:\rakudo\bin\raku C:\NtUtil\CobianWrapper.pl6 --rotates 4 --backup_path [BACKUP]\MyDocsBackup\backup1

more? (y/n) y

Sample Cobian Pre-backup Event call to CobianWrapper.pl6: COMMANDLINE,"C:\rakudo\bin\raku.exe C:\NtUtil\CobianWrapper.pl6 --rotates 20 --backup_path [BACKUP]\MyDocsBackup\backup1",true

Sample Cobian File, Destination for use with CobianWrapper.pl6: %DISKLABEL="BACKUP":\MyDocsBackup\backup1

Sample Cobian Post-backup Event call to CobianWrapper.pl6 (requires USB_Disk_Eject-1.3.0.3.exe): COMMANDLINE,"C:\NtUtil\USB_Disk_Eject-1.3.0.3.exe /REMOVELABEL BACKUP",true

Suggest Cobian Backup settings: --> Tools (pull down) --> Options General (left Column): uncheck: Log new version as error uncheck: Check for Updates Log (left Column): Mail log files uncheck: Send as attachment When to mail: Mail after every task Visuals: Show numbers in progress bars Advanced: Communications (tab): IPC timeout: change from 180_000 to 3_600_000

5) Things still worked after a reboot. Yippee!

I have VM's of W7, W10, and archived somewhere XP, if you need those tested too.

HTH, -T

ToddAndMargo commented 2 years ago

On 7/9/21 12:52 PM, Patrick Böker wrote:

@ToddAndMargo https://github.com/ToddAndMargo I just wrapped up my work on the new MSI installer. Do you mind giving it a test and provide feedback? Here is the link for the 2021.06 MSI file: https://rooster.uber.space/patcloud/index.php/s/SZjxqrZXdG6xpnZ/download https://rooster.uber.space/patcloud/index.php/s/SZjxqrZXdG6xpnZ/download

And rakuw still opens a shell (big black box) for the user to see.

patrickbkr commented 2 years ago

@ToddAndMargo Thanks for your tests!

1) Not tested: if the msi would properly remove the old install. (A real annoyance to troubleshoot.)

Can't tell for sure, but I think this should work. I'll test this (probably tomorrow evening).

2) Raku was moved from C:\rakudo to C:\Program Files\Rakudo\bin If this is not on purpose, please fix. Also, the install path should be customizable.

The installer should allow customizing the install path. Did it for some reason not show you that option? (Did you install the MSI without a GUI in unattended mode? Did you somehow manage to do an update of a previous installation?)

And the name got changed from Rakudo.exe to Raku.exe I had to update my shortcuts.

The MSI installs the whole bunch of executables, including all variants of both rakudo.exe and raku.exe. Where did you get the impression that executable names got changed? (I'd like to fix that.)

Also, which shortcuts are you talking about?

3) Zef could not unlock repo.lock (or create it) as a standard user ... Rerunning the command as Administrator worked.

This shouldn't be. I'll look into this.

@ugexe @niner I thought Rakudo (or Zef?) would fall back to installing to a users home dir repo if the site repo wasn't writable. Is that assumption wrong? Is this possibly broken on Windows? Do I misidentify this case as an instance of non-writable site repo?

4) These two programs worked ... 5) Things still worked after a reboot. Yippee!

Nice.

I have VM's of W7, W10, and archived somewhere XP, if you need those tested too. HTH, -T

I think there is no pressing need to test this again on other versions. (I did all my tests on Windows 10.)

patrickbkr commented 2 years ago

@ToddAndMargo

And rakuw still opens a shell (big black box) for the user to see.

Thanks for the report. That was a minor build system bug. Will be fixed by https://github.com/rakudo/rakudo/pull/4451 . Only rakuw.exe was affected. rakudow.exe and perl6w.exe are both fine.

patrickbkr commented 2 years ago

@ToddAndMargo

  1. Zef could not unlock repo.lock (or create it) as a standard user ... Rerunning the command as Administrator worked.

This shouldn't be. I'll look into this.

@ugexe @niner I thought Rakudo (or Zef?) would fall back to installing to a users home dir repo if the site repo wasn't writable. Is that assumption wrong? Is this possibly broken on Windows? Do I misidentify this case as an instance of non-writable site repo?

This is now fixed with rakudo/rakudo#4452 and ugexe/zef#405

patrickbkr commented 2 years ago

@ToddAndMargo

  1. Not tested: if the msi would properly remove the old install. (A real annoyance to troubleshoot.)

Can't tell for sure, but I think this should work. I'll test this (probably tomorrow evening).

I did a test. Updating works as it should. It remembers installation dir and whether the env vars should be set or not. Then it uninstalls the previous version and installs the new one. It probably will not work with an older Star Bundle installation, but should work from now onward.

Btw. did you realize, that I need feedback for doing anything about 2. ?