Dev1 Galaxy Forum / gnome compile issue

Re: gnome compile issue

dummy@example.com (golinux) — Wed, 09 Dec 2020 15:41:26 +0000

dzhigit wrote:

It is getting harder and harder to like GNOME and not like systemd

Isn't lockin the whole point of GNOME/systemd? I could see that coming 6 years ago and abandoned ship . . .

Re: gnome compile issue

dummy@example.com (dzhigit) — Wed, 09 Dec 2020 14:30:52 +0000

anticapitalista wrote:

Sorry, I meant this problem you are having with;
libelogind0 : Conflicts: libsystemd0
not the brightness issue.

It worked after I used equivs to "install" libsystemd-dev, even though I gave it elogind's older version number. GNOME won't compile with elogind anyway, and when running the binary in Ceres/Sid several things are broken. It is getting harder and harder to like GNOME and not like systemd

Re: gnome compile issue

dummy@example.com (dzhigit) — Wed, 09 Dec 2020 14:21:19 +0000

Ok, so the reason is that elogind's header files are in /usr/include/elogind instead of /usr/include/systemd, meaning that anything that compiles against systemd needs to be modified, and even then it might not work. I don't know why I didn't think of it.

I think this is by design; applications are supposed to build
against the systemd headers and then, if they only use functions
also exposed by libelogind0 they can also run with that.

As Thorsten has already suggested, this is by design. Debian packages are only
built against libsystemd-dev. The libelogind0/libsystemd0 compatibility is a
*runtime* option, not compile-time. We don't even know (and can't test) if all
of the source packages depending on libsystemd-dev will compile against
libelogind-dev.

> Please add Provides: libsystemd-dev to control.
This would be both unwise and counter-productive. Having libelogind0 provide
libsystemd0 was a very controversial move and getting it accepted into Bullseye
a hard won victory. I am very reluctant to do anything that might jeopardise
that.

If you have an libelogind0 system and need to compile against libsystemd-dev,
please use one of the various build chroots or containers. This requirement is
already documented in libelogind0's README.Debian.

Re: gnome compile issue

dummy@example.com (anticapitalista) — Wed, 09 Dec 2020 13:32:19 +0000

dzhigit wrote:

https://bugs.debian.org/cgi-bin/bugrepo … bug=976868
anticapitalista wrote:
Connected to this? https://github.com/elogind/elogind/issues/170
Perhaps. I thought it was this: https://github.com/elogind/elogind/issues/158

Sorry, I meant this problem you are having with;

libelogind0 : Conflicts: libsystemd0

not the brightness issue.

Re: gnome compile issue

dummy@example.com (aitor) — Tue, 08 Dec 2020 20:57:00 +0000

dzhigit wrote:

also, this is unrelated but while chrooting into debian, I noticed package init now depends on systemd-sysv | sysvinit-core? where did runit-init go?

init, sysvinit and sysvinit-core will be removed from de system; however, sysvinit-utils and init-system-helpers will remain together with some new packages like runit, runit-init and getty-run.

Re: gnome compile issue

dummy@example.com (dzhigit) — Tue, 08 Dec 2020 20:12:20 +0000

also, this is unrelated but while chrooting into debian, I noticed package init now depends on systemd-sysv | sysvinit-core? where did runit-init go?

Re: gnome compile issue

dummy@example.com (dzhigit) — Tue, 08 Dec 2020 20:10:05 +0000

https://bugs.debian.org/cgi-bin/bugrepo … bug=976868

anticapitalista wrote:

Connected to this? https://github.com/elogind/elogind/issues/170

Perhaps. I thought it was this: https://github.com/elogind/elogind/issues/158

Re: gnome compile issue

dummy@example.com (anticapitalista) — Tue, 08 Dec 2020 18:42:53 +0000

Connected to this? https://github.com/elogind/elogind/issues/170

Seems like elogind needs to catch up.

Re: gnome compile issue

dummy@example.com (dzhigit) — Tue, 08 Dec 2020 18:06:59 +0000

Ok, I am reporting bug into libelogind-dev from chroot.

Re: gnome compile issue

dummy@example.com (Head_on_a_Stick) — Tue, 08 Dec 2020 17:52:19 +0000

Yes but a chroot is easier and quicker:

mkdir sid
# debootstrap sid sid/ https://deb.debian.org/debian
# chroot sid/

Re: gnome compile issue

dummy@example.com (dzhigit) — Tue, 08 Dec 2020 17:43:09 +0000

I have QEMU machine. Will that work?

Re: gnome compile issue

dummy@example.com (Head_on_a_Stick) — Tue, 08 Dec 2020 17:37:49 +0000

Well it would be for a Debian package and they prefer it if you use the reportbug package but some maintainers can be funny if bugs are reported in derivatives. Can you reproduce this in a Debian sid chroot?

Re: gnome compile issue

dummy@example.com (dzhigit) — Tue, 08 Dec 2020 17:32:57 +0000

Head_on_a_Stick wrote:

I've just unpacked the .deb in my Alpine Linux system and checked

ah, good idea. I also checked antiX and it has the same issue. I file bug report into Debian BTS?

Re: gnome compile issue

dummy@example.com (Head_on_a_Stick) — Tue, 08 Dec 2020 17:23:39 +0000

dzhigit wrote:

maybe libelogind-dev does not provide libsystemd-dev?

No, it does not. I've just unpacked the .deb in my Alpine Linux system and checked

Perhaps a bug report is called for then.

EDIT: until it's fixed use the equivs package to create "fake" dependencies.

Re: gnome compile issue

dummy@example.com (dzhigit) — Tue, 08 Dec 2020 17:19:41 +0000

Thank you for helping, the problem is now I left that laptop alone and when I came back I cannot get it to boot.

# apt update
apt source gnome-settings-daemon

Yes, this is what I am doing. (although I am using apt-get)

You shouldn't have to do that at all, the libelogind0 package has Provides: libsystemd0.

Hmm, maybe libelogind-dev does not provide libsystemd-dev? I am unable to check currently because this computer is using antiX. EDIT: or libeudev-dev does not provide libudev-dev?

Also, I forgot to mention, that was on Devuan Ceres. I believe brightness control is working in Beowulf.