907550 – app-admin/syslog-ng-4.2.0[python]: private virtualenv is not initialized

Bug 907550 - app-admin/syslog-ng-4.2.0[python]: private virtualenv is not initialized

Summary: app-admin/syslog-ng-4.2.0[python]: private virtualenv is not initialized

Status:	CONFIRMED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal with 3 votes (vote)
Assignee:	Tomáš Mózes

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2023-06-01 04:43 UTC by Andrey Grozin
Modified:	2023-12-28 20:25 UTC (History)
CC List:	8 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Andrey Grozin gentoo-dev

2023-06-01 04:43:11 UTC

Recently, every time I boot my notebook, I see the message

[date-time] python: private virtualenv is not initialized, use the `syslog-ng-update-virtualenv' script to initialize it or make sure all required Python dependencies are available in the system Python installation: path='/var/lib/syslog-ng-venv'

(twice during each boot). Why does syslog-ng use a venv? I suppose all python dependencies are listed in the ebuild.

Comment 1 Cheyenne Wills 2023-08-21 19:17:54 UTC

I'm getting the same message as well -- just got the upgrade from syslog-ng 4.0.1 to 4.2.0

Comment 2 Fernando 2023-08-22 20:07:06 UTC

Same thing here after upgrading to 4.2.0, ended up disabling python use flag while this gets resolved.

Comment 3 Klemen Mihevc 2023-09-25 12:22:48 UTC

fixed in syslog-ng-4.3.1

Comment 4 Robert R. Richter 2023-12-28 20:25:08 UTC

please stabilize syslog-ng-4.3.1