The officially official Devuan Forum!

dzhigit

Member

Registered: 2020-11-07

Posts: 14  

gnome compile issue

I am trying to compile gnome-settings-daemon with this patch to fix brightness control issue, but it gives this error

../meson.build:96:0: ERROR: Dependency "gnome-desktop-3.0" not found, tried pkgconfig

so I tried

$ LANG=C apt-get install libgnome-desktop-3-dev -s
NOTE: This is only a simulation!
      apt-get needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libelogind0 : Conflicts: libsystemd0
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

How can I change dependency on libsystemd-dev and libudev-dev to libelogind-dev and libeudev-dev?

Head_on_a_Stick

Member

From: London

Registered: 2019-03-24

Posts: 3,125  

Website

Re: gnome compile issue

Why not just grab the source package instead and apply the patch to that?

Add the relevant deb-src lines to /etc/apt/sources.list then use

# apt update
apt source gnome-settings-daemon
cd gnome-settings-daemon-*
patch -p1 < brightness.patch
dpkg-source --commit
# mk-build-deps --install --remove
debuild -us -uc
# dpkg -i ../gnome-settings-daemon*.deb
# aptitude purge gnome-settings-daemon-build-deps

The dpkg-source & mk-build-deps commands are supplied by the dpkg-dev & devscripts packages.

How can I change dependency on libsystemd-dev and libudev-dev to libelogind-dev and libeudev-dev?

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

Can we see

apt policy libgnome-desktop-3-dev

---

Brianna Ghey — Rest In Power

dzhigit

Member

Registered: 2020-11-07

Posts: 14  

Re: gnome compile issue

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.

Last edited by dzhigit (2020-12-08 17:20:38)

Head_on_a_Stick

Member

From: London

Registered: 2019-03-24

Posts: 3,125  

Website

Re: gnome compile issue

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.

Last edited by Head_on_a_Stick (2020-12-08 17:27:33)

---

Brianna Ghey — Rest In Power

dzhigit

Member

Registered: 2020-11-07

Posts: 14  

Re: gnome compile issue

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?

Head_on_a_Stick

Member

From: London

Registered: 2019-03-24

Posts: 3,125  

Website

Re: gnome compile issue

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?

---

Brianna Ghey — Rest In Power

dzhigit

Member

Registered: 2020-11-07

Posts: 14  

Re: gnome compile issue

I have QEMU machine. Will that work?

Head_on_a_Stick

Member

From: London

Registered: 2019-03-24

Posts: 3,125  

Website

Re: gnome compile issue

Yes but a chroot is easier and quicker:

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

---

Brianna Ghey — Rest In Power

dzhigit

Member

Registered: 2020-11-07

Posts: 14  

Re: gnome compile issue

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

anticapitalista

Member

Registered: 2018-06-10

Posts: 36  

Re: gnome compile issue

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

Seems like elogind needs to catch up.

Last edited by anticapitalista (2020-12-08 18:44:47)

dzhigit

Member

Registered: 2020-11-07

Posts: 14  

Re: gnome compile issue

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

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

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

dzhigit

Member

Registered: 2020-11-07

Posts: 14  

Re: gnome compile issue

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?

Last edited by dzhigit (2020-12-08 20:13:01)

aitor

Member

From: basque country

Registered: 2016-12-03

Posts: 230  

Website

Re: gnome compile issue

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.

Last edited by aitor (2020-12-08 20:58:14)

---

If you work systematically, things will come by itself (Lev D. Landau)

anticapitalista

Member

Registered: 2018-06-10

Posts: 36  

Re: gnome compile issue

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

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.

dzhigit

Member

Registered: 2020-11-07

Posts: 14  

Re: gnome compile issue

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.

dzhigit

Member

Registered: 2020-11-07

Posts: 14  

Re: gnome compile issue

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

golinux

Administrator

Registered: 2016-11-25

Posts: 3,317  

Re: gnome compile issue

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 . . .

---

Get answers - Help Devuan - Report a bug - Search packages