You are not logged in.
This is an UNOFFICIAL method, that used to work. But not anymore.
EDIT 1: I also tried direct migrate from debian to devuan, that now also doesn't work because of similiar errors? Which is this:https://www.devuan.org/os/documentation/install-guides/chimaera/bullseye-to-chimaera
The point is, it's debian but on systemd related packages, it uses devuan repos instead. Rest is debian. But it doesn't work anymore. It says systemd is the init system bla bla, and can't remove it. No matter how you try. Is there a way to override this? Here was a topic I used: https://forum.pardus.org.tr/t/pardusu-nosystemd-hale-getirmek/20676
Don't mind the Turkish, you get the idea I hope. Pardus is another debian based system btw, %100 the same. I tried this with debian before also and it worked. But not anymore it doesn't. At 4. phase it uses live usb and we chroot inside it, and we try to remove systemd. But doesn't work.
Why I do this? Sometimes devuan repos go down for a long time. With this way we use devuan repos only for systemd related packages thus less usage.
Last edited by recklessswing (2022-10-30 23:02:53)
Offline
I'm not sure what your question is or even if there is one . . .
Online
Just use straight Devuan. Or if you need different Turkish language support, try antiX - it's also Debian without systemd and has a lot of international language support. Trying to take a systemd distro like Pardus and turn it into a non-systemd distro is just a huge amount of work for no particular reason, when Devuan and antiX have already done the hard work for you. Maybe you could start from Devuan or antiX, and add some Pardus packages and/or repos on top of it.
Offline
I'm not sure what your question is or even if there is one . . .
I think they're asking if it's possible to use both Debian and Devuan (unmerged)'s repos, with Devuan packages being at a higher priority. A possible usecase could be that the user is in a country where Debian has a faster and closer mirror than Devuan's, and want to use that as much as possible.
Former maintainer of the iwd package. See #639!
You can also find me on the Pale Moon forums. I develop XUL add-ons for Pale Moon.
My PGP public key
Offline
golinux wrote:I'm not sure what your question is or even if there is one . . .
I think they're asking if it's possible to use both Debian and Devuan (unmerged)'s repos, with Devuan packages being at a higher priority. A possible usecase could be that the user is in a country where Debian has a faster and closer mirror than Devuan's, and want to use that as much as possible.
Thanks jobbautista9!
@recklessswing . . . There are 2 scripts as well as manual instructions on how to migrate from Bullseye to Chimaera on our install page. Perhaps something in those methods will be useful to you.
Online
You could assign Debian repositories a pin value of 100 so they are treated as backports: only installed if specifically targetted but kept upgraded from there in future.
Something like
Package: *
Pin: origin "deb.debian.org"
Pin-Priority: 100
And install with
# apt install -t bullseye $package
Last edited by Head_on_a_Stick (2022-10-30 11:14:08)
Brianna Ghey — Rest In Power
Offline
There are the commands in the links I posted. It used to work but not anymore. Can't remove systemd. Thus it fails. Even though I try to remove it from a chroot.
Offline
I love a challenge but that's a step too far, even for me. Can we at least see the full error message? Or would that be considered cheating?
Last edited by Head_on_a_Stick (2022-10-30 19:58:06)
Brianna Ghey — Rest In Power
Offline
For example this was on chroot:
root@pardus:/# apt-get full-upgrade
...
Downloading packages etc.
....
....
Removing: systemd-sysv (247.3-7+deb11u1) ...
dpkg: systemd: some dependency problems blah blah
plymouth depends on this: systemd (>= 232-8~).
libpam-systemd:amd64 depends to this: systemd (= 247.3-7+deb11u1).
libnss-systemd:amd64 depends to this: systemd (= 247.3-7+deb11u1).
Removing: systemd (247.3-7+deb11u1) ...
systemd is the active init system, please switch to another before removing systemd.
dpkg: systemd paketi işlenirken sorun yaşandı (--remove):
systemd paketi pre-removal betiği kuruldu alt süreci 1 hatalı çıkış kodu ile sona erdi
#means systemd pre removal script is installed but sub process returned error code 1
dpkg: çok fazla hata oldu, işlem durduruluyor
#dpkg: too many errors, stopping the process
İşleme sırasında hatalarla karşılaşıldı:
systemd
Çok fazla hatayla karşılaşıldığı için işlem yarıda kesildi.
#Because of too many errors the process is halted.
E: Sub-process /usr/bin/dpkg returned an error code (1)
Last edited by recklessswing (2022-10-30 20:08:43)
Offline
You can nano /etc/apt/preferences.d/systemd
Package: systemd
Pin: release *
Pin-Priority: -1
Package: *systemd*
Pin: release *
Pin-Priority: -1
Package: systemd:i386
Pin: release *
Pin-Priority: -1
and than use as many compatible repos as you like. It should be ok. For example I have LMDE chimaera edition))
But if some package from another repo requires systemd as dependency than you are out of luck with this package.
Last edited by Devarch (2022-10-30 23:48:56)
Offline
You can nano /etc/apt/preferences.d/systemd
Package: systemd
Pin: release *
Pin-Priority: -1Package: *systemd*
Pin: release *
Pin-Priority: -1Package: systemd:i386
Pin: release *
Pin-Priority: -1and than use as many compatible repos as you like. It should be ok. For example I have LMDE chimaera edition))
But if some package from another repo requires systemd as dependency than you are out of luck with this package.
I tried similiar stuff but in the end they failed. Good try though.
Offline
I tried similiar stuff but in the end they failed. Good try though.
What do you mean when you say "similar"?
My chimaera is converted from debian with this exact not similar configuration. Systemd has been purged succesfully. I've also active LMDE repos with the same priority as devuan's repos, mx and sparky repos with lower priority.
Offline