Do all of the packages for CF2021/CF2023 get updated every time a ColdFusion update is released? Ben Nadel is having issues installing packages using the latest CF2021 update level on Docker: https://twitter.com/BenNadel/status/1680906460107096064?s=20

Not all packages always update

I think Ben is having the reverse issue: he's on the latest cf engine, but he's worried that there are no packages with a matching update level. Which I think is perfectly normal and shouldn't be a problem.

I could see starting at 1.0 being a problem if you need different versions for CF2021 vs CF2023 vs CFNext, etc.

Voted on CF-4215444. Would be a great improvement.

Seems to be some weirdness with the Adobe API urls. It worked earlier today for a little bit but now CFPM is broken again.

The packages repository <https://www.adobe.com/go/bundlesdependency.json> is not accessible.

The URL for the remote

bundlesdependency.json

seems to be incorrect ( but looks like it’s hard-coded in the

cfpm

implementation code somewhere. The correct URLs are in

WEB-INF/cfusion/lib/neo_updates.xml

but CFPM is not using them. The HF installers should also be updating that

bundlesdependency.json

- but it looks like it only gets updated when you log in to the admin and then navigate to the package management page. When I try to do CFPM installs I get this:

The packages repository <https://www.adobe.com/go/bundlesdependency.json> is not accessible. You can only load the packages that are available locally in the WEB-INF\bundles directory
The following packages will be installed : adminapi:2021.0.05.330109,administrator:2021.0.06.330132,caching:2021.0.05.330109,orm:2021.0.05.330109,document:2021.0.05.330109,image:2021.0.
05.330109,pdf:2021.0.05.330109,htmltopdf:2021.0.05.330109,awss3:2021.0.05.330109,db2:2021.0.05.330109,sqlserver:2021.0.05.330109,zip:2021.0.05.330109,spreadsheet:2021.0.05.330109,mail:2
021.0.05.330109,redissessionstorage:2021.0.05.330109,chart:2021.0.05.330109,debugger:2021.0.05.330109,ajax:2021.0.05.330109,ftp:2021.0.05.330119 packages and their dependencies will be installed. The installation time can be as much as 6 minutes.
<https://www.adobe.com/go/bundlesdependency.json> cannot be downloaded. Error : Not Found.
Downloading the package adminapi-2021.0.05.330109.zip
<https://www.adobe.com/go/adminapi-2021.0.05.330109.zip> cannot be downloaded. Error : Not Found.
The package adminapi is marked for installation. Installation will be done, on the next server start.
<https://www.adobe.com/go/bundlesdependency.json> cannot be downloaded. Error : Not Found.
Downloading the package adminapi-2021.0.05.330109.zip
<https://www.adobe.com/go/adminapi-2021.0.05.330109.zip> cannot be downloaded. Error : Not Found.
Downloading the package administrator-2021.0.06.330132.zip
<https://www.adobe.com/go/administrator-2021.0.06.330132.zip> cannot be downloaded. Error : Not Found.
The package administrator is marked for installation. Installation will be done, on the next server start.
Downloading the dependent package commons-jcs-core-2.1.jar
Downloading the dependent package ehcache-web-2.0.4.jar
Downloading the dependent package commons-pool2-2.4.2.jar
Downloading the dependent package commons-logging-1.2.jar
Downloading the dependent package spymemcached-2.10.3.jar
Downloading the dependent package jedis-2.9.0.jar
Downloading the dependent package slf4j-api-1.7.12.jar
An error has occurred while installing the package caching. Exception : <https://www.adobe.com/go/repo/ehcache-web-2.0.4.jar> cannot be downloaded. Error : Not Found.
caching package is uninstalled successfully.
..... lots more of this ...

cc/@Mark Takata (Adobe)

@priyank_adobe @Bagish Mishra potential update fault in our package manager or the endpoint misbehaving

All, for the last 2 updates, there was no change in packages. We create the package zip as we have customers who doesn't have access to internet and if they are installing the update from older update level, then they would need the entire package.

@priyank_adobe I can confirm, though, when updated using the jar updater, that performing a CFPM install without versions on the packages to install throws an error. See the log output above. It’s trying to connect to

<https://www.adobe.com/go/bundlesdependency.json>

which delivers a 404 and, because it defaults back to the local

bundlesdependency.json

and tries to use that. The problem is that some of the nested dependency versions from the previous release’s

bundlesdependency.json

( e.g.

<https://www.adobe.com/go/repo/ehcache-web-2.0.4.jar>

) longer exist.

@jclausen We will check and get back to you.

Right. But that is not the one that the

cfpm

shell script seems to use. There are also totally different URLs, which redirect to other URLs in the

neo_updates.xml

file in `cfusion/lib`:

<update autocheck="false" checkinterval="10" checkperiodically="false" sendupdate="true">
	<url><https://www.adobe.com/go/coldfusion-updates></url>
	<defaulturl><https://www.adobe.com/go/coldfusion-updates></defaulturl>
	<packagesurl><https://www.adobe.com/go/coldfusion-packages></packagesurl>
	<defaultpackagesurl><https://www.adobe.com/go/coldfusion-packages></defaultpackagesurl>
	<notification>
		<emaillist/>
		<fromemail/>
	</notification>
</update>