Running into an issue with `ortussolutions/command...
# box-products
c
Running into an issue with
ortussolutions/commandbox:adobe2021
I am unable to use cfpm to install any packages. I am getting the error CommandBox> cfpm install mail run /bin/bash "/usr/local/lib/serverHome/WEB-INF/cfusion/bin/cfpm.sh" install mail One or more packages require the server to be at update 5. Since the server is at update 4, you must install the update 5 of the server. After upgrading the server update, the packages can be installed.
πŸ‘ 1
c
I saw someone report on the #adobe channel that when they updated to 2021u5 it wiped out their packages, so I'm guessing that the package registry is somehow tied to the latest update level of CF (whether by design or not is questionable). https://cfml.slack.com/archives/C06TABBT8/p1665504021809989?thread_ts=1665501468.420899&cid=C06TABBT8
πŸ‘ 1
m
We are looking into this. I believe the package manager is not allowing updates to new packages if the update level is < 5 on CF2021. I'm not sure if this is related to a security issue or not.
πŸ‘ 2
p
Ya, I just posted on this in the Box channel. The ForgeBox image needs to be updated to Update 5. Currently caught in a catch 22.
πŸ‘ 1
b
@Peter Amiri @Mark Takata (Adobe) This is a known behavior that Adobe has said is "working as designed". I think it's a fairly large oversight on their part and have entered this ticket https://tracker.adobe.com/#/view/CF-4215444
βž• 1
@Peter Amiri It's not quite a catch-22,-- you can fix it by adding versions to all your packages which is incredibly time consuming and changes with every version!
In the format of
Copy code
cfpm install zip:2021.0.02.328618
πŸ‘ 1
@jclausen Should have the new Adobe CF engines up on ForgeBox by tomorrow so you can start testing them
p
Thanks @bdw429s . Didn't know about versioning each package. I may do that anyway since this is going into a testing suite and I don't want the container changing on me without me knowing it.
b
It's in the help command for
cfpm
πŸ™‚
You can run
cfpm listall
to see all the available versions
But it's a total pain since not every core CF version gets a new module version
So you have to go through your modules individually every time Adobe has a release to see what the current module versions are.
p
At least it won’t break next time there is an update released. That would be worth the time put in to figure out all the versions.
c
Thanks for everyone's feedback, I'll dive back into this one tomorrow. These small issues and production breaking bugs make me realize that this will be my last ACF version. We will be moving to Lucee.
b
@Peter Amiri If you do pin the versions, just ensure you always re-check them with every version so you don't get behind
c
Going back 1 version for each package resolved the immediate issue. I will keep them versioned moving forward, but it makes me wonder if there is a way to download and add the files to my repo and use the files from there instead of depending on Adobe?
m
Cavan I believe so. https://helpx.adobe.com/coldfusion/using/coldfusion-package-manager.html Look at the "configure local repository" section.
You can download the repo and then install packages from there. this was designed for a firewalled or otherwise isolated install, but I see no reason why you couldn't do this as an alternative in your case.