Is there a reason the fixes can't be cherrypicked and then SRU'd to fix
this issue? Backports is typically NOT the way to get fixes for issues
into already stable releases.
** Changed in: man-db (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
From what I read (and remember), the command doesn't freeze but just takes
a bit long.
Honestly I don't really consider such issue worth a backport, and it's not
really bringing any new feature to the table (at least, you are not
describing anything).
I was thinking that perhaps this could be
Backported debs in:
https://launchpad.net/~jrodrigu/+archive/ubuntu/bpo/+packages
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1992163
Title:
[BPO] man-db/2.10.2-1 from jammy
To
** Description changed:
[Impact]
- * Users of man-db/2.9.1-1 in focal are sometimes facing
+ * Users of man-db/2.9.1-1 in focal are sometimes facing
unresponsiveness when man-db is called from an `apt upgrade` or `apt
install` command (the man-db command freezes).
[Scope]
- *
You have been subscribed to a public bug by Jorge Rodríguez (jrodrigu):
[Impact]
* Users of man-db/2.9.1-1 in focal are sometimes facing
unresponsiveness when man-db is called from an `apt upgrade` or `apt
install` command (the man-db command freezes).
[Scope]
* Backport from jammy
