-
If I understand correctly, the bdrv builds without errors for VanillaDpup 11.0. My initial local build of TrixiePup64 11.0 works nicely when BUILD_BDRV=no in _00build.conf, but fails when BUILD_BDRV=yes. I see the following errors when generating the bdrv (full log attached below): Some packages could not be installed. This may mean that you have The following packages have unmet dependencies:
The following libelogin0 and systemd packages are successfully downloaded to the TrixiePup64 local-build repositories: /tmp/Trixiepup64_build/local-repositories/x86_64/packages-deb-trixie/libelogind0_252.9-1debian2_amd64.deb Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052064. Packages that depends on libsystemd cannot be installed on a system with sysvinit instead of systemd, because libelogind is too old (<254) and some packages (like procps) need (libsystemd|libelogind)>=254. Once this is fixed in Debian, build should pass.
It's built using a fork of woof-CE that allows systemd in bdrv. The build passes but the result is much bigger. This is a temporary solution until elogin in trixie is usable again. In general, don't be surprised if trixie breaks at least every once in a while, while it's so far from release. sid breaks even more often. |
Beta Was this translation helpful? Give feedback.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052064.
Packages that depends on libsystemd cannot be installed on a system with sysvinit instead of systemd, because libelogind is too old (<254) and some packages (like procps) need (libsystemd|libelogind)>=254.
Once this is fixed in Debian, build should pass.
It's built using a fork of woof-CE that allows systemd in bdrv. The build passes but the result is much bigger. This is a temporary solution until elogin in trixie is usable again.
In general, don't be surprised if trixie breaks at least every once in a while, while it's so far from release. sid …