Fix system rollback with deprecated packages

algent

A lot of people have been in a situation that they need to revert the updates because something was broken in the last update.
But the reverting don't work if in the last update deprecated packages are involved. For example, in this test system there are two packages deprecated:

Operation #103: upgrade
Date: 2021-06-09 09:12
 
    * python3-sip 4.19.24-20-1-x86_64 is removed.
    * nautilus-admin 1.1.9-3-1-x86_64 is removed.

To rollback the update i run:
sudo eopkg hs -t 102

The download process went fine until:

Downloading 14 / 24
System error. Program terminated.
Repo item python3-sip not found

This issue can be fixed by using a Local repository.
Create a folder where you want and name it for example Local:

mkdir Local
cd Local

Then download here the two missing packages python3-sip-4.19.24-20-1-x86_64.eopkg and nautilus-admin-1.1.9-3-1-x86_64.eopkg.
You will find them on https://packages.getsol.us/ in shannon repository, or download them using terminal:

wget https://packages.getsol.us/shannon/p/python-sip/python3-sip-4.19.24-20-1-x86_64.eopkg
wget https://packages.getsol.us/shannon/n/nautilus-admin/nautilus-admin-1.1.9-3-1-x86_64.eopkg

Copy these files in ~/Local and then generate the Local eopkg index , simply by running:
eopkg index --skip-signing ~/Local

You can see now the content of this Local Repository:

$ ls -l
total 256
-rw-rw-r-- 1 algent algent  10078 Jun  9 09:43 eopkg-index.xml
-rw-rw-r-- 1 algent algent     40 Jun  9 09:43 eopkg-index.xml.sha1sum
-rw-rw-r-- 1 algent algent   2752 Jun  9 09:43 eopkg-index.xml.xz
-rw-rw-r-- 1 algent algent     40 Jun  9 09:43 eopkg-index.xml.xz.sha1sum
-rw-rw-r-- 1 algent algent   6137 Sep  7  2019 nautilus-admin-1.1.9-3-1-x86_64.eopkg
-rw-rw-r-- 1 algent algent 226290 Oct 24  2020 python3-sip-4.19.24-20-1-x86_64.eopkg

Add this new repository in the system: (I used name Local, but you can use what ever you want, just don't use Solus).
sudo eopkg ar Local ~/Local/eopkg-index.xml.xz

Verify the repositories in your system:

$ eopkg lr
Solus [active]
   https://mirrors.rit.edu/solus/packages/shannon/eopkg-index.xml.xz
Local [active]
   /home/algent/Local/eopkg-index.xml.xz

Run sudo eopkg up to include the new repo in the updates.

Now you can successfully rollback. (Note -t 102 is for my test system)
sudo eopkg hs -t 102

Then reboot.

After finishing, you can disable "Local" repo or remove it.
sudo eopkg dr Local to disable
sudo eopkg rr Local to remove

brent

Downloading 14 / 24
System error. Program terminated.
Repo item python3-sip not found

this looks depressingly familiar...so great fix.
But, at the end, does disabling the Local media effect the deprecated, installed, eopkgs?

algent

brent But, at the end, does disabling the Local media effect the deprecated, installed, eopkgs?

They will be uninstalled automatically again next update.
This trick is to succeed the system rollback, not to save deprecated packages. There are reasons why they are deprecated.
For example old python3-sip will conflict with current python-sip, but not with the old python-sip.
That is why it should be deprecated.

brent

algent I gotcha, thank you. I forgot these will get torpedoed after the first giant update after roll back.

MichelDwo

Thanks a lot @algent for the tip.

I know I'm reacting a bit more than 2 years later after you posted it, but when I try to perform the takeback , I get the following error :

System error. Program terminated.
unknown url type: /home/<username>/Local/<packagename>.eopkg

(I'm copying the error message, hence the 'username' and 'packagename' examples)

algent

MichelDwo
Can you list the repositories: eopkg lr

MichelDwo

I can, both are listed like in your example.

The Solus one displays the https link to the CDN.

The Local one displays the path : /home/<username>/Local/eopkg-index.xml.xz

I have also tried the following:
delete-cache
clean
rebuild-db
but the issue remains.

MichelDwo

Oh, but when I execute the takeback command with the —debug parameter, I get the following (could post it here thanks to my phone’s OCR):

Package python-pathlib2 found in repository Local
System error. Program terminated.
(type 'exceptions ValueError'>: unknown url type: /home/michel/reparepo/python-pathlib2-2.3.6-3-1-x86_64 .eopkg
Please use
"eopkg help' for general help.
Traceback:
File
"usr bin/eopkg", line 78, in <module> cli.run_command ()
File
"usr/lib/puthon2.?/site-packages/pisi/cli/pisicli.py", line 138, in run_command self.command. run ()
File "us/lib/python2.7/site-packages/pisi/cli/history.py",line 123, in run
self. takeback (opno)
File "/usr/lib/puthon2.7/site-packages/pisi/cli/history.py", line 61, in takeback
pisi.api.takeback(operation)
File "/usr/lib/python2.7/site-packages/pisi/api.py",line65,inwrapper
ret = func(*
args, **.
kw)
File
"/usr/lib/python2.7/site-packages/pisi/api.py",line462,in takeback pisi.operations .history.takeback(operation)
File
"usr/lib/python2.7/site-packages/pisi/operations/history.py", line 188, in takeback if fetch_remote_file(pkg, errors:
File
"usr/lib/python.?/site-packages/pisi/operations/history.py*,line 115, in fetch_remote_file pisi. fetcher. fetch_ur1(uri, dest, ctx.ui.Progress)
File
"/usr/lib/python2.?/site-packages/pisi/fetcher.py, line 263, in fetch url fetch. fetch()
File
"/usr/lib/python2.?/site-packages/pisi/fetcher.py",line 155, in fetch with contextlib.closing(ur11ib2.urlopen(self.url.get_uri(),timeout = 15)) as fp:
File
"usr/lib/python2.?/ur11ib2.py", line 154, in urlopen return opener. open (url, data, timeout)
File
"usr/lib/python2.7/ur11ib2.py", line 421, in open
protocol = req.get_type ()
File "usr/lib/python2.?/urllib2.py", line 283, in get_type raise ValueError,
"unknown url type: %" % self. __original

algent

MichelDwo What is the reason you want to rollback the update?

MichelDwo

algent

login screen did not load, so I consider it’s a display driver issue.
I wanted to rollback in order to narrow down to the faulty package.

I’ll continue to investigate when I’m in front of the faulty machine again (not before 2weeks)
Thanks for your time @algent 🙂

ReillyBrogan

MichelDwo Are you able to get to a TTY at least?

MichelDwo

ReillyBrogan

yes, this is how I was able to test the solution provided by @algent in this thread/topic.

WetGeek

ReillyBrogan Are you able to get to a TTY at least?

Speaking of a TTY, I've always wondered if someone were to happen to have an actual (antique?) teletype machine, would they be able to connect it to a Linux distro and actually use it to connect with a TTY input?

I did a little research, and it turns out you can! Who woulda thought.

brent

WetGeek I didn't see the linux connection digital part--it looked like it was going from analog to a vac tube Commodore but I consider that vactube commodore like thing analog for some reason...
...but great piece of history in the article. it looked like the ancestor to fax but that was never discussed.
Hunter S. Thompson used to refer to it as the "mojo wire"--a way to get his story in the field to his editor right away.
I knew third shift production guy who worked for a big current news magazine recall around midnight when that teletype started chattering like a madman and spitting out feed from all the overseas/late domestic stories being filed..then off to the races from the editors to the pressroom and all the labor involved in-between my god it was a glorious trade. I used to be in it/edit: but way after that contraption.

MichelDwo

I cannot explain how/why but when I switched on my computer after my holiday, it worked again.
Let's assume it's a code 45 error and I was the error there.

Thanks a lot for your time and again for this very useful thread 🙏 .

brent

MichelDwo
go to sleep with things fubar'd. wake up with things fixed.
so many times...Cant' figure it out...some claim its Celtic Magic🙂