Forum OpenACS Development: Re: Is this a bug: right after creating pkg in APM, key is not known but should be
1. The package version is set up and marked enabled and installed.
2. You go to the "install packages" acs-admin page, and the package does not show up.
3. Apparently it is half-installed/half-not installed.
4. The reason is that no apm_package_type is created for the package, so it's in a semi-zombie state (this is why you can't install it, and if it allowed you to install it, it would scream because the version already exists!)
Jim, you can test this by going to psql and giving this command:
select * from apm_package_versions where package_key = 'your-package-key';
select * from apm_package_types where package_key = 'your-package-key'.
Torben, please remove your misleading change to the HTML page.
It would require a rewriting of the entire APM to get rid of this "install package upon creation" bit, because add depedencies, parameters, etc are all driven by the package version's params etc as stored in the database (not the XML info file).
So the right thing to do is to make the new package fully installed, as gross as that is, and I will do so this weekend, by making an entry in apm_package_types for the new package when it is created.
Does the apm_package_type mean (for now) service or app?
no apm_package_type is created for the packageYes it is, just tested in 5.5. I'll be posting a log. Here is the log: http://jam.sessionsnet.org/files/download/package-error-log.txt?file_id=5669