See inline below ...
On Fri, 2023-02-24 at 16:26 +0100, Jürgen Altfeld wrote:
[...]
>
> I now realize (thanks to your persistence & asking the right
> questions - excellent soft skills BTW :-)
Thanks for the kudos :-)
[...]
>
> 1. Would you agree with my proposal to fix it (just enabling
> Cha
I have opened a new issue at BiT:
https://github.com/bit-team/backintime/issues/1410
Would it be possible to continue or conversation about this bug there
to make it visible for others (= non-Debian users of BiT)?
THX :-)
On Thu, 23 Feb 2023 21:38:55 +0100 Sven Geuer wrote:
> The current situation just does not deem user friendly to me.
> I am afraid the average user is unable to detect what the problem is and how
> to fix it,
> especially as things worked out of the box before python3-keyring 23.2.0-1
> was int
Hi BiT Dev,
thank you for the detailled reply.
More inline below ...
On Thu, 2023-02-23 at 01:53 +0100, BiT dev wrote:
> On Tue, 21 Feb 2023 20:40:21 +0100 Sven Geuer
> wrote:
>
> > I still need to pin python3-keyring to use
> > keyring.backends.SecretService.
>
> What do you mean with "pin"?
On Tue, 21 Feb 2023 20:40:21 +0100 Sven Geuer wrote:
> I still need to pin python3-keyring to use
> keyring.backends.SecretService.
What do you mean with "pin"? Installing an old version of python3-keyring
(without the chainer) by pinning the ("old") DEB package (version)?
> Unfortunately BiT
5 matches
Mail list logo
