eopkg always fails to update

ekurtz

hi all

recently came back to solus on an older laptop after a few months. every single time i update any package via sudo eopkg up I get the following when reaching the updating manpages step.

 [✓] Applying udev rules                                                success
Program terminated.
File conflicts:
/usr/bin/2to3 from python package
/usr/bin/idle from python package
/usr/bin/pydoc from python package
/usr/bin/python from python package
/usr/share/man/man1/python.1 from python package

running eopkg check or eopkg rdb as I've saw suggested on forums results in something like

Program terminated.
Unable to read file (/var/lib/eopkg/package/groff-1.22.4-5/files.xml): [Errno 2] No such file or directory: '/var/lib/eopkg/package/groff-1.22.4-5/files.xml'
Unable to read file (/var/lib/eopkg/package/groff-1.22.4-5/files.xml): [Errno 2] No such file or directory: '/var/lib/eopkg/package/groff-1.22.4-5/files.xml

I followed the steps suggested here https://discuss.getsol.us/d/7464-eopkg-help-no-such-file-or-directory-filesxml-metadataxml/4 to manually extract the files and to eventually repair broken packages. The last time I did this, there were about 20 to 30 packages that I manually had to wget and uneopkg.

i also tried

eopkg clean
eopkg delete-cache

and then
eopkg rdb
but that now fails with

Disabling keyboard interrupts for file operations.
Rebuilding the FilesDB...
Adding packages to FilesDB /var/lib/eopkg/info/files.db:
System error. Program terminated.
System error. Program terminated.
not enough values to unpack (expected 3, got 1)
not enough values to unpack (expected 3, got 1)

which seems like a generic python error, so i couldn't find anything specific to Solus here.

yesterday i eventually fully reinstalled solus and thought that solved it, but i have run into the same problems on a mostly fresh install.

does anyone have any ideas? any help is appreciated

edit: here are my system details

# System Details Report
---

## Report details
- **Date generated:**                              2025-11-11 17:56:08

## Hardware Information:
- **Hardware Model:**                              Lenovo ThinkPad T495
- **Memory:**                                      32.0 GiB
- **Processor:**                                   AMD Ryzen™ 7 PRO 3700U w/ Radeon™ Vega Mobile Gfx × 8
- **Graphics:**                                    AMD Radeon™ Vega 10 Graphics
- **Disk Capacity:**                               1.0 TB

## Software Information:
- **Firmware Version:**                            R12ET50W(1.20 )
- **OS Name:**                                     Solus 4.7 Endurance
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               49
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.16.12-323.current

alfisya

~~When was the last time you updated the PC?~~

Even on the fresh install? That seems weird.

Can you share eopkg history? Maybe pipe it to a file and put it on pastebin.

sudo eopkg history > ~/eopkg_history.txt

alfisya

A few tips on fresh install:

Always do sudo eopkg up first before installing anything from the repo
Better reboot after the first update
We just did an Epoch bump and usr-merge, so do sudo eopkg up again after rebooting.
Reboot again after the second update.
Now, it should be safe to install anything from the repo.

ekurtz

alfisya

thank you for your quick reply! unfortunately I'm not able to share eopkg history, as the laptop died and I can only access a terminal via crtl+alt+f3 after rebooting.

I will try to reinstall again and follow your steps once I get home later today.

I should also mention that I do dual boot with windows (necessary for special software). I've never had trouble with this in the past, but in the interest of full disclosure.

Thanks again

ekurtz

alfisya

This worked perfectly, thank you!

I realized that some of my issues may have been because my Live USB of solus was over a year old.

I also ran into the eopkg minor /lib32 error that some folks ran into in the weekly sync thread, but it sounds like that is no problem.
In the future, if I have issues, I will post in whichever weekly thread is most relevant.

Thanks again!

Harvey

The /lib32 thing isn't really a problem. I beleive its because /lib32 is a symlink to /usr/lib32 and most people don't have anything installed there so the link is pointing to something that does not exist and eopkg is pointing it out. Its fine.