Unable to run eopkg up

polomi

I'm running Solus Budgie. I last updated last weekend and it worked fine. But today, when I run sudo eopkg up, I get the following error:

Updating repositories
Updating repository: Solus
eopkg-index.xml.xz.sha1sum     (40.0  B)100%      2.25 MB/s [00:00:00] [complete]
Solus repository information is up-to-date.
System error. Program terminated.
[Errno 2] No such file or directory: '/var/lib/eopkg/package/libiptcdata-1.0.4-1/metadata.xml'
Please use 'eopkg help' for general help.
Use --debug to see a traceback.

Indeed, there is no such file on my system. Here is the result with --debug:

I tried to search around but didn't find any mention of this specific file.

Girtablulu

sudo eopkg rdb

polomi

Girtablulu It ran fine until

Adding 'libiptcdata' to db... No handlers could be found for logger "pisi"
Program terminated.
Unable to read file (/var/lib/eopkg/package/libiptcdata-1.0.4-1/files.xml): [Errno 2] No such file or directory: '/var/lib/eopkg/package/libiptcdata-1.0.4-1/files.xml'
Please use 'eopkg help' for general help.

algent

polomi Do you use timeshift?
Try sudo mkdir /var/lib/eopkg/package/libiptcdata-1.0.4-1
Then:
sudo touch /var/lib/eopkg/package/libiptcdata-1.0.4-1/metadata.xml
Then reinstall
sudo eopkg it --reinstall libiptcdata

polomi

algent No, in fact I don't know what that is.

Maybe this could be helpful. Here are the last operations from eopkg hs:

polomi

algent RE to your edit: this worked. Thank you!

The issue is solved.

algent

polomi yw. I replied from my phone, and this thing isn't practical.
I use timeshift (A system restore utility that I have compiled it from source) and had this issue when I restored once my system last year and solved the issue by creating manually the missing file. And of course it is an empty file but reinstalling the package will install the correct file.

Girtablulu

algent the reinstall command would have been the correct answer not the manuall creating of stuff...

algent

Girtablulu I don't remember well, but I think the reinstalling it wasn't working in my case.
But now we can't prove this because we didn't suggest at first place the reinstall option.

algent

Yes, I wasn't wrong. I just restored the system from a snapshot 2021-01-19.
The problem here it is the same but with another package.
By running similar commands by creating manually the missing file the issue is fixed.

and the update too is running fine.