From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: borgbackup 1.2.0 is not working
Date: Sat, 18 Jun 2022 18:18:33 +0200 [thread overview]
Message-ID: <60c0a19c-515e-a0b2-3025-8a866880dbe8@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]
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.
next reply other threads:[~2022-06-18 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 16:18 Adolf Belka [this message]
2022-06-23 15:43 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60c0a19c-515e-a0b2-3025-8a866880dbe8@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox