Updating Testrepo Installed software using cli
Updating Testrepo Installed software using cli
I am hunting for the correct cli to use in updating all my upgradeable installed test software (from mxpi testrepo). I can do it with lots of little check marks (ticks for non-US folks) in mxpi, but that's pretty painful. :lipsrsealed:
I have hunted around for the terminal command... without success. Thanks in advance!
I have hunted around for the terminal command... without success. Thanks in advance!
Pax vobiscum,
Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
Re: Updating Testrepo Installed software using cli
Have a look heremanyroads wrote: ↑Fri Feb 08, 2019 5:25 pm I am hunting for the correct cli to use in updating all my upgradeable installed test software (from mxpi testrepo). I can do it with lots of little check marks (ticks for non-US folks) in mxpi, but that's pretty painful. :lipsrsealed:
I have hunted around for the terminal command... without success. Thanks in advance!
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
Re: Updating Testrepo Installed software using cli
Vielen dank @fehlix!!!
Pax vobiscum,
Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
Re: Updating Testrepo Installed software using cli
[redacted]
(fehlix' post, below, cleared my confusion)
(fehlix' post, below, cleared my confusion)
Last edited by skidoo on Thu May 30, 2019 4:16 pm, edited 1 time in total.
Re: Updating Testrepo Installed software using cli
Yes, it is possible. If there's an update to the app in MX test.
Also, newer versions of installed apps could be seen as an upgrade to a normally installed app.
That's why the recommendation is to not leave MX Test repo active.
As manyroads mentioned updating from the mx test is fastidious. Actually, the normal pattern is that apps are moved to the main MX repo for normal upgrading, but it is for testing, so if MX test is active, you are beta testing.
Also, newer versions of installed apps could be seen as an upgrade to a normally installed app.
That's why the recommendation is to not leave MX Test repo active.
As manyroads mentioned updating from the mx test is fastidious. Actually, the normal pattern is that apps are moved to the main MX repo for normal upgrading, but it is for testing, so if MX test is active, you are beta testing.
Last edited by Richard on Fri Feb 08, 2019 7:10 pm, edited 2 times in total.
Thinkpad T430 & Dell Latitude E7450, both with MX-21.3.1
kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.
kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.
Re: Updating Testrepo Installed software using cli
Thanks for the clarification Richard! I do understand the procedure better now.
Re: Updating Testrepo Installed software using cli
Hi kids (btw. I include me in that mix)!
I just posted this in another thread... it seems to work pretty well
viewtopic.php?f=94&t=48299&start=30#p484767
I just posted this in another thread... it seems to work pretty well
viewtopic.php?f=94&t=48299&start=30#p484767
Pax vobiscum,
Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
Mark Rabideau - ManyRoads Genealogy -or- eirenicon llc. (geeky stuff)
i3wm, bspwm, hlwm, dwm, spectrwm ~ Linux #449130
"For every complex problem there is an answer that is clear, simple, and wrong." -- H. L. Mencken
Re: Updating Testrepo Installed software using cli
Cool.
Another script to play with.
What do you use from mx test that doesn't get moved to the main mx repo?
Another script to play with.
What do you use from mx test that doesn't get moved to the main mx repo?
Last edited by Richard on Fri Feb 08, 2019 7:37 pm, edited 1 time in total.
Thinkpad T430 & Dell Latitude E7450, both with MX-21.3.1
kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.
kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.
Re: Updating Testrepo Installed software using cli
If you would manually enable mx testrepo within mx.list, you would see exactly the same after apt update.skidoo wrote: ↑Fri Feb 08, 2019 6:21 pm fehlix, this screenshot depicts a post in the linked topic. I was (still am) alarmed at noting the "126 upgradable" .. "ok done" result.
Suppose that I have, via past packageinstaller usage, chosen to install 2 apps from "mx testing" repo.
When running this script, I probably would not wish to have ALL my currently installed packages upgraded to testing versions.
The only difference with running my script "apttestrepo" is: 1. you cannot forget to disable the testrepo again, a it is only overlay-enabled on the fly. 2nd you only need run apttestrepo update, to update "only" the testrepp package list, if you already had run "apt update" before. and 3rd you don't need re-update apt again after using apttestrepo , as the overlay-enabled will be ignored by running only apt.
BTW: Did you know that I hate posting text-output from the CLI as images,
EDIT: just use as you would use "apt", e.g. for upgrade one package:
Example:
Check first: apttestrepo --simulate install xfce4-whiskermenu-plugin
Code: Select all
sudo apttestrepo --simulate install xfce4-whiskermenu-plugin
## /etc/apt/sources.list.d/mx.list
## mx-testrepo
deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/testrepo/ stretch test
sudo apt -o Dir::Etc::sourcelist=/tmp/mx-testrepo-apt-sources.list.d-temp.fehlix.23620.193933841/temp_source.list --simulate install xfce4-whiskermenu-plugin
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libva-wayland1 nvidia-egl-wayland-common
Use 'sudo apt autoremove' to remove them.
The following packages will be upgraded:
xfce4-whiskermenu-plugin
1 upgraded, 0 newly installed, 0 to remove and 153 not upgraded.
Inst xfce4-whiskermenu-plugin [2.1.5-0mx17] (2.3.1-0.1~mx17+1 MX repository:17.0/mx [amd64])
Conf xfce4-whiskermenu-plugin (2.3.1-0.1~mx17+1 MX repository:17.0/mx [amd64])
Code: Select all
sudo apttestrepo install xfce4-whiskermenu-plugin
apttestrepo list --upgradable | grep virtualbox
Check:
Code: Select all
LANG=en_US.UTF-8 apttestrepo --simulate install virtualbox virtualbox-dkms virtualbox-ext-pack virtualbox-guest-additions-iso virtualbox-qt
## /etc/apt/sources.list.d/mx.list
## mx-testrepo
deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/testrepo/ stretch test
sudo apt -o Dir::Etc::sourcelist=/tmp/mx-testrepo-apt-sources.list.d-temp.fehlix.24279.29243926/temp_source.list --simulate install virtualbox virtualbox-dkms virtualbox-ext-pack virtualbox-guest-additions-iso virtualbox-qt
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libva-wayland1 nvidia-egl-wayland-common
Use 'sudo apt autoremove' to remove them.
Suggested packages:
vde2
The following packages will be upgraded:
virtualbox virtualbox-dkms virtualbox-ext-pack virtualbox-guest-additions-iso virtualbox-qt
5 upgraded, 0 newly installed, 0 to remove and 149 not upgraded.
Inst virtualbox-ext-pack [5.2.24-1~mx17+1] (6.0.4-1~mx17+1 MX repository:17.0/mx [all]) []
Inst virtualbox [5.2.24-dfsg-4~mx17+1] (6.0.4-dfsg-1~mx17+1 MX repository:17.0/mx [amd64]) [virtualbox-qt:amd64 ]
Inst virtualbox-qt [5.2.24-dfsg-4~mx17+1] (6.0.4-dfsg-1~mx17+1 MX repository:17.0/mx [amd64])
Inst virtualbox-dkms [5.2.24-dfsg-4~mx17+1] (6.0.4-dfsg-1~mx17+1 MX repository:17.0/mx [all])
Inst virtualbox-guest-additions-iso [5.2.24-1~mx17+1] (6.0.4-1~mx17+1 MX repository:17.0/mx [all])
Conf virtualbox-ext-pack (6.0.4-1~mx17+1 MX repository:17.0/mx [all])
Conf virtualbox (6.0.4-dfsg-1~mx17+1 MX repository:17.0/mx [amd64])
Conf virtualbox-qt (6.0.4-dfsg-1~mx17+1 MX repository:17.0/mx [amd64])
Conf virtualbox-dkms (6.0.4-dfsg-1~mx17+1 MX repository:17.0/mx [all])
Conf virtualbox-guest-additions-iso (6.0.4-1~mx17+1 MX repository:17.0/mx [all])
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB