From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 6/7] borgbackup: Removed python3-pkgconfig as run time dependency
Date: Wed, 10 May 2023 15:04:21 +0200 [thread overview]
Message-ID: <20230510130422.2676356-6-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20230510130422.2676356-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
Tested-by: Adolf Belka <adolf.belka(a)ipfire.org>
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
lfs/borgbackup | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lfs/borgbackup b/lfs/borgbackup
index 0cbb809b7..79d6446ee 100644
--- a/lfs/borgbackup
+++ b/lfs/borgbackup
@@ -33,9 +33,9 @@ DL_FROM = $(URL_IPFIRE)
DIR_APP = $(DIR_SRC)/$(THISAPP)
TARGET = $(DIR_INFO)/$(THISAPP)
PROG = borgbackup
-PAK_VER = 14
+PAK_VER = 15
-DEPS = python3-pkgconfig python3-msgpack python3-packaging python3-pyfuse3
+DEPS = python3-msgpack python3-packaging python3-pyfuse3
# borgbackup only works with specific versions of python3-msgpack
SERVICES =
--
2.40.1
next prev parent reply other threads:[~2023-05-10 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 13:04 [PATCH 1/7] python3-trio: Fixes Bug#13076 - allows fuse mount to work again Adolf Belka
2023-05-10 13:04 ` [PATCH 2/7] python3-attr: Module no longer needed in the borgbackup dependency chain Adolf Belka
2023-05-10 13:04 ` [PATCH 3/7] python3-exceptiongroup: Fixes Bug#13076 - New run time dependency for borgbackup fuse mount Adolf Belka
2023-05-10 13:04 ` [PATCH 4/7] python3-flit_scm: Fixes Bug#13076 - Build time dependency for python3-exceptiongroup Adolf Belka
2023-05-10 13:04 ` [PATCH 5/7] python3-pkgconfig: Identified that this module is only required as a build time dependency Adolf Belka
2023-05-10 13:04 ` Adolf Belka [this message]
2023-05-10 13:04 ` [PATCH 7/7] make.sh: Fixes Bug#13076 Adolf Belka
2023-05-17 12:39 ` [PATCH 1/7] python3-trio: Fixes Bug#13076 - allows fuse mount to work again Adolf Belka
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=20230510130422.2676356-6-adolf.belka@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