Dear community,
Currently salsa service is experiencing performance issues, so it is not
possible for me to resolve these issues. Anki requires re-packaging for it
has now many Rust components.
What is needed? I've started repackaging on the anki-23-12 branch, but
dependencies include not-yet-packaged rust crates. These are
{axum-client-ip coarsetime fsrs htmlescape id-tree percent-encoding-iri
serde-aux serde-tuple utime}. Once these are packaged, I can finish the
re-packaging of anki. If anyone can help with this I'd appreciate it a lot!
Unfortunately with the salsa issues I cannot even login to salsa at
the moment and all git fetch/push operations fail.
If it's better to remove anki, until the repackaging is complete, then let
me know!
Kind regards,
Laurin
On Thu, Sep 5, 2024 at 8:21 AM Helmut Grohne <hel...@subdivi.de> wrote:
> Source: anki
> Severity: serious
> Justification: grab attention of maintainer
> User: helm...@debian.org
> Usertags: sidremove
>
> Dear maintainer,
>
> I suggest removing anki from Debian for the following reasons:
> * It accumulated 3 RC-bugs:
> + #958853: anki: old version beginning to fail with newer Python
> releases
> Last modified: 1 year, 2 months
>
> + #965258: anki: old version beginning to fail with newer Python
> releases
> Last modified: 1 year, 2 months
>
> + #1036438: anki: Anki outdated and causing problems in synchronizing
> and importing decks
> Last modified: 1 year, 2 months
>
> * It is not part of bookworm or trixie and is not a key package.
>
> This bug serves as a pre-removal warning. After one month, the bug will be
> reassigned to ftp.debian.org to actually request removal of the package.
>
> In case the package should be kept in unstable, please evaluate each of the
> RC-bugs listed above.
> * If the bug is meant to prevent the package from entering testing or a
> stable
> release, but this package should stay part of unstable, please add a
> usertag:
>
> user helm...@debian.org
> usertags NNN + sidremove-ignore
>
> * If the bug no longer applies, please close it. If it is closed, check
> whether the fixed version is correct and adjust if necessary.
>
> * Is the bug really release-critical? If not, please downgrade.
>
> * If the bug still applies, please send a status update at least once a
> year.
>
> Once all of the mentioned RC bugs have been acted upon in one way or
> another,
> please close this bug.
>
> In case the package should be removed from unstable, you may reassign this
> bug report:
>
> Control: severity -1 normal
> Control: retitle -1 RM: anki -- RoM; rc-buggy
> Control: reassign -1 ftp.debian.org
> Control: affects -1 + src:anki
>
> Alternatively, you may wait a month and have it reassigned.
>
> In case you disagree with the above, please downgrade this bug below RC
> severity. Doing so will also prevent automatic reassignment.
>
> Kind regards
>
> A tool for automatically removing packages from unstable
>
> This bug report has been automatically filed with little human
> intervention.
> If the filing is unclear or in error, don't hesitate to contact
> Helmut Grohne <hel...@subdivi.de> for assistance.
>
