https://voxpupuli.org/ logo
Join Slack
Powered by
Hey all, a very small OpenVox 9 release update thi...
# announce
c
Hey all, a very small OpenVox 9 release update this week: we now have dedicated 
openvox9
repositories and 
openvox9-release
packages on the testing server! These can be downloaded from the same location as the 
openvox8-release
packages: • https://s3.osuosl.org/openvox-artifacts/index.html#repo_test/apt/ • https://s3.osuosl.org/openvox-artifacts/index.html#repo_test/yum/ Last weeks 
9.0.0.alpha1
builds have been published to these new testing repositories and future builds of OpenVox 9 will show up there instead of in the 
openvox8
repos.
🎉 8
thumbsup party 1
b
These builds seem to report their version number as 8.26.2…
c
Yes. See caveats in the previous release announcement: https://voxpupuli.slack.com/archives/C07N0HBE22V/p1779326330901209
b
Perhaps, but it’s very confusing when trying to work out which nodes I’ve got 9.0.0.alpha1 installed on when they all self-report as 8.26.2…
c
Yes, agreed. It is something that is already on the fix list.
👍 1
Looks like 
/opt/puppetlabs/puppet/VERSION
has the right number, which might help for tracking which agents are running the new build:
Copy code
# cat /opt/puppetlabs/puppet/VERSION
9.0.0.alpha1
The underlying reason the the 
alpha1
release still reports 
8.26.2
is that the GitHub Actions workflows that bump that version number don't quite support pre-releases. Among other things, they would have made a mess out of the CHANGELOG. Once those actions are fixed, we can do a more normal release.
b
Yep, it’s 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/version.rb
where the problem is AFAICT
And a slightly hacky workaround is to do this:
Copy code
ln -sfn ../../../../VERSION /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/VERSION
(or the equivalent file resource, naturally)
Open in Slack
PreviousNext
Powered by