!PackMan Verify broken

The verify function of !PackMan errors before even checking any packages, doesn’t seem to like the .^. used in the path.

I’m seeing that as well (PackMan 0.9.5; RISC OS 5.28; Raspberry Pi 3B+). The errors never seem to stop: Alt-Break is needed to escape.

The error log (!PackMan.errorlog) contains the same error repeated multiple times:
File name 'SCSI::HardDisc4.$.!BOOT.Resources.!System.' not recognised (SWI 29) r0=25

Switching on PackMan logging doesn’t produce any further diagnostics.

I’ve discovered what’s doing (at least some of) it. Several of the entries in !Packages.Info have path entries as well as file names inside “Files”. For example, !Packages.Info.ARMEABISupport.Files has:
System.
System.400.
System.400.Modules.ARMEABISupport

Remove these extraneous paths and the verification proceeds to the next package.

Of course there is a danger in removing the path entries: the packages may now fail to install…

I cannot get this to work properly, some packages verify okay but there will be another after it, it doesn’t seem to like checking directories for their existence.

I’ve had an email from Alan Buckley. He’s found the problem (a package is allowed to create directories, but the Verify process didn’t take this into account) and a fix should appear in the next version of PackMan.

Excellent, thanks!

Confirmation that PackMan 0.9.6 fixes this bug.

Seems to of created a new bug though, i have an issue with libcurl which say "Protocol “https” not supported or disabled by libcurl.

https://imgur.com/a/GKF8rGF

It worked after a reboot but has persisted since.

I could easily be missing something but libcurl is installed.

The only source i have that requires SSL is riscosports.co.uk/packages/vfptesting

That’s exactly what I’m seeing. I had to disable the RISC OS Ports URL; Advanced → Sources https://www.riscosports.co.uk/packages/vfptesting

Sorry about this, I have accidently compiled PackMan without SSL support. I have been informed of the problem so I’m hoping to get a new version to re-enable SSL out soon.

AH that’ll do it, thanks for the update :)