Control: severity -1 serious
Justification: this package depends on ruby 2.7, gone from bookworm. See
below.
On 2022-04-14 10:12:25, Gabriel Filion wrote:
> in current debian testing, ruby has been transitioned to 3.0 and judging
> from the release history, puppet has not added support for ruby
Hi there,
I'm just chiming in to add yet another object on the scale:
in current debian testing, ruby has been transitioned to 3.0 and judging
from the release history, puppet has not added support for ruby 3.0
until 7.8.0:
On 2022-03-31 17:05:19, Thomas Goirand wrote:
> On 3/29/22 21:08, Antoine Beaupré wrote:
>> On 2020-02-02 13:06:42, Thomas Goirand wrote:
>>
>> [...]
>>
>>> FYI, I packaged and uploaded the first 2 so far, but can't push to Git.
>>> Please set me as maintainer or owner, so I can do that.
>>>
>>>
On 3/29/22 21:08, Antoine Beaupré wrote:
On 2020-02-02 13:06:42, Thomas Goirand wrote:
[...]
FYI, I packaged and uploaded the first 2 so far, but can't push to Git.
Please set me as maintainer or owner, so I can do that.
Note that I'm doing a git based workflow, packaging upstream tags,
On 2022-03-31 12:05:01, Thomas Goirand wrote:
> On 3/29/22 21:21, Antoine Beaupré wrote:
>> On 2022-03-29 21:14:42, Thomas Goirand wrote:
>>> On 3/29/22 20:58, Antoine Beaupré wrote:
On 2020-05-16 21:13:25, Martin Konrad wrote:
> Hi,
>> The others are related to other operating
On 3/29/22 21:21, Antoine Beaupré wrote:
On 2022-03-29 21:14:42, Thomas Goirand wrote:
On 3/29/22 20:58, Antoine Beaupré wrote:
On 2020-05-16 21:13:25, Martin Konrad wrote:
Hi,
The others are related to other operating systems than Debian, so I
really wonder if we need them (yum, really? zfs
On 2022-03-29 15:21:52, Antoine Beaupré wrote:
> On 2022-03-29 21:14:42, Thomas Goirand wrote:
[...]
>> At this time, maybe we should giveup on having jruby work with Ruby 3,
>> and accept the parts of it which are embedded (like the ruby
>> interpreter).
>
> Yeah, that would make sense I think.
On 2022-03-29 15:21:52, Antoine Beaupré wrote:
[...]
> Again, I'm coming at this a little from the outside and I'm just trying
> to see what the way forward is right now. Just today I had to downgrade
> jetty9 after the buster point upgrade for some obscure reason, and I
> can't help but think
On 2022-03-29 21:14:42, Thomas Goirand wrote:
> On 3/29/22 20:58, Antoine Beaupré wrote:
>> On 2020-05-16 21:13:25, Martin Konrad wrote:
>>> Hi,
The others are related to other operating systems than Debian, so I
really wonder if we need them (yum, really? zfs and zone are for
On 3/29/22 20:58, Antoine Beaupré wrote:
On 2020-05-16 21:13:25, Martin Konrad wrote:
Hi,
The others are related to other operating systems than Debian, so I
really wonder if we need them (yum, really? zfs and zone are for
Solaris, and scheduled_task is for windows...).
If we want to make
On 2020-02-02 13:06:42, Thomas Goirand wrote:
[...]
> FYI, I packaged and uploaded the first 2 so far, but can't push to Git.
> Please set me as maintainer or owner, so I can do that.
>
> Note that I'm doing a git based workflow, packaging upstream tags,
> rather than using pristine-tar. If this
On 2020-05-16 21:13:25, Martin Konrad wrote:
> Hi,
>> The others are related to other operating systems than Debian, so I
>> really wonder if we need them (yum, really? zfs and zone are for
>> Solaris, and scheduled_task is for windows...).
> If we want to make transitioning from Puppet 5 to
Hi,
> The others are related to other operating systems than Debian, so I
> really wonder if we need them (yum, really? zfs and zone are for
> Solaris, and scheduled_task is for windows...).
If we want to make transitioning from Puppet 5 to Puppet 6 as easy as
possible I think there is no way
On 2/2/20 1:06 PM, Thomas Goirand wrote:
> On 2/1/20 10:51 AM, Stig Sandbeck Mathisen wrote:
>> Thomas Goirand writes:
>>
>>> Could you list them? I'd be ok to do that work within the team, if
>>> someone else is working on Puppet itself.
>>
>> >From the "puppet-agent" repository, at
>>
Thomas Goirand writes:
> Note that I'm doing a git based workflow, packaging upstream tags,
> rather than using pristine-tar. If this bothers anyone, please let me
> know (but please only complain about the workflow if you really have
> the intention to contribute to the packaging, otherwise
On 2/1/20 10:51 AM, Stig Sandbeck Mathisen wrote:
> Thomas Goirand writes:
>
>> Could you list them? I'd be ok to do that work within the team, if
>> someone else is working on Puppet itself.
>
>>From the "puppet-agent" repository, at
>
Thomas Goirand writes:
> Could you list them? I'd be ok to do that work within the team, if
> someone else is working on Puppet itself.
>From the "puppet-agent" repository, at
https://github.com/puppetlabs/puppet-agent/blob/6.4.x/configs/projects/puppet-agent.rb#L116
puppetlabs-augeas_core
On 1/30/20 7:23 AM, Stig Sandbeck Mathisen wrote:
> Antoine Beaupre writes:
>
>> ... the upgrade from 5 to 6 doesn't involve much churn in the DSL, so
>> it's not as big of a deal as the 3 to 4 or 4 to 5 migrations we had to
>> suffer through. The tooling does change, however, so it might be
>>
Antoine Beaupre writes:
> ... the upgrade from 5 to 6 doesn't involve much churn in the DSL, so
> it's not as big of a deal as the 3 to 4 or 4 to 5 migrations we had to
> suffer through. The tooling does change, however, so it might be
> tricky on the packaging side (which is why, I am guessing,
Package: puppet
Version: 5.5.10-4
Severity: important
Puppet 5.5 will reach end of life in November 2020, before Debian
Buster does (~2022):
https://puppet.com/docs/puppet/5.5/about_agent.html
(Since this page can basically disappear at any time in the future
(because they regularly archive
20 matches
Mail list logo
