Hello Adolf,

This looks like borgbackup is looking for the pip metadata:

https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=config/rootfiles/packages/...

The egg-info stuff from line 94.

If you add that to the package it might work.

-Michael

On 18 Jun 2022, at 17:18, Adolf Belka adolf.belka@ipfire.org wrote:

Hallo all,

In the forum it has been flagged up that borgbackup is not working in CU168.

I cloned a CU168 vm in my testbed system and installed borgbackup and ran borg -h and replicated the posters error. The following message occurred:-

borg -h Traceback (most recent call last): File "/usr/bin/borg", line 33, in <module> sys.exit(load_entry_point('borgbackup==1.2.0', 'console_scripts', 'borg')()) File "/usr/bin/borg", line 22, in importlib_load_entry_point for entry_point in distribution(dist_name).entry_points File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 919, in distribution return Distribution.from_name(distribution_name) File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 518, in from_name raise PackageNotFoundError(name) importlib.metadata.PackageNotFoundError: No package metadata was found for borgbackup

I have done searches about the error message and have not been able to find anything that helps.

The build for borgbackup-1.2.0 ran without any problems and there are no error messages in the logs for the build that I have been able to find.

Does anyone have a clue what is going on here.

At first I thought that the package importlib-metadata was missing for the execution but then I thought the message was more related to not being able to find metadata about borgbackup but I haven't been able to find any clues about that either in my searches.

Looking for any inspiration or good guesses otherwise I will raise it as an issue on the borgbackup git repository.

Regards,

Adolf.