https://www.puppet.com/community logo
Join Slack
Powered by
# voxpupuli
  • v
    i managed to kick src:puppet 5 from testing and unstable too, which, phew, we won't ship it with bookworm at least
  • v
    our biggest challenge right now is the puppetserver
  • v
    because jruby
  • v
  • v
    we're in #debian-puppet on irc.oftc.net
  • v
    so yeah, try out the puppet-agent 7, it works here, in bookworm
  • v
    I get that, but for now I mostly care about the agent
  • v
    i doubt a backport for bullseye is possible
  • v
    because, again, ruby 3
  • v
    my plan is to just go to bookworm asap
  • v
    why is ruby 3 a factor here?
  • v
    pun intended? :)
  • v
    i think because puppet agent has some ruby 3 deps or something
  • v
    i'm not sure
  • v
    no, it was not intended :P
  • v
    I doubt that since Puppet 7 AIO runs on Ruby 2.7
  • v
    it was more the other way around: only Puppet agent 7.19 has proper Ruby 3 support (without deprecation warnings)
  • v
    shrugs
  • v
    i wouldn't be surprised if puppet agent 7 crashes in flames in stable
  • v
    but i could be wrong
  • v
    actually, looking at the build deps, it might just work
  • v
    well, the background is that puppetlabs-* has merged patches that pass exec { 'cmd': command => [...] } and that's a Puppet 6 feature
  • v
    fantastic
  • v
    hardening is IMHO a good thing, but what I just ran into
  • v
    so I wonder if it would be possible to build the Puppet Agent 7.x packages in bullseye-backports
  • v
    ah well
  • v
    Depends: ruby-sorted-set but it is not installable
  • v
    so there's that already
  • v
    you'd need to backport that first
  • v
    which requires you backporting ruby-rbtree
1...155156157...648Latest