Skip to main content
Topic: dinit upgrade wonked (Read 8310 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

dinit upgrade wonked

Code: [Select]
world/bluez-dinit        20211026-3  20250815-1    0.00 MiB
system/dbus-dinit        20240610-2  20250815-3    0.00 MiB
system/dinit            0.19.4-1    0.19.4-6      0.00 MiB
system/dinit-base        0.19.4-1    0.19.4-6      0.00 MiB
system/dinit-rc          0.5.0-1      0.6.0-3        0.00 MiB
system/dinit-user-spawn              1.0.0-5        0.08 MiB
system/python            3.13.5-1    3.13.6-1      0.01 MiB
world/tomlplusplus                    3.4.0-1        0.85 MiB

Total Installed Size:  69.02 MiB
Net Upgrade Size:      0.95 MiB

:: Proceed with installation? [Y/n]
(8/8) checking keys in keyring                                                  [----------------------------------------------] 100%
(8/8) checking package integrity                                                [----------------------------------------------] 100%
(8/8) loading package files                                                    [----------------------------------------------] 100%
(8/8) checking for file conflicts                                              [----------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
dinit-rc: /etc/rc.local exists in filesystem (owned by artix-branding-base)
Errors occurred, no packages were upgraded.
-> error installing repo packages



i post b/c i don't want to break my system applying the fix i think should work
Cat Herders of Linux

Re: dinit upgrade wonked

Reply #1
I'm getting a dependency error which cannot be addressed unless the source packages are reconciled and re-released:
Code: [Select]
error: failed to commit transaction (conflicting files)
dinit-rc: /etc/rc.local exists in filesystem (owned by artix-branding-base)
Errors occurred, no packages were upgraded.

Re: dinit upgrade wonked

Reply #2
Plus this new dinit-user-spawn messes all up.

 

Re: dinit upgrade wonked

Reply #3
Dinit fucked, cannot start linux anymore.
Some error like
Code: [Select]
Couldn't load service loginready

Re: dinit upgrade wonked

Reply #4
Code: [Select]
world/bluez-dinit        20211026-3  20250815-1    0.00 MiB
system/dbus-dinit        20240610-2  20250815-3    0.00 MiB
system/dinit            0.19.4-1    0.19.4-6      0.00 MiB
system/dinit-base        0.19.4-1    0.19.4-6      0.00 MiB
system/dinit-rc          0.5.0-1      0.6.0-3        0.00 MiB
system/dinit-user-spawn              1.0.0-5        0.08 MiB
system/python            3.13.5-1    3.13.6-1      0.01 MiB
world/tomlplusplus                    3.4.0-1        0.85 MiB

Total Installed Size:  69.02 MiB
Net Upgrade Size:      0.95 MiB

:: Proceed with installation? [Y/n]
(8/8) checking keys in keyring                                                  [----------------------------------------------] 100%
(8/8) checking package integrity                                                [----------------------------------------------] 100%
(8/8) loading package files                                                    [----------------------------------------------] 100%
(8/8) checking for file conflicts                                              [----------------------------------------------] 100%
error: failed to commit transaction (conflicting files)
dinit-rc: /etc/rc.local exists in filesystem (owned by artix-branding-base)
Errors occurred, no packages were upgraded.
-> error installing repo packages



i post b/c i don't want to break my system applying the fix i think should work


Remove the branding package.
I added a default rc.local & rc.shutdown since they were in the backup array.

Re: dinit upgrade wonked

Reply #5
Plus this new dinit-user-spawn messes all up.


Nope it does not.
If you are one of the people who refuse dbus, this might be a problem on your end.
All user-spawn does is install the binary and the associated service enabled by hook.
No actual user services are started or enabled, that is user business, eg dbus .

Re: dinit upgrade wonked

Reply #6
I have no problems with dbus, elogind, etc. I'm not using login managers though.
As i said in another subject - it takes forever to load dinit-user-spawn service if using auto startx from .profile.
And what's the reasoning behind using it by default anyway?

Re: dinit upgrade wonked

Reply #7
I have no problems with dbus, elogind, etc. I'm not using login managers though.
As i said in another subject - it takes forever to load dinit-user-spawn service if using auto startx from .profile.
And what's the reasoning behind using it by default anyway?



Thats not the problem of a new dependency installed frankly.
Do you run a dbus  user service?

The only unknown is how turnstile and dinit-user-spawn behave together.
If in doubt, remove and disable turnstile.

I don't have to justify development decisions, but reasoning is that dinit-user-spawn fills a gap required for increasingly desktop related user services .
It is much better than turnstile, since low level  and it does precisely what it is supposed to do, limited scope well done.
Turnstile has a different scope, more aiming to replace logind, and it is experimental and not included in a default artix install.

Re: dinit upgrade wonked

Reply #8
Yes, I run dbus user service and don't use turnstile.

When I manualy startx from tty dinit-user-spawn works fine. It loads the service itself as well as user service instances (dbus, mpd, transmission). But it takes several minutes to load the service with startx from .bash_profile. That's the problem.
I've tested turnstile the same way - no problems.




Re: dinit upgrade wonked

Reply #9

I've tested turnstile the same way - no problems.


A possible problem I see, user-spawn isn't a direct replacement of turnstile.
Both coexisting might lead to unknown side effects, since turnstile does the user service thingy too.
I just wasn't gonna hard block turnstile.

Re: dinit upgrade wonked

Reply #10
Chiming in to say that I've also had problems following the dinit upgrade. First was on my desktop similar to OP where the upgrade would throw an error, I rm'd rc.local and I could continue with the upgrade.

Now on my laptop, after upgrading dinit, it wouldn't boot into the system because the rclocal service was missing all of a sudden. I also solved this by just manually creating the service:
Code: (/usr/lib/dinit.d/rclocal) [Select]
type = scripted
command = /usr/lib/dinit/rclocal
depends-on = local.target
Hopefully this helps others.

Re: dinit upgrade wonked

Reply #11
A possible problem I see, user-spawn isn't a direct replacement of turnstile.
Both coexisting might lead to unknown side effects, since turnstile does the user service thingy too.
I just wasn't gonna hard block turnstile.

I don't use turnstile at all, I've just tested these 2 utils separately from each other.

Re: dinit upgrade wonked

Reply #12
Chiming in to say that I've also had problems following the dinit upgrade. First was on my desktop similar to OP where the upgrade would throw an error, I rm'd rc.local and I could continue with the upgrade.

Now on my laptop, after upgrading dinit, it wouldn't boot into the system because the rclocal service was missing all of a sudden. I also solved this by just manually creating the service:
Code: (/usr/lib/dinit.d/rclocal) [Select]
type = scripted
command = /usr/lib/dinit/rclocal
depends-on = local.target
Hopefully this helps others.

This worked for me, thanks.

Re: dinit upgrade wonked

Reply #13
Is there going to be a release of a new set of packages that will include all the correct dependencies without requiring fiddling with files ?
I'm asking because I have not yet run the update - I need to be sure I will not break the system.
If it is not possible to fix all dependencies by pushing new packages, at least can we have a clear procedure (i.e. install X, remove Y, modify Z) ?

Thank you for your efforts !

Re: dinit upgrade wonked

Reply #14
Dinit fucked, cannot start linux anymore.
Some error like
Code: [Select]
Couldn't load service loginready

I had this recently, just find the service file that uses that line (waits-for = loginready) and either uncomment or remove and it should all work fine. For me it was the mullvad-daemon service file in /etc/dinit.d