- This topic has 9 replies, 3 voices, and was last updated Sep 14-1:30 am by stevesr0.
-
Posts
-
anticapitalista
If anyone wants to run antiX-19 base or full with sid/unstable (and probably testing as well) repos (there are already core and net sid isos available), make sure you do the following.
1,
sudo apt update && sudo apt dist-upgradebefore changing repos.
2. Only use antix and debian repos and only use sid/unstable – do not mix with buster, buster-backports, testing.
Then
sudo apt update3. Before dist-upgrading, make sure you purge fbsplash-antix otherwise the upgrade will fail.
This will also remove screenlight-antix and console-grid-guisudo apt purge fbsplash-antix4. You will need to manually upgrade sshfs. This will replace fuse with fuse3
sudo apt install sshfs5.
sudo apt dist-upgradeNote: Some python2 apps will be removed eg apt-notifier
6. Don’t forget to reinstall fbsplash-antix and the removed apps from step 3.
sudo apt install fbsplash-antix screenlight-antix console-grid-gui7. To remove multiple entries in menu under Desktop
sudo apt install --reinstall desktop-session-antix8. Cleanup
sudo apt autoremove- This topic was modified 2 years, 7 months ago by anticapitalista.
- This topic was modified 2 years, 7 months ago by anticapitalista. Reason: Latest-safest version
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
xinomilo
@anticapitalista, i think the above works only for sysvinit version. if upgrading antix runit stable -> sid, there’s a conflict with init package, that can’t complete dist-upgrade.. been a couple of weeks since i last tested that, but that was my experience with previous runit version too..
probably due to this : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924132anticapitalista
Actually my test was with runit version – did you do step 3 before a dist-upgrade?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
xinomilo
ok, reinstalled 19.2 runit antix buster, now dist-upgrading to sid… currently in step 4 :
The following packages have been kept back:
init sshfsthat’s what i remember.. manually trying to install init :
# apt install init
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following package was automatically installed and is no longer required:
getty-run
Use ‘apt autoremove’ to remove it.
…
The following packages will be REMOVED:
runit-init
….# apt policy init
init:
Installed: 1.56+nmu1
Candidate: 1.57
Version table:
1.57 500
500 http://ftp.xx.debian.org/debian unstable/main amd64 Packages
*** 1.56+nmu1 100
100 /var/lib/dpkg/statusso, maybe a note about init package not dist-upgrading in instructions above..
anticapitalista
I didn’t get that message.
init updated to 1.57Let me try again.
- This reply was modified 2 years, 7 months ago by anticapitalista.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
anticapitalista
ok, reinstalled 19.2 runit antix buster, now dist-upgrading to sid… currently in step 4 :
The following packages have been kept back:
init sshfsthat’s what i remember.. manually trying to install init :
# apt install init
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following package was automatically installed and is no longer required:
getty-run
Use ‘apt autoremove’ to remove it.
…
The following packages will be REMOVED:
runit-init
….# apt policy init
init:
Installed: 1.56+nmu1
Candidate: 1.57
Version table:
1.57 500
500 http://ftp.xx.debian.org/debian unstable/main amd64 Packages
*** 1.56+nmu1 100
100 /var/lib/dpkg/statusso, maybe a note about init package not dist-upgrading in instructions above..
Ok – you are right – I have sent a bugfix deb of init and init-system-helpers to antiX sid nosystemd and testing nosystemd repos
Thanks.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
xinomilo
thanks for the quick response… 🙂
i still don’t see a new init version in a couple of mirrors i tried, so i guess i’ll wait a bit longer to try it out..
a couple of other notes from dist-upgrade :
—
about fbsplash. even if doing step 3 before dist-upgrade, i still get :dpkg: error processing archive /var/cache/apt/archives/initscripts_2.96-3_all.deb (–unpack):
trying to overwrite ‘/etc/rc.local’, which is also in package fbsplash-antix 0.3.2so i chose to remove fbsplash-antix, dist-upgrade, then reinstall.. that worked ok, but maybe there’s another way to workaround(?)
—
another thing, dist-upgrade tries to change some files in /etc, that contain previous antix adjustments since installation (not personal) :
/etc/apt/sources.list.d/antix.list (package: apt-antix)
/etc/sysctl.conf (package: procps)
could just be normal behavior, just sayin’..
—have to say once again, thanks for all your work in antix 🙂
anticapitalista
I made a few amendments to the original post.
Bugfix debs of init and init-system-helpers should now be in the repos.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
xinomilo
so i tried this all over again, and these instructions work smoothly.. thx 🙂
stevesr0
Hi anticapitalista,
Delayed question about this posting. Since I am unaware of a “prepackaged” elogind free iso for antiX-21, I tried to upgrade the special 19.5 antiX elogind-free version to Sid in order to try your elogind free version of Pipewire.
However, I didn’t follow the steps here and I got the same error messages that dirkd posted about when he tried to (IIRC) tried to upgrade from 19 to testing.
Since you had advised him to start with antiX-21, I wonder whether at this time, this approach might still work in upgrading or would it be better to go first to 21, then to Sid?
Thanks for advice.
stevesr0
- You must be logged in to reply to this topic.
