- This topic has 11 replies, 6 voices, and was last updated Oct 26-11:46 am by BobC.
-
Posts
-
RobK88
I would like to upgrade to antiX 19.
I understand that the best way to upgrade is via a fresh install.
But how can i easily reinstall all the additional software packages that are currently installed on my existing antiX system?
I am sure that I even do not remember all the names of the additional software packages that I have installed. (Many of which are command line programs).Is there a way I cam get a list of the additional software packages that I have installed on my existing antix system? (Then after the fresh install on AntiX 19, I can install them via apt-get).
Or is it best that I just change to repos to Buster and do a “sudo apt-get dist-upgrade”?
Your thoughts please!
Anonymous
just change to repos to Buster and do a “sudo apt-get dist-upgrade”?
No.
get a list of the additional packages I have installed
From a terminal commandline, type:
touch ~/manualpkgs.sh && chmod +x ~/manualpkgs.sh && leafpad ~/manualpkgs.shthe paste the following content into the freshly-created file, and Save.
Then at terminal commandline, launch the script via:
$ ~/manualpkgs.sh
(don’t type the dollarsign; it’s just shown here to represent the commandline prompt)#!/bin/sh ############################# # # Toward facilitating migration, this script outputs a list of packagenames # which have been manually added to the currently-running system "since Day1" # ############################# ### generate a textfile containing a list of all ### currently installed packagenames which are denoted as manual: apt-mark showmanual | sort -u > /tmp/zall_manual ### parse installed-packages.txt and generate a textfile containing ### a packagename-only list: cat /usr/share/antiX/installed-packages.txt|awk -F ' ' '{print $1}' \ |sort -u|sed -e "s/[\: ].*$//g" >/tmp/zall_preinstalled ### generate the "marked as manually-installed since Day1" list by ignoring any ### packagenames which were present within the pre-installed packages list: comm -13 /tmp/zall_preinstalled /tmp/zall_manual > /tmp/zmanual_since_day1 ### optional cleanup (user may want to preserve and inspect these interim lists) rm /tmp/zall_manual && /tmp/zall_preinstalled ### optional ~~ launch a gui text editor to display the list leafpad /tmp/zmanual_since_day1&caveats:
1)
The list will undoubtedly contain various lib* packagenames; few, if any, of these are items that you’ve manually (explicitly) installed. They are included in the list for the sake of completeness ~~ in case you maybe _did_ explicitly install some of ’em (e.g. to support optional features of a multimedia player, b/c “lib_blahblah” was only Recommended by the multimedia player’s pkg, not listed as Depends)2)
Some of the listed packages may no longer be available on a new system configured to use “Debian stable (Buster)” repository ~~ Debian10 dropped (“deprecated”, kicked-to-the-curb) quite a few packages which depend on various Gtk2 component libraries.3)
Bear in mind that on the new system, upon installing the same-named package containing a newer version of a given program… you can expect that some programs will exhibit maddeningly different UI features (narrow scrollbars, no page-at-a-time scrolling, etc) due to Gtk3 theming.Many many thanks for your post and taking the time to write a script for me!
It is greatly appreciated!!I assume that before I do a clean install, I should copy /tmp/zmanual_since_day1 to my home directory.
Then after I do a clean install of antiX 19 (while preserving my home directory), I should apt-get install the packages listed in ~/zmanual_since_day1Is there a way I can automate this?? like “agt-get install ~/zmanual_since_day1” ? Or maybe “cat ~/zmanual_since_day1 | apt-get install -” ??
P.S. Also many thanks for letting me know that many packages were deprecated in Buster / AntiX 19 especially if they depended on various Gtk2 component libraries.
I would have thought that the developers of Buster would have kept many of the grk2 libraries for the older packages to run.automated reinstallation (i haven’t tested, and would not recommend) ~~ that might require assessing dependencies
and rearranging the order of items in the list, to avoid winding up with “unmet dependencies” failure.you could use
sed -i ‘:a;N;$!ba;s/\n/ /g’ /tmp/zmanual_since_day1
to quickly replace newline characters with spaces so that the package names are all on one line within the file
toward pasting the looooooong list to commandline, ala
sudo apt install install pkg1 pkg2 … pkg19===============
edit:
yeah, automation is prone to failure. To illustrate, here’s a quick testcase:$ sudo apt install ncdu boguspackagename leafpad [sudo] password for demo: Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package boguspackagenameIf a given packagename within the list no longer exists… the entire operation will immediately fail
Again many thanks for all your help!
Given your comments and insights, I am now considering first running the Live CD/DVD of AntiX 19 and then seeing which of the software packages in my existing antiX 17 setup have been deprecated in antiX 19. If there are packages I cannot live without, then I might have to stick with antiX 17 for the time being.
Rob
manyroads
@RobK88 I can tell you what I do, that takes about 30 minutes and is guaranteed to work. If uses basically no automation. And it is definitely NOT cool.
1. I write down a list of apps that I want both to add & remove. (Look at the new distro see if there are new ones I don’t want); and on my old old distro to identify those that are not included on the the new distro (for addition)).
2. I use synaptic to get their correct names (write the names down. I use a pen and paper in a notebook for keeping/archiving. ;).
3. Then I write/type a command stream that looks like:sudo apt install app1 app2 app3,...appN
4. Next write a command stream to remove cruff like:sudo apt install app1 app2 app3,...appN
5. Save the command streams to a usb.
6. Install the new distro
7. Plug in the usb & mount.
7. Run the two command streams/ strings.
Done.I know there’s nothing technically excellent here. It is simple; it does work; I use it all meaning I use it about 20-40 times a year.
btw. Once I have my app lists… I actually just update the adds with those apps I want to continue using. (So I don’t need to do this whole thing every time.)
Note: you still have to move your data… that’s pretty easy with a usb drive, DropBox or similar. Mine takes time because the data files are over 500GB.
Perhaps this will help.
Pax vobiscum,
Mark Rabideau - http://many-roads.com
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken
dwm & i3wm ~Reg. Linux User #449130
20 Jan 2021 ~ "End of an Error"
anticapitalista
You could try Upgrading antiX-17 to antiX-19
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Many thanks for all the input! It is greatly appreciated.
I have decided to use the great script provided by skidoo to list all of the extra packages that I have manually installed since I first installed AntiX 17, do a fresh install of AntiX-19 and then reinstall all these extra packages (except those dropped in Buster / AntiX-19).
Just some quick questions. My existing Home directory is on a separate disk partition. Should I back it up and re-format it prior to the fresh install of antiX-19? Or should I just leave it alone during the fresh install of antiX-19?
anticapitalista
Definitely create a backup of home.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
oops
3. Then I write/type a command stream that looks like: sudo apt install app1 app2 app3,…appN
It is the way I usually did too, now I do exactly the same think but into a VirtulBox machine first (and adjust /etc/skell/*, the kernel, etc ) then create a antiX-19_snapshot.iso … then the hard installation on the PC (sometime by keeping my /home too and reusing the main user). There is many ways/roads to do that 😉
My new install of antiX19-x32 on my eepc:
neofetch
_,met$$$$$gg. user1-antix@antix1
,g$$$$$$$$$$$$$$$P. ———————–
,g$$P” “””Y$$.”. OS: Debian GNU/Linux 10 (buster) i686
,$$P’ `$$$. Host: MS-N033 Ver.001
‘,$$P ,ggs. `$$b: Kernel: 5.2.8-antix.1-686-smp-paed$$' ,$P"' . $$$ Uptime: 1 hour, 16 mins $$P d$' , $$P Packages: 1836 (dpkg) $$: $$. - ,d$$' Shell: bash 5.0.3 $$; Y$b._ _,d$P' Resolution: 1024x600 Y$$. <code>.</code>"Y$$$$P"' DE: icewm$$b “-.__ WM: IceWM 1.5.5+git20190610 (Linux/i686)
`Y$$ WM Theme: VistaBlack_antiX_TOF
`Y$$. Theme: Arc-EvoPro2 [GTK2/3]
`$$b. Icons: Faenza-Cupertino-mini [GTK2/3]
`Y$$b. Terminal: xfce4-terminal
`”Y$b._ Terminal Font: Liberation Mono 9
`””” CPU: Intel Atom N280 (2) @ 1.667GHz
GPU: Intel Mobile 945GM/GMS/GME, 943/940GML Express
Memory: 165MiB / 1936MiB- This reply was modified 3 years, 6 months ago by oops.
- This reply was modified 3 years, 6 months ago by oops.
oops
3. Then I write/type a command stream that looks like: sudo apt install app1 app2 app3,…appN
It is the way I usually did too, now I do exactly the same think but into a VirtulBox machine first (and adjust /etc/skell/*, the kernel, etc ) then create a antiX-19_snapshot.iso … then the hard installation on the PC (sometime by keeping my /home too and reusing the main user). There is many ways/roads to do that 😉
ex:Install antiX19 x32 into my eepc:
neofetch --off user1-antix@antix1 ----------------------- OS: Debian GNU/Linux 10 (buster) i686 Host: MS-N033 Ver.001 Kernel: 5.2.8-antix.1-686-smp-pae Uptime: 1 hour, 46 mins Packages: 1836 (dpkg) Shell: bash 5.0.3 Resolution: 1024x600 DE: icewm WM: IceWM 1.5.5+git20190610 (Linux/i686) WM Theme: VistaBlack_antiX_TOF Theme: Arc-EvoPro2 [GTK2/3] Icons: Faenza-Cupertino-mini [GTK2/3] Terminal: xfce4-terminal Terminal Font: Liberation Mono 9 CPU: Intel Atom N280 (2) @ 1.667GHz GPU: Intel Mobile 945GM/GMS/GME, 943/940GML Express Memory: 443MiB / 1936MiB- This reply was modified 3 years, 6 months ago by oops.
BobC
Ok, different people have different ways to do things.
For /home, my method is to
1. back up /home just in case.
2. clean up /home.
3. use aptik-gtk to save /home, users and groups
4. install new system
5. install all missing packages
6. use aptik-gtk to restore /home, users and groups
7. overlay changed things outside of /homeIf you search for a thread with packagecomp (and a zip file of it), zip file here it includes the scripts I used and instructions. I have used it for antiX 17 and 19, both 386 and x64, and should work for other Debian based distros. Skidoo, Dave and BitJam (possibly others too, my memory is faded) provided the ideas and/or code behind it back then. It has the same basis as skidoo’s script because if I recall, that was one of his ideas back then. I used it last weekend on this machine. It isn’t perfect. You have to review the list and decide things to not install. There is a readme file included.
My pkgs.add file format is pretty normal, one package per line, like below:
acpitail acpitool adobe-flash-properties-gtk adobe-flashplugin antix-snapshot-gui apt-file apt-xapian-index aptitude aptitude-common- This reply was modified 3 years, 6 months ago by BobC.
- This reply was modified 3 years, 6 months ago by BobC. Reason: added link
- You must be logged in to reply to this topic.
