Control: reopen -1 =
I reopen this bug as it is still not fixed in Debian.
The fact that it has been fixed upstream is documented by the fixed-
upstream tag, while this alone is not reason enough to close the bug.
The fixed version needs to be packaged in Debian first.
Sorry,
Sven
--
GPG Finger
Il 29/03/2023 10:11, c.bu...@posteo.jp ha scritto:
Do I see it correct that the commit was done but not yet uploaded?
In result there should be a 1.3.3-5, right?
There is still no reply from Jonathan Wiltshire, I also sent him a
mail some days ago.
I'll probably try to do a NMU in the week
Do I see it correct that the commit was done but not yet uploaded?
In result there should be a 1.3.3-5, right?
Hi Christian,
On Sun, 2023-03-05 at 19:18 +, c.bu...@posteo.jp wrote:
> Dear Sven,
>
> this is one of the upstream maintainers (@buhtz).
>
> Thanks a lot for your contribution. Keep in mind the the upstream PR
> isn't merged yet.
>
> And wouldn't it be better to use the next upstream releas
On 2023-03-05 19:52 Sven Geuer wrote:
> On Fri, 2023-03-03 at 01:46 +0100, BiT dev wrote:
> > [...]
> > https://github.com/bit-team/backintime/pull/1413
> > [...]
>
> I created a patch to backintime 1.3.3-4 and tested it successfully.
>
> Here is the merge request for a backintime 1.3.3-5:
> htt
On Fri, 2023-03-03 at 01:46 +0100, BiT dev wrote:
> [...]
> https://github.com/bit-team/backintime/pull/1413
> [...]
I created a patch to backintime 1.3.3-4 and tested it successfully.
Here is the merge request for a backintime 1.3.3-5:
https://salsa.debian.org/jmw/pkg-backintime/-/merge_requests
I have implemented the support for the ChainerBackend class of the python
keyring package
and it is currently on its way into the dev branch of BiT via this pull request:
https://github.com/bit-team/backintime/pull/1413
Any feed-back (esp. testing it on your computer) is welcome. THX a lot!
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
Control: reopen -1 =
Hello Christian,
On Fri, 20 Jan 2023 11:01:33 + c.bu...@posteo.jp wrote:
> Dear Sven,
>
> there is a new release 1.3.3 in "unstable" branch of Debian.
>
> Can you please try to reproduce the problem with that version and
> then report back.
>
> Thanks
> Christian
Unfo
Dear Sven,
there is a new release 1.3.3 in "unstable" branch of Debian.
Can you please try to reproduce the problem with that version and then
report back.
Thanks
Christian
> DEBUG: [common/tools.py:823 keyringSupported] No appropriate keyring found.
>'keyring.backends.chainer' can't be used with BackInTime
> ...
> Two Conclusion:
> 1) Backintime fails to access the keyring when keyring.backends.chainer is in
> use.
Correct.
The keyring.backends.chainer.cha
Package: backintime-qt
Version: 1.2.1-3
Severity: normal
Dear Maintainer,
In ssh mode backintime fails to read previously stored credentials since
python3-keyring 23.2.0-1 has been rolled out. Instead it always calls
backintime-askpass to query the password from the GUI.
Logs say it cannot work
16 matches
Mail list logo
