PackMan package manager 0.9.2 beta released

Just tried again with the same result, i.e. zilch. The ‘done’ came up very quickly, and there did not seem to be any green colour on the progress field.

Fetch log is as follows.

Time     Code  Description
23:34:05 30000 Reading list of sources from disc
23:34:05 30001 Downloading source lists
23:34:05 30004 All sources downloaded
23:34:05 30006 Packages from downloaded sources added to available list
23:34:05 30007 Adding local packages
23:34:05 30008 Updating package database
23:34:05 30009 Package database update completed

The times reported are incorrect by about 12 minutes. The RTC in the machine is accurate.

The sources file is as supplied in v. 0.9.3.

# Default set of packages used when PackMan is first installed
#
# Packages on lines starting with a # are initially disabled
#
# The main package lists are switching to the ROOL site
# (<a href="http://www.riscosopen.org">www.riscosopen.org</a>) as they have received some testing 

pkg <a href="http://packages.riscosopen.org/packages/pkg/programs-armv5">http://packages.riscosopen.org/packages/pkg/programs-armv5</a>
pkg <a href="http://packages.riscosopen.org/packages/pkg/thirdparty">http://packages.riscosopen.org/packages/pkg/thirdparty</a>

# RISC OS 5 disc image nightly builds
# <a href="http://packages.riscosopen.org/packages/pkg/rool">http://packages.riscosopen.org/packages/pkg/rool</a>

# JASPP - source of old games made to run on new hardware
# <a href="http://www.jaspp.org.uk/packages/release">http://www.jaspp.org.uk/packages/release</a>

# Core system packages for the Raspberry Pi RISC OS distribution.
 
#pkg <a href="http://packages.riscosopen.org/packages/pkg/raspberrypi-system">http://packages.riscosopen.org/packages/pkg/raspberrypi-system</a>

# New system components that are under test (may break your system)
#pkg <a href="http://packages.riscosopen.org/packages/pkg/raspberrypi-testing">http://packages.riscosopen.org/packages/pkg/raspberrypi-testing</a>

# Original packaging list from <a href="http://www.riscpkg.org">www.riscpkg.org</a>
#pkg <a href="http://www.riscpkg.org/pkg/Unstable">http://www.riscpkg.org/pkg/Unstable</a>

# Autobuilder - useful ported applications and the GCC compiler
#pkg <a href="http://www.riscos.info/packages/pkg/autobuilt">http://www.riscos.info/packages/pkg/autobuilt</a>

There is no file called Sources in !Boot.Choices.Packman, but there is one in !Packman.Resources. The files in !Boot.Choices.Packman are Backups and WhatsNew. On my Pandaboard running Packman v0.9.1 !Boot.Choices.PackMan contains those 2 files plus Choices.
As for the time being ahead by 2 hours, I am in GMT and the RISC OS clock is giving the correct time. By comparison, on my Pandaboard the times in the “Log Viewer” window are about 12 minutes ahead of the RISC OS clock.
I have emailled you the Sources file inside !Packman.Resources.

There is no file called Sources in !Boot.Choices.Packman, but there is one in !Packman.Resources

I’ve found this problem now, PackMan is supposed to fallback to !PackMan.Resources when the sources list isn’t in !Boot.Choices.PackMan, but I messed up the fallback directory path.

I’ve got a fix ready, but I want to try and sort out a couple more of the problems before producing a new release.

A fix for now is to copy The Sources file to from !PackMan.Resources to !Boot.Choices.PackMan.

I’ve just uploaded PackMan 0.9.4 which hopefully should sort out the problems reported here.

I believe the package indices are updated overnight so it should appear on the package lists tomorrow or Monday at the latest.

If you are using a version 0.9.2 or 0.9.3 that won’t update the package list, you can download the new version from https://sites.google.com/site/alansriscosstuff/packman.

Sorry for any inconvenience and thanks to all the people who promptly reported the problems so I could look into them so quickly.

Re – blank PackMan entry in PackMan

I’ve just manually updated to 9.4 and I can see 9.4 is now in the list file, but it’s still showing as blank line within PackMan with incompatibility icon only. If I change the package name for PackMan in !Packages.Available it then shows.

When I update the lists it offers the Upgrade All button, which lists PackMan 9.4 with the only option being “Remove” – which I stupidly clicked on and of course it deleted itself. After manually putting PackMan back again, it then shows PackMan correctly in the list and I can then let it pull itself back down again so it shows as installed.

I’d conclude from that there’s something cached that’s preventing it showing itself. As for allowing it to remove itself…should that be offered as a option?

I’ve just uploaded PackMan 0.9.4 which hopefully should sort out the problems reported here.

On RISC OS 4.02 it fails to run (abort on data transfer at &807C). This appears to be because the WimpSlot of 4MB isn’t large enough to load the !RunImage, whereas RISC OS 5 now adjusts the WimpSlot for AIF files by magic.

Updating from 0.9.3 to 0.9.4 has yet again overwritten SharedULib 1.15 with 1.14, but at least this time 1.15 was preserved as a backup zip. A spurious empty Apps.Admin directory was again created, !PackMan itself did finish up in the specified location.

On RISC OS 4.02 it fails to run (abort on data transfer at &807C). This appears to be because the WimpSlot of 4MB isn’t large enough to load the !RunImage, whereas RISC OS 5 now adjusts the WimpSlot for AIF files by magic.

FWIW, that magic is also available for older OS versions; feel free to include it in Packman if you think it’s worthwhile.

http://www.phlamethrower.co.uk/riscos/absolutely.php

For RISC OS 5 it was fixed in RISC OS 5.20 (or more specifically, FileSwitch 2.81, but checking the OS version is likely to be safer to avoid ROL vs. ROOL numbering issues)

PackMan 0.9.4 – Phantom updates

Today I refreshed the software list and this resulted with the option to update. I clicked update button and then a window opened with a list of updates; with withdraw being present by each update. As the list looked odd, but correct. I decided to close the update window and went to view the updates again, this time I was presented with only one update. I updated the available app and it worked. What I saw would suggest that there were phantom updates in the initial update window.

Has anyone else seen this?

Packman did update itself from 0.9.3 to 0.9.4 (the 0.9.3 being a completely clean install). It seems to install other packages correctly, but only if you install in to the default location. If you try to install in a different place, then it actually ends up in the default location and a ‘log’ is produced. For example

Time     Code  Description
16:16:20 30038 The files for the packages have been installed correctly, but
16:16:20 30039 the following warnings occurred during configuration.
16:16:20 10003 Component 'SCSI::SSD.$.Apps.CJTest.!UnitConv' has not been installed'

The CJTest directory was where I tried to install it.

If it is installed in the default location, then using the options from the Info window to try to move the package also fails. An error that files could not be copied is raised.

I am pretty sure it was possible to change the default location of the package previously.

Chris the !UnitConv install problem is due to a mistake in the UnitConv package. The Folder structure in the package is Apps.Misc.!UnitConv (which is correct) but the Component fields says Apps.Miscellaneous.!UnitConv (Movable). The component field should match the folder structure. i.e. Apps.Misc.!UnitConv (Movable)

Jon, I think what you were seeing was caused by it needing an update lists to after the install of 0.9.4 to fix the package lists.

On RISC OS 4.02 it fails to run (abort on data transfer at &807C). This appears to be because the WimpSlot of 4MB isn’t large enough to load the !RunImage, whereas RISC OS 5 now adjusts the WimpSlot for AIF files by magic.

I’ve updated the Wimpslot for RISC OS 4 so it will start now. I’m going to see if anything else turns up in the next couple of days and do another release soon with this fix.

Jeffrey, it does look good your module, but I’m not sure I will use it for now.

PackMan 0.9.4 – Phantom updates

Andrew, I think PackMan 0.9.4 needed to update lists to recover from the 0.9.x problems. If if happens again can you try to spot which packages are involved and let me know.

Thank you, I’ll report back if it happens again.

As I’ve been swapping between builds, RISC OS Direct and my current one. I noticed that the RISC OS Direct build had OSLib listed in !PackMan. To resolve this, I decided (slaps forehead) to delete all the PackMan files from my current build and do a complete re-install, OSLib is now available (…programs-armv5). Morale of this story check your source links, before deleting anything!

Not the Phantom updates, but I thought you might be interesed in what I’ve seen, so that we can confirm that this is expected behaviour or not.

The steps I took and what I saw:

1. Updated PackMan’s lists on start-up.
2. Pressed the offered upgrade-all button.
3. In the new window – 3 downloads offered, 0 Recommendations or suggestions. However there are 3 upgrades and a remove PackMan 0.9.4-1 listed as items to upgrade/configure.
4. Opened the PackMan listing window and there are only 3 upgrades.

Is this expected behaviour? Is Packman doing housekeeping?

Not the Phantom updates, but I thought you might be interested in what I’ve seen, so that we can confirm that this is expected behaviour or not.

I am interested – Thanks!
It’s not expected behaviour, it’s probably been in PackMan for a while.
I think I may have a fix for it. I’m working on getting another PackMan release to fix some RISC OS 4 problems and will put my fix into that.

Analysis of another failure:

Today, PackMan 0.9.4 offered upgrades to Fireworkz and PipeDream (plus their manuals).

The upgrade produced an error message “basic_ios::clear” – afterwards, the Fireworkz and PipeDream entries had disappeared from the package list (with blank lines where they used to be).

I moved the old versions of the packages out of the way (with a slight hiccup because PipeDream stores its documentation in two different places) and reran “Upgrade all”. This time the upgrade – now effectively an install – ran to completion. On re-examining the package list, all the PipeDream and Fireworkz entries had reappeared.

The “basic_ios::clear” error appears to happen when the package owner changes the directory structure of the package (in this case, PipeDream-Examples had moved the contents of the “Pictures” subdirectory to a new “ImageFiles.Drawfiles” subdirectory).

Lesson learned: When PackMan offers you lots of upgrades, do them one at a time. That way, you’ll know which one caused the error.

Stuart, thanks for reporting that failure. It showed two more errors in PackMan. It didn’t restore the old environment for a package after an error (a new problem) and it couldn’t upgrade by adding a file where one of it’s parent directories was a file in the older version of the package.

Both of these have been fixed now and I’ve just uploaded PackMan 0.9.5, so it should appear in the package lists tomorrow.

I’m hoping this release should fix all the problems reported here that I could reproduce.

Thank you for the updates… A minor observation, that may only relate to my machine, is that the What’s New filter doesn’t appear work. The list I have seems static. Is there a way for me to reset the filter?

I have tried several times to update Packman. My version is 4 years old today 0.9.1 Beta 04 May 2016.
This time I get the message SSl certificate problem: unable to get local issuer certificate.

What must I do to be saved?

What must I do to be saved?

Read the following announcement: https://www.riscosopen.org/forum/forums/1/topics/15212

Download and Install

*Provide some details… RISC OS version and computer?

Thanks, have done steps 1 and 2 above.
PackMan 0.9.5 Beta (13 April 2020) installed and run and sitting on icon bar.

Menu > Update lists

Still gives an error but a different one:-

“Failed to update package lists”
“error setting certificate verify locations”

Apart from not being able to update lists it appears to be working normally
eg Select click brings up PackMan list ok
Menu > Advanced options all work

ARMX6 5.25 (25 April 18)

“error setting certificate verify locations”

This one I recognise. From the PackMan icon bar menu, choose “Advanced > Sources” and disable the entry for jaspp.org uk – that should allow “Update lists” to run to completion. This allows you to confirm that PackMan is working, but you’ll be missing all the JASPP packages.

To get the JASPP entry working again, you have to install the AcornSSL module. This can be found in the “Nightly Beta HardDisc4” archive available from the Miscellaneous downloads page. You may prefer to do this via “Configuration > System > System Merge” as that updates the rest of !System at the same time.

Hi john,

It works and updates here Ok on an ARMX6 using the same ROM.

The only thing is I have ROOL’s latest disc updates.

I seem to recall that if people had issues they had to clear some files but I can’t fully remember the details or find the discussion about it.