We're not updating non-core modules to match the kernel - their version numbers change independently. So if photo-album is at 4.0, and it requires acs-kernel 4.0, and then the acs-core collection goes to 5.0 so acs-kernel goes to 5.0 but photo-album is unchanged, photo-album stays at 4.0.
I just went through each of the core packages and updated their version in the APM. Some notes I took along the way:
- The release date of each package is being updated to today when I save changes in the APM
- Some of the package info is very out of date
- There were a few packages that were missing the Primary Owner URL, and the package manager requires that info. So I looked up the owner's email addresses at openacs.org
- The list of core packages in CVS appears to be wrong: it's notifications, not acs-notification
- For some reason, acs-authentication/acs-authentication.info got checked
out with no write perms. It could be like that in CVS, too.
Now... I'm looking at a diff of my work and I see that the APM has made some unexpected changes. Perhaps someone at Collaboraid can confirm that these are all desirable changes? I'm not very familiar with the changes that have been made. They are attached in a file called diff.out.
I realized while looking over the diffs that I didn't do anything with the Requires. It looks like the APM has attempted to take care of that for me. For example, this is for acs-admin:
Requires service acs-kernel, version 4.6.2 (remove)
Provided by Kernel, version 5.0.0a4
Provided by Kernel, version 5.0.0a5
It seems to be updating, rather than replacing, the reference to a package that has been updated. Should I go through them all and remove and recreate these requires?