Need help with EOPKG

kp2401075

Hello all,

I need help with eopkg.

 ⮞  sudo eopkg search libreoffice
System error. Program terminated.
Error -3 while decompressing data: invalid distance too far back
Please use 'eopkg help' for general help.
Use --debug to see a traceback.

I used --debug switch to get more info.

 ⮞  sudo eopkg search libreoffice --debug

DEBUG: PackageDB initialized in 0.0583667755127.
DEBUG: RepoDB initialized in 9.51290130615e-05.
System error. Program terminated.
<class 'zlib.error'>: Error -3 while decompressing data: invalid distance too far back
Please use 'eopkg help' for general help.

Traceback:
  File "/usr/bin/eopkg", line 82, in <module>
    cli.run_command()
  File "/usr/lib/python2.7/site-packages/pisi/cli/pisicli.py", line 142, in run_command
    self.command.run()
  File "/usr/lib/python2.7/site-packages/pisi/cli/search.py", line 90, in run
    pkgs = db.search_package(self.args, lang, repo, fields)
  File "/usr/lib/python2.7/site-packages/pisi/db/packagedb.py", line 158, in search_package
    for name, xml in self.pdb.get_items_iter(repo):
  File "/usr/lib/python2.7/site-packages/pisi/db/itembyrepo.py", line 85, in get_items_iter
    yield item, gzip.zlib.decompress(self.dbobj[r][item])

algent

kp2401075 ⮞ sudo eopkg search libreoffice

Also you don't need sudo to do the search or looking for info for any package.

CorvusRuber

Usual question: did you install something with sudo pip install ?
Because it looks like you've broken something in the system python toolchain, and since eopkg is written in python....

brent

Kepos you say in this last post that bothsudo eopkg up and eopkg sr xxx are returning timeout errors .
But the log you furnished shows no recognizable timeout error that I've ever seen in my experience.
I think CorvusRuber is right:
sudo eopkg check
or
sudo eopkg rdb
--something seems broken here

Kepos

Got the same warning and issue with sudo eopkg upgrade . It seems the routing to Solus repository takes too long.
After doing the same order twice or sometimes several times it finally is possible to finish the update.

jrsilvey

brent Kepos you say in this last post that bothsudo eopkg up and eopkg sr xxx are returning timeout errors .
But the log you furnished shows no recognizable timeout error that I've ever seen in my experience.
I think CorvusRuber is right:
sudo eopkg check
or
sudo eopkg rdb
--something seems broken here

I believe my friend @brent is right.

I would throw in the sudo usysconf run -f command as well after you follow the steps above. That command may or may not be needed in this instances but as far as I am concerned I always run it after running sudo eopkg check.

From the Boot Rescue page in the Solus Help Center..

Re-run System-Wide Configuration Triggers

In the chroot environment, run the following command which will perform various configuration triggers to update your icon cache, update GRUB and EFI configuration, re-compile settings, and more.

sudo usysconf run -f

After this, you should exit your chroot with exit then reboot your system. In the event you are still unable to access Solus, please contact us.

In this instance you wouldn't need to chroot into anything though.. this is the only place I know that there is some guidance about usysconf though.

Kepos

jrsilvey
I'm not sure, why I should use sudo usysconf run -f as I am not using any snap, just plain Solus repository so far.

algent

Kepos usysconf is not specific for snaps, but it is an universal system configuration.
From man usysconf:

DESCRIPTION
       usysconf is a system configuration agent designed for integration within the software update process. The main
       job for usysconf is to run OS configuration tasks within a well defined centralised location.

       usysconf will run a variety of triggers to ensure system consistency and health, detecting changes within  the
       filesystem  and  taking  any appropriate actions to configure components such as kernels or the dynamic linker
       cache.

kp2401075

It has been resolved by it self. today.

I did nothing other than install some packages today. after that search is working fine again.