apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

Debuser2018 · 2021-10-19 03:44:18

I used to run Debian testing with Sid with apt-pinning really long back. Recently, no experience with apt-pinning and I see some configuration files are need to be placed under directories. Example is apt.conf, /etc/apt/preferences.d/ .

So, what I want to achieve is Gnome-40 available in Testing installed in my Stable Chimaera. Any guidance. What I'm not sure is, if Daedalus is active with security updates etc available.

EDIT: Chose to upgrade to Daedalus (Testing) distro.

Last edited by Debuser2018 (2021-10-24 07:25:11)

steve_v · 2021-10-19 04:48:03

What a truly horrifying idea.

If you really want to break your system, nothing much has changed recently regards apt-pinning and /etc/apt/preferences still works.

Personally I use something like

Package: *
Pin: release n=<release codename>
Pin-Priority: 1

If I need something from another release.
But that something is going to be a small package with no major dependencies, and I'm going to watch apt like a hawk to make sure nothing else gets pulled in... because I like my system non-borked. I expect trying it with a behemoth like gnome would be a total disaster.

Head_on_a_Stick · 2021-10-19 04:52:29

A pin priority of 100 would ensure that the package is kept updated from unstable, just as if it was a backport.

steve_v wrote:

What a truly horrifying idea

+1

@OP, if you want bleeding edge software just use unstable.

Last edited by Head_on_a_Stick (2021-10-19 04:53:08)

hevidevi · 2021-10-19 11:55:37

I tried this a few months ago and failed miserably on a test partition.

thierrybo · 2021-10-19 20:53:25

Head_on_a_Stick wrote:

A pin priority of 100 would ensure that the package is kept updated from unstable, just as if it was a backport.
steve_v wrote:
What a truly horrifying idea
+1
@OP, if you want bleeding edge software just use unstable.

Agree, after two years using testing, I had less problems and feels more safe and stable than when I was using stable and pulling several packages from testing.

Head_on_a_Stick · 2021-10-20 05:10:07

thierrybo wrote:

testing

That's not covered by the security team and any upstream fixes may be subject to the mandatory transition delay from unstable.

I wrote:

if you want bleeding edge software just use unstable

^ This.

Last edited by Head_on_a_Stick (2021-10-20 05:10:27)

Debuser2018 · 2021-10-20 05:14:06

OK. Not choosing apt-pinning. I will switch to testing distribution.

But, How can I upgrade to testing (Daedalus)? Should I put only this line in /etc/apt/sources.list, after backing up Beowulf sources.list:
deb http://deb.devuan.org/merged daedalus main contrib non-free
OR
if this line also needed?
deb http://deb.devuan.org/merged daedalus-proposed-updates main contrib non-free

Last edited by Debuser2018 (2021-10-20 05:14:46)

Head_on_a_Stick · 2021-10-20 18:30:41

The proposed-updates repository is for people to test the changes for the next stable point release so it doesn't make sense for testing.

You should probably read https://www.debian.org/doc/manuals/debi … .html#s3.1 (official Debian documentation but it also applies to Devuan).

Debuser2018 · 2021-10-21 15:56:32

Upgraded to Daedulus. Browsers (Firefox, Chrome) not working. I can trace below messages from terminal:

:ERROR:browser_dm_token_storage_linux.cc(94)] Error: /etc/machine-id contains 0 characters (32 were expected).

and..
there is no /etc/machine-id file after the upgrade! BTW, I'm using openRC init on this system.

Last edited by Debuser2018 (2021-10-21 15:56:49)

Head_on_a_Stick · 2021-10-21 16:12:07

So I would check for any relevant man pages:

 $ apropos machine-id
machine-id (5)       - Local machine ID configuration file
systemd-machine-id-commit.service (8) - Commit a transient machine ID to disk
systemd-machine-id-setup (1) - Initialize the machine ID in /etc/machine-id
$

And then

man machine-id

To save you time:

machine-id(5) wrote:

When a machine is booted with systemd(1) the ID of the machine will be
established. If systemd.machine_id= or --machine-id= options (see first
section) are specified, this value will be used. Otherwise, the value
in /etc/machine-id will be used. If this file is empty or missing,
systemd will attempt to use the D-Bus machine ID from
/var/lib/dbus/machine-id

So perhaps try that?

# ln -sf /var/lib/dbus/machine-id /etc/machine-id

Or just make one up and hope the machine-id Police don't come knocking...

EDIT: this may be worth a bug report to Devuan, looks like no package supplies that file since systemd is supposed to generate it. I think it popped up recently in another thread IIRC.

Last edited by Head_on_a_Stick (2021-10-21 16:16:10)

Debuser2018 · 2021-10-21 16:30:35

Yes, /var/lib/dbus/machine-id exists. /etc/machine-id is missing. Symbolic link needs to be forced? I tried with ln -s and it did not seem to work.

Last edited by Debuser2018 (2021-10-21 16:31:00)

Debuser2018 · 2021-10-21 17:48:59

Browsers works fine in Gnome shell Xorg session. Problem occurs when using wayland session.

Head_on_a_Stick · 2021-10-21 18:24:32

Have you enabled Wayland support?

MOZ_ENABLE_WAYLAND=1 firefox

If that works then add the variable to /etc/environment (or in it's own file under /etc/environment.d/).

EDIT: are we having fun yet?

Last edited by Head_on_a_Stick (2021-10-21 18:25:01)

MiyoLinux · 2021-10-21 18:58:36

OMG...

I'm so glad that I'm using this old computer. Give me 2 CPUs and an incredible 4 GBs of RAM, and I'm happy.

Sorry to disrupt the thread...

Good luck to you.

Debuser2018 · 2021-10-22 05:58:46

Head_on_a_Stick wrote:

Have you enabled Wayland support?
MOZ_ENABLE_WAYLAND=1 firefox
If that works then add the variable to /etc/environment (or in it's own file under /etc/environment.d/).
EDIT: are we having fun yet?

Yes, Firefox worked with the above environment variable set. However, I have to add MOZ_ENABLE_WAYLAND=1 in /etc/environment file, not under /etc/environment.d/..

Google Chrome works with following lines, when invoked from terminal.:
/usr/bin/google-chrome-stable --enable-features=UseOzonePlatform --ozone-platform=wayland

However, there are many offending applications including synaptic which refuse to run even with xhost +si:localuser:root. Synaptic without root shows up with above option. Not synaptic-pkexec.

Head_on_a_Stick · 2021-10-22 15:30:42

Debuser2018 wrote:

there are many offending applications including synaptic which refuse to run even with xhost +si:localuser:root. Synaptic without root shows up with above option. Not synaptic-pkexec.

Yes, that's by design. Running graphical applications as root is now officially discouraged. You have been warned

This works for me for synaptic in GNOME's Wayland desktop and also under sway:

xhost +local:

EDIT: just remember to undo the damage afterwards:

xhost -local:

Last edited by Head_on_a_Stick (2021-10-22 15:31:10)

Debuser2018 · 2021-10-22 16:32:25

Synaptic is not working with above method. Synaptic as local user works; But neither synaptic-pkexec nor sudo /usr/sbin/synaptic works.

Debuser2018 · 2021-10-23 15:04:42

Many software seems to not work. Add Google-earth-pro to the list. I can see that the program is launched, but no GUI.

~$ ps aux |grep earth
devuan   9893  0.0  0.0   6768  3304 pts/0    S+   20:31   0:00 /bin/bash /usr/bin/google-earth-pro
devuan   9896  8.0  0.8 395600 71420 pts/0    Sl+  20:31   0:00 /opt/google/earth/pro/googleearth-bin

Same with synaptic-pkexec.

~$ ps aux |grep synaptic
devuan   9932  0.0  0.0   2432   672 pts/1    S+   20:32   0:00 /bin/sh /usr/bin/synaptic-pkexec
root      9933  2.2  1.4 472600 120112 pts/1   Sl+  20:32   0:01 /usr/sbin/synaptic

EDIT: Context: not working on wayland session. In Xorg this apps works.

Even xterm, too doesn't work in Wayland Gnome sessions:

:~$ ps aux |grep xterm
devuan  10712  0.1  0.1  24588 10312 pts/0    S+   12:57   0:00 xterm
devuan  10734  0.0  0.0   6192  2284 pts/2    S+   12:57   0:00 grep --color=auto xterm

Last edited by Debuser2018 (2021-10-24 07:34:36)

Debuser2018 · 2021-10-25 15:11:15

No solutions, that worked.

Head_on_a_Stick · 2021-10-25 15:35:38

So you have installed the xwayland package, right?

EDIT: use foot in Wayland, it's just as "light" as xterm and it doesn't need XWayland.

Last edited by Head_on_a_Stick (2021-10-25 15:38:17)

Debuser2018 · 2021-10-26 03:35:30

Head_on_a_Stick wrote:

So you have installed the xwayland package, right?
EDIT: use foot in Wayland, it's just as "light" as xterm and it doesn't need XWayland.

I think it's something else. Of course, Xwayland is installed. But, don't know how many apps will not be working. It is not alone 2-3 apps that are not working. I can provide any details needed. But, no way to figure out why Wayland is not working, when it is perfectly fine for a Ubuntu 21.10 with Gnome-40 in another system.

Last edited by Debuser2018 (2021-10-26 03:45:23)

The officially official Devuan Forum!

#1 2021-10-19 03:44:18

apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#2 2021-10-19 04:48:03

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#3 2021-10-19 04:52:29

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#4 2021-10-19 11:55:37

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#5 2021-10-19 20:53:25

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#6 2021-10-20 05:10:07

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#7 2021-10-20 05:14:06

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#8 2021-10-20 18:30:41

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#9 2021-10-21 15:56:32

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#10 2021-10-21 16:12:07

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#11 2021-10-21 16:30:35

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#12 2021-10-21 17:48:59

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#13 2021-10-21 18:24:32

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#14 2021-10-21 18:58:36

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#15 2021-10-22 05:58:46

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#16 2021-10-22 15:30:42

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#17 2021-10-22 16:32:25

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#18 2021-10-23 15:04:42

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#19 2021-10-25 15:11:15

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#20 2021-10-25 15:35:38

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

#21 2021-10-26 03:35:30

Re: apt-pinning for Gnome-40 packages from Daedalus with Chimaera?

Board footer