From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/7] python3-trio: Fixes Bug#13076 - allows fuse mount to work again
Date: Wed, 17 May 2023 14:39:33 +0200 [thread overview]
Message-ID: <32567ab7-0c52-7139-5aab-2a8ea9ee7448@ipfire.org> (raw)
In-Reply-To: <20230510130422.2676356-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2516 bytes --]
Hi All,
Could this patch set be reviewed for CU175.
The borgbackup fuse mount option stopped working since CU173. This patch
set is the fix for that.
Regards,
Adolf.
On 10/05/2023 15:04, Adolf Belka wrote:
> - In Core 173 python3-trio was updated to version 0.22.0 when python was upgraded to 3.10.8
> Although the build of python3-trio was successful it was missed that there was a new
> run-time dependency of python3-exceptiongroup for python3-pyfuse3 to work.
> python2-flit_scm is required as a build dependency for python3-exceptiongroup.
> - The modified packages were installed in my vm testbed and confirmed that borg mount then
> worked again.
> - It was also noted that python3-attr was no longer needed neither as a runtime
> dependency nor as a build time dependency.
> - Dependencies line of python3-trio updated for these two changes.
>
> Fixes: Bug#13076
> Tested-by: Adolf Belka <adolf.belka(a)ipfire.org>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> lfs/python3-trio | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lfs/python3-trio b/lfs/python3-trio
> index 2cae4bcf6..49f1207ab 100644
> --- a/lfs/python3-trio
> +++ b/lfs/python3-trio
> @@ -1,7 +1,7 @@
> ###############################################################################
> # #
> # IPFire.org - A linux based firewall #
> -# Copyright (C) 2007-2020 IPFire Team <info(a)ipfire.org> #
> +# Copyright (C) 2007-2023 IPFire Team <info(a)ipfire.org> #
> # #
> # This program is free software: you can redistribute it and/or modify #
> # it under the terms of the GNU General Public License as published by #
> @@ -33,9 +33,9 @@ DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> PROG = python3-trio
> -PAK_VER = 2
> +PAK_VER = 3
>
> -DEPS = python3-attr python3-async_generator python3-attrs python3-sniffio python3-sortedcontainers python3-outcome python3-idna
> +DEPS = python3-async_generator python3-attrs python3-sniffio python3-sortedcontainers python3-outcome python3-idna python3-exceptiongroup
>
> SERVICES =
>
--
Sent from my laptop
prev parent reply other threads:[~2023-05-17 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 13:04 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 ` [PATCH 6/7] borgbackup: Removed python3-pkgconfig as run " Adolf Belka
2023-05-10 13:04 ` [PATCH 7/7] make.sh: Fixes Bug#13076 Adolf Belka
2023-05-17 12:39 ` Adolf Belka [this message]
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=32567ab7-0c52-7139-5aab-2a8ea9ee7448@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