You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run an AlmaLinux shop (rpm based), and I'd like to cleanly migrate from puppet-server to openvox-server, puppetdb to openvoxdb, etc. With the client, we were able to configure the rpms to cleanly upgrade from puppet-agent to openvox-agent by adding these fields to the spec file:
Replaces: puppet-agent
Obsoletes: puppet-agent
(Note the lack of version numbers, which is non-standard but it necessary here.)
I want to do the same thing with openvoxdb, openvox-server, openvoxdb-termini, and any other related rpms that I'm forgetting about.
The problem is that I can't figure out how. The build systems for the server, db, etc projects is not the same as it for the client; it uses ezbake, which is a leinengen plugin. There doesn't appear to be a place to add those fields in the build process.
This isn't quite a show-stopper for our migration, but it certainly ramps up the problem aggressively; I have plenty of existing puppet modules that are looking for puppetdb or puppet-server in particular, and I don't want to spend too much time fighting with them. And right now, trying to test rpms one at a time is a no-go, because these rpms directly conflict with each other (deploying the same files, etc).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I run an AlmaLinux shop (rpm based), and I'd like to cleanly migrate from puppet-server to openvox-server, puppetdb to openvoxdb, etc. With the client, we were able to configure the rpms to cleanly upgrade from puppet-agent to openvox-agent by adding these fields to the spec file:
(Note the lack of version numbers, which is non-standard but it necessary here.)
I want to do the same thing with openvoxdb, openvox-server, openvoxdb-termini, and any other related rpms that I'm forgetting about.
The problem is that I can't figure out how. The build systems for the server, db, etc projects is not the same as it for the client; it uses ezbake, which is a leinengen plugin. There doesn't appear to be a place to add those fields in the build process.
This isn't quite a show-stopper for our migration, but it certainly ramps up the problem aggressively; I have plenty of existing puppet modules that are looking for
puppetdb
orpuppet-server
in particular, and I don't want to spend too much time fighting with them. And right now, trying to test rpms one at a time is a no-go, because these rpms directly conflict with each other (deploying the same files, etc).Where do we start to fix this?
Beta Was this translation helpful? Give feedback.
All reactions