I've sent a summary of discussion about this upstream and will wait for
their response, and there's something I still want to ask for clarification.
On 1/9/25 12:55, Michael Biebl wrote:
Am 08.01.25 um 19:44 schrieb Chris Knadle:
Hello, Michael.
I'm emailing again because I've tried again to
On 1/14/25 14:38, Michael Biebl wrote:
Am 14.01.25 um 16:11 schrieb Diederik de Haas:
On Tue Jan 14, 2025 at 3:49 PM CET, Diederik de Haas via
Pkg-voip-maintainers wrote:
On Thu Jan 9, 2025 at 6:55 PM CET, Michael Biebl wrote:
No, all you are supposed to do in your .install files is to use t
On Tue Jan 14, 2025 at 8:38 PM CET, Michael Biebl wrote:
> Am 14.01.25 um 16:11 schrieb Diederik de Haas:
> > On Tue Jan 14, 2025 at 3:49 PM CET, Diederik de Haas via
> > Pkg-voip-maintainers wrote:
> >> On Thu Jan 9, 2025 at 6:55 PM CET, Michael Biebl wrote:
> >>> No, all you are supposed to do i
Am 14.01.25 um 16:11 schrieb Diederik de Haas:
On Tue Jan 14, 2025 at 3:49 PM CET, Diederik de Haas via Pkg-voip-maintainers
wrote:
On Thu Jan 9, 2025 at 6:55 PM CET, Michael Biebl wrote:
No, all you are supposed to do in your .install files is to use the
correct paths
/usr/lib/systemd/system/
On Tue Jan 14, 2025 at 3:49 PM CET, Diederik de Haas via Pkg-voip-maintainers
wrote:
> On Thu Jan 9, 2025 at 6:55 PM CET, Michael Biebl wrote:
> > No, all you are supposed to do in your .install files is to use the
> > correct paths
> > /usr/lib/systemd/system/foo.service
> > /usr/lib/sysusers.d/
Hi Michael,
On Thu Jan 9, 2025 at 6:55 PM CET, Michael Biebl wrote:
> >> You install systemd-dev (including systemd.pc), the build system picks
> >> up the paths from systemd.pc via pkgconf and installs the files into
> >> the correct paths. All you need to do in .install is reference the now
>
On Fri Jan 10, 2025 at 1:53 PM CET, Chris Hofstaedtler wrote:
> Yes, we expect Debian package maintainers to implement the simple thing.
In a project I'm part of there is this running joke:
"You sound like Diederik"
It involves kernel stuff and periodically there needs to be a rebase
onto a new u
Hi,
On Thu, Jan 09, 2025 at 06:42:00PM -0500, Chris Knadle wrote:
> On 1/9/25 12:55, Michael Biebl wrote:
> > Am 08.01.25 um 19:44 schrieb Chris Knadle:
> > > Hello, Michael.
> > >
> > > I'm emailing again because I've tried again to follow the
> > > suggestions that were made for this bug, and i
Hello Michael.
On 1/9/25 12:55, Michael Biebl wrote:
Am 08.01.25 um 19:44 schrieb Chris Knadle:
Hello, Michael.
I'm emailing again because I've tried again to follow the suggestions
that were made for this bug, and it is not working.
On 11/22/24 06:09, Michael Biebl wrote:
Again, I don't un
On Wed, 8 Jan 2025 13:44:33 -0500 Chris Knadle wrote:
Hello, Michael.
I'm emailing again because I've tried again to follow the suggestions
that were made for this bug, and it is not working.
On 11/22/24 06:09, Michael Biebl wrote:
> Again, I don't understand why you try to fiddle with debia
Am 08.01.25 um 19:44 schrieb Chris Knadle:
Hello, Michael.
I'm emailing again because I've tried again to follow the suggestions
that were made for this bug, and it is not working.
On 11/22/24 06:09, Michael Biebl wrote:
Again, I don't understand why you try to fiddle with debian/rules and
v
Hello, Michael.
I'm emailing again because I've tried again to follow the suggestions
that were made for this bug, and it is not working.
On 11/22/24 06:09, Michael Biebl wrote:
Again, I don't understand why you try to fiddle with debian/rules and
variables in .install files (don't do that)
Again, I don't understand why you try to fiddle with debian/rules and
variables in .install files (don't do that)
You install systemd-dev (including systemd.pc), the build system picks
up the paths from systemd.pc via pkgconf and installs the files into the
correct paths. All you need to do in
Hello Chris, Michael, Stefan.
I don't understand how to do what has been requested. I've tried a
number of variations of including systemd-dev as a dependency and using
variables to reference the system sysusers directory, and this is not
working out for me. I've spent more time on this than I
Am 20.11.24 um 08:54 schrieb Chris Hofstaedtler:
Hi Chris,
On Tue, Nov 19, 2024 at 11:58:15PM -0500, Chris Knadle wrote:
I think I finally figured out what referencing systemd.pc is about. There's
no systemd-dev package, it looks like system.pc is in the "systemd" package.
As Michael pointed
Hi Chris,
On Tue, Nov 19, 2024 at 11:58:15PM -0500, Chris Knadle wrote:
> I think I finally figured out what referencing systemd.pc is about. There's
> no systemd-dev package, it looks like system.pc is in the "systemd" package.
As Michael pointed out, systemd.pc is in the "systemd-dev" package.
Hello Michael and Stefan.
I think I finally figured out what referencing systemd.pc is about.
There's no systemd-dev package, it looks like system.pc is in the
"systemd" package. The file can be seen here:
https://github.com/systemd/systemd/blob/main/src/core/systemd.pc.in
and it looks like
Hi,
the best way I'd say to fix this is via a build-depends on systemd-dev
to get the correct path for the sysusers directory from systemd.pc.
/etc/sysconfig.d is a weird fallback path (which honestly doesn't make a
lot of sense) in case systemd.pc is not found.
from auxiliary_files/CMakeLi
Greetings.
As far as I know /etc/sysconfig.d/ is a directory used by Fedora/Red Hat
based distros, not Debian.
Looking through the Git log I see I added this on Feb 1 2023 with the
following commit message:
add etc/sysconfid./mumble-server.conf as the build breaks without
it at compat
Package: mumble-server
Severity: normal
Hi,
mumble-server installs a systemd-sysusers file to /etc/sysconfig.d
According to the sysusers.d(5) man page sysusers files can be placed in
/etc/sysusers.d/*.conf
/run/sysusers.d/*.conf
/usr/lib/sysusers.d/*.conf
So installing the sysusers file to /etc
20 matches
Mail list logo
