Bug#1037178: puppet does not sync files anymore after recent ruby2.5 security upload

2023-06-09 Thread Schmidt, Bernhard
Am Mittwoch, dem 07.06.2023 um 15:28 +0200 schrieb Bernhard Schmidt:

Hi Utkarsh,


> > > Yep, I'm taking a look to prep something for 2.5.
> > 
> > I've prepared a fix for the regression and uploaded the binaries
> > at:
> > https://people.debian.org/~utkarsh/lts/ruby2.5/
> > 
> > Can you please give these a try and see if that fixes the
> > regression you're seeing?
> 
> Looking good!

Any news here?

Bernhard


Bug#1037178: puppet does not sync files anymore after recent ruby2.5 security upload

2023-06-07 Thread Schmidt, Bernhard
Am Mittwoch, dem 07.06.2023 um 18:47 +0530 schrieb Utkarsh Gupta:

Hi,

> > Yep, I'm taking a look to prep something for 2.5.
> 
> I've prepared a fix for the regression and uploaded the binaries at:
> https://people.debian.org/~utkarsh/lts/ruby2.5/
> 
> Can you please give these a try and see if that fixes the regression
> you're seeing?

Looking good!

# puppet agent --test
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Error: /File[/var/lib/puppet/facts.d]: Failed to generate additional
resources using 'eval_generate': Failed to open TCP connection to :8140
(Connection refused - connect(2) for "" port 8140)
Error: /File[/var/lib/puppet/facts.d]: Could not evaluate: Could not
retrieve file metadata for puppet:///pluginfacts: Failed to open TCP
connection to :8140 (Connection refused - connect(2) for "" port 8140)
Info: Retrieving plugin
Error: /File[/var/lib/puppet/lib]: Failed to generate additional
resources using 'eval_generate': Failed to open TCP connection to :8140
(Connection refused - connect(2) for "" port 8140)
Error: /File[/var/lib/puppet/lib]: Could not evaluate: Could not
retrieve file metadata for puppet:///plugins: Failed to open TCP
connection to :8140 (Connection refused - connect(2) for "" port 8140)
Info: Retrieving locales
[..]


# dpkg -i libruby2.5_2.5.5-3+deb10u6_amd64.deb
(Reading database ... 69723 files and directories currently installed.)
Preparing to unpack libruby2.5_2.5.5-3+deb10u6_amd64.deb ...
Unpacking libruby2.5:amd64 (2.5.5-3+deb10u6) over (2.5.5-3+deb10u5) ...
Setting up libruby2.5:amd64 (2.5.5-3+deb10u6) ...
Processing triggers for libc-bin (2.28-10+deb10u2) ...

# puppet agent --test
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Retrieving locales
Info: Loading facts
Info: Caching catalog for xxx.lrz.de
Info: Applying configuration version 'master-3a083818c9e2'
Notice: Applied catalog in 3.86 seconds

Bernhard


Bug#737262: [Pkg-systemd-maintainers] Bug#737262: systemd: Possible memory leak in systemd-journald

2014-02-01 Thread Schmidt, Bernhard
Hi,

 Bernhard Schmidt bernhard.schm...@lrz.de writes:
 Package: systemd
 Version: 44-11+deb7u4
 […]
 I think there is a small memory leak in wheezy's systemd-journald. 
 Yeah, journald in version 44 is buggy in many aspects. Please upgrade.

I’d love to, but there is no newer version available for Wheezy. As soon as 
systemd 204 is available in backports I’ll consider upgrading.

I’ve installed a cronjob to restart systemd-journald.service every night for 
now.

Bernhard

--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org