Jump to content

Package not found in repository


j-gray
 Share

Recommended Posts

I've been rolling out OS X clients with a scheduled task on dynamic group.

 

All of a sudden, the task is failing with the error, "Package not found in repository".

 

I found that there is a newer version of the client and the version I've been rolling out is no longer available.

 

How can I get the previous package back so that I can finish our rollout?

Link to comment
Share on other sites

  • ESET Staff

What package version you were rolling out? It might happen that it was replaced, due to reported issues with the macOS sierra installation. Was it 6.3 already?

Link to comment
Share on other sites

What package version you were rolling out? It might happen that it was replaced, due to reported issues with the macOS sierra installation. Was it 6.3 already?

We were rolling out 6.3.85.0

 

It looks like it was replaced by 6.3.85.1

Link to comment
Share on other sites

I believe this was reported previously, there was a proposal to keep older versions in the repository to guard against this. I guess it hasn't happened yet.

Yes, I thought there was a previous thread, but I could not locate it.

 

There is a checkbox to select legacy software, but those packages are much older.

 

 

ESET:  please allow customers to chose the version of software they wish to install.

 

This really causes issues when you take away software in the middle of a rollout.

 

We finally completed testing of 6.3.85 and now it appears to be no longer available.

Link to comment
Share on other sites

  • ESET Staff

As you can see, the build number is not changed, only the last suffix. Installer was repacked, with a little change in the installer, to support local installation on macOS Sierra, which was having issues due to gatekeeper. That was the reason, for not keeping two (basically same) versions of mac product in repository. In case of the last month rollout of server products, we have kept all of the older versions, and we are planning to do this in the future as well.

Link to comment
Share on other sites

As you can see, the build number is not changed, only the last suffix.

Yes, I understand this.  However, because it is a new version, we're required to test it before we deploy it to the masses. This is common practice.

 

It also breaks the current deployment task because the specified package is no longer available, and it forces us to stop our current deployment, again, because the package we were deploying is no longer available.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...