Bug#1009643: [Pkg-puppet-devel] Bug#1009643: Puppet: Fails to work with Ruby 3.0
* Antoine Beaupré [Mon Oct 03, 2022 at 12:28:06PM -0400]: > On 2022-10-03 18:21:46, Michael Prokop wrote: > > AFAICT (thanks to our daily Grml ISO builds) this RC bug caused > > puppet to get removed from Debian/testing, so unless this gets fixed > > we won't have puppet in bookworm? Is anyone taking care of this? > > Puppet 5 has been EOL for years. It's a good thing it's gone from > bookworm, and a deliberate act on part of the Puppet package > maintainers. ACK :) > We've packaged puppet-agent 7 and uploaded to unstable, it should > trickle down in bookworm in a day or two if all goes well. Oh, that's great news! :) > We're working on packaging puppetserver 7. You can follow that work and > more here: > https://wiki.debian.org/Teams/Puppet/Work Thanks, both for your fast response as well as working on the puppet packaging! \o/ regards -mika- signature.asc Description: PGP signature
Bug#1009643: [Pkg-puppet-devel] Bug#1009643: Puppet: Fails to work with Ruby 3.0
On 2022-10-03 18:21:46, Michael Prokop wrote: > AFAICT (thanks to our daily Grml ISO builds) this RC bug caused > puppet to get removed from Debian/testing, so unless this gets fixed > we won't have puppet in bookworm? Is anyone taking care of this? Puppet 5 has been EOL for years. It's a good thing it's gone from bookworm, and a deliberate act on part of the Puppet package maintainers. We've packaged puppet-agent 7 and uploaded to unstable, it should trickle down in bookworm in a day or two if all goes well. We're working on packaging puppetserver 7. You can follow that work and more here: https://wiki.debian.org/Teams/Puppet/Work A. -- Imagine a world in which every single person on the planet is given free access to the sum of all human knowledge. - Jimmy Wales, co-founder of Wikipedia
Bug#1009643: [Pkg-puppet-devel] Bug#1009643: Puppet: Fails to work with Ruby 3.0
Hi! * Antoine Beaupré [Tue Aug 30, 2022 at 05:15:58PM -0400]: > On 2022-08-25 14:19:42, Antoine Beaupré wrote: > > > For what it's worth, I have tested lavamind's Puppet 7 package from > > experimental, on bookworm, and it works fine: > > > > https://tracker.debian.org/pkg/puppet-agent > > > > ... I am not sure how to express this in the BTS here, because it's a > > different source package, so I can't mark it as fixed there without > > first marking it as affecting that other package, but it never affected > > it. > > The correct way seems to be to move this bug report back to src:puppet > where it belongs, which this message should do. AFAICT (thanks to our daily Grml ISO builds) this RC bug caused puppet to get removed from Debian/testing, so unless this gets fixed we won't have puppet in bookworm? Is anyone taking care of this? regards -mika- signature.asc Description: PGP signature
Processed: Re: [Pkg-puppet-devel] Bug#1009643: Puppet: Fails to work with Ruby 3.0
Processing control commands: > reassign -1 src:puppet Bug #1009643 [puppet] Puppet: Fails to work with Ruby 3.0 Bug reassigned from package 'puppet' to 'src:puppet'. No longer marked as found in versions puppet/5.5.22-4. Ignoring request to alter fixed versions of bug #1009643 to the same values previously set -- 1009643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009643 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1009643: [Pkg-puppet-devel] Bug#1009643: Puppet: Fails to work with Ruby 3.0
Control: reassign -1 src:puppet On 2022-08-25 14:19:42, Antoine Beaupré wrote: [...] > For what it's worth, I have tested lavamind's Puppet 7 package from > experimental, on bookworm, and it works fine: > > https://tracker.debian.org/pkg/puppet-agent > > ... I am not sure how to express this in the BTS here, because it's a > different source package, so I can't mark it as fixed there without > first marking it as affecting that other package, but it never affected > it. The correct way seems to be to move this bug report back to src:puppet where it belongs, which this message should do. -- A man is none the less a slave because he is allowed to choose a new master once in a term of years. - Lysander Spooner
Bug#1009643: Puppet: Fails to work with Ruby 3.0
On 2022-04-14 10:49:43, Antoine Beaupré wrote: > On 2022-04-13 17:26:27, Gabriel Filion wrote: >> Hi there, >> >> For what it's worth, upstream puppet does not yet suppport ruby 3.0. >> >> see: https://puppet.com/docs/puppet/7/release_notes_puppet.html >> >> puppet 7 added support for ruby 2.7 but 2.9 and 3.0 were never there >> upstream. I'm guessing they'll bump to 3.x for the puppet 8 cycle only. > > That's actually not quite correct: Puppet 7.8 added support for Ruby 3, > so we should be able to jump there. > > It is my hope that we can ship Puppet agent 6 and Puppet server 7 in > bookworm to fix all of those issues in one fell swoop. See: > > https://alioth-lists.debian.net/pipermail/pkg-puppet-devel/2022-April/012681.html > > I don't think it's worth fixing the Puppet 5.5 packages to be honest, > our energy is better spent updating to upstream packages. For what it's worth, I have tested lavamind's Puppet 7 package from experimental, on bookworm, and it works fine: https://tracker.debian.org/pkg/puppet-agent ... I am not sure how to express this in the BTS here, because it's a different source package, so I can't mark it as fixed there without first marking it as affecting that other package, but it never affected it. Anyways, just to say that this is fixed in experimental. :) -- A developed country is not a place where the poor have cars. It's where the rich use public transportation. - Gustavo Petro
Bug#1009643: Puppet: Fails to work with Ruby 3.0
On 2022-04-13 17:26:27, Gabriel Filion wrote: > Hi there, > > For what it's worth, upstream puppet does not yet suppport ruby 3.0. > > see: https://puppet.com/docs/puppet/7/release_notes_puppet.html > > puppet 7 added support for ruby 2.7 but 2.9 and 3.0 were never there > upstream. I'm guessing they'll bump to 3.x for the puppet 8 cycle only. That's actually not quite correct: Puppet 7.8 added support for Ruby 3, so we should be able to jump there. It is my hope that we can ship Puppet agent 6 and Puppet server 7 in bookworm to fix all of those issues in one fell swoop. See: https://alioth-lists.debian.net/pipermail/pkg-puppet-devel/2022-April/012681.html I don't think it's worth fixing the Puppet 5.5 packages to be honest, our energy is better spent updating to upstream packages. -- That's the kind of society I want to build. I want a guarantee - with physics and mathematics, not with laws - that we can give ourselves real privacy of personal communications. - John Gilmore
Bug#1009643: Puppet: Fails to work with Ruby 3.0
Hi there, For what it's worth, upstream puppet does not yet suppport ruby 3.0. see: https://puppet.com/docs/puppet/7/release_notes_puppet.html puppet 7 added support for ruby 2.7 but 2.9 and 3.0 were never there upstream. I'm guessing they'll bump to 3.x for the puppet 8 cycle only.
Bug#1009643: Puppet: Fails to work with Ruby 3.0
Package: puppet
Version: 5.5.22-4
Severity: serious
Justification: Fails at core functions
Since testing switched /usr/bin/ruby to use ruby3.0, a previously working
Puppet manifest fails:
s...@larsa.muc:/tmp$ ruby3.0 /usr/bin/puppet apply t.pp
Notice: Compiled catalog for larsa.muc.corp.google.com in environment
production in 0.01 seconds
Error: Could not set 'link' on ensure: wrong number of arguments (given 3,
expected 2) (file: /tmp/t.pp, line: 1)
Error: Could not set 'link' on ensure: wrong number of arguments (given 3,
expected 2) (file: /tmp/t.pp, line: 1)
Wrapped exception:
wrong number of arguments (given 3, expected 2)
Error: /Stage[main]/Main/File[/tmp/testme123]/ensure: change from 'absent'
to 'link' failed: Could not set 'link' on ensure: wrong number of arguments
(given 3, expected 2) (file: /tmp/t.pp, line: 1)
Notice: Applied catalog in 0.02 seconds
s...@larsa.muc:/tmp$ cat t.pp
file {"/tmp/testme123":
ensure => symlink,
target => "/tmp/t.pp",
}
