Your message dated Tue, 5 Feb 2019 21:23:41 +0000
with message-id <[email protected]>
and subject line Re: Bug#921224: anki: Syncing to AnkiWeb fails with Unknown
response code: 400
has caused the Debian Bug report #921224,
regarding anki: Syncing to AnkiWeb fails with Unknown response code: 400
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
921224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921224
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: anki
Version: 2.1.7+dsfg-1
Severity: normal
Dear Maintainer,
The current version of Anki (2.1.7) fails to sync with AnkiWeb,
and gives the following traceback:
Syncing failed:
Traceback (most recent call last):
File "/usr/share/anki/aqt/sync.py", line 348, in run
self._sync()
File "/usr/share/anki/aqt/sync.py", line 373, in _sync
self.hkey = self.server.hostKey(*self.auth)
File "/usr/share/anki/anki/sync.py", line 574, in hostKey
badAuthRaises=False)
File "/usr/share/anki/anki/sync.py", line 556, in req
self.assertOk(r)
File "/usr/share/anki/anki/sync.py", line 495, in assertOk
raise Exception("Unknown response code: %s" % resp.status_code)
Exception: Unknown response code: 400
After uninstalling via APT and then re-installing version 2.1.8 via
tarball (from ankisrs.net), syncing succeeds.
Any idea when 2.1.8 will be migrated to testing?
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages anki depends on:
ii libjs-jquery 3.3.1~dfsg-1
pn libjs-jquery-flot <none>
pn libjs-jquery-ui <none>
pn libjs-mathjax <none>
ii libqt5core5a 5.11.3+dfsg-2
ii python3 3.7.2-1
ii python3-bs4 4.6.3-2
pn python3-decorator <none>
ii python3-distutils 3.7.2-3
pn python3-markdown <none>
pn python3-pyaudio <none>
ii python3-pyqt5 5.11.3+dfsg-1+b3
ii python3-pyqt5.qtwebchannel 5.11.3+dfsg-1+b3
ii python3-pyqt5.qtwebengine 5.11.3+dfsg-1+b3
ii python3-requests 2.20.0-2
pn python3-send2trash <none>
Versions of packages anki recommends:
pn python3-matplotlib <none>
Versions of packages anki suggests:
pn dvipng <none>
pn lame <none>
ii mpv 0.29.1-1
--- End Message ---
--- Begin Message ---
Version: 2.1.8+dfsg-1
On Sun, Feb 03, 2019 at 07:12:25PM +0800, Ryan Lue wrote:
> Package: anki
> Version: 2.1.7+dsfg-1
> Severity: normal
>
> Dear Maintainer,
>
> The current version of Anki (2.1.7) fails to sync with AnkiWeb,
> and gives the following traceback:
>
> Syncing failed:
> [...]
> File "/usr/share/anki/anki/sync.py", line 495, in assertOk
> raise Exception("Unknown response code: %s" % resp.status_code)
> Exception: Unknown response code: 400
>
> After uninstalling via APT and then re-installing version 2.1.8 via
> tarball (from ankisrs.net), syncing succeeds.
>
> Any idea when 2.1.8 will be migrated to testing?
Dear Ryan,
That's quite strange. 2.1.7 works fine for me; there's also something
weird about ankiweb giving a status code of 400, which is a "Bad
request" code. Anyway, I've just uploaded version 2.1.8 to unstable,
so it should hit testing in about 5 days' time.
I hope this solves the problem for you, as you say that the upstream
2.1.8 works, so I'm closing this bug report in the meantime. Please
feel free to reopen it if 2.1.8 doesn't work for you.
Best wishes,
Julian
--- End Message ---
