Not able to upgrade Foreman from v3.3 to v3.4

Problem: not able to upgrade Foreman from v3.3 to v3.4

Expected outcome: successful upgrade

Foreman and Proxy versions: Both v3.3

Foreman and Proxy plugin versions: Both v3.3

Distribution and version: Ubuntu 20.04

Other relevant data: I get the following output when using the upgrade procedure here Foreman :: Manual

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ruby-foreman-tasks : Depends: foreman (>= 3.4.0-2) but 3.4.0-1 is to be installed
E: Unable to correct problems, you have held broken packages.

I can confirm the problem. Installed a test machine today with Debian 11.5 and Foreman 3.4. When installing ruby-foreman-tasks I got the feedback:


Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ruby-foreman-tasks : Depends: foreman (>= 3.4.0-2) but 3.4.0-1 is to be installed
E: Unable to correct problems, you have held broken packages.

I downloaded ruby-foreman-tasks_7.0.0-2_all.deb from the plugin repo and unzipped the DEBIAN/control file to see that it explicitly mentions foreman (>= 3.4.0-2) as a dependency. But this version does not seem to be in the repository!?

1 Like

There were some intermediate problems, but by now you should see 3.4.0-2 in the repos and stuff should be able to upgrade again.

Can you confirm?

Hello @evgeni, the problem is still there.

The following packages have unmet dependencies:
 ruby-foreman-tasks : Depends: foreman (>= 3.4.0-2) but 3.4.0-1 is to be installed

Oooh, thanks for re-checking. I was thinking 3.3, not 3.4… Sorry!

3.4 had the right changes backported in explicitly vendor sinatra by ekohl · Pull Request #8514 · theforeman/foreman-packaging · GitHub but it seems the repo publishing for that failed: foreman-3.4-release-pipeline #5 [Jenkins]

I kicked off foreman-3.4-release-pipeline #6 [Jenkins] which should take about an hour to complete.

1 Like

Thanks! I’ll check again later and I’ll let you know :slight_smile:

Should be really fixed now :slight_smile:

It works now! Thanks again @evgeni.

1 Like

Great!

Thanks for reporting and testing.

And again, sorry for the initial slip!