annotate debian/control @ 6023:6c67219ce779 stable

topic: don't cache topic of e.g. memctx in _topiccache (issue6500)

_topiccache exists to make us hit the storage less often when we want to look
at topics for any reason. It doesn't make much sense to cache something that is
memory-only and is cheap to access however. Caching things like that was also a
source of a bug where creating multiple memctx instances in one process would
cache topic of the first one and ignore actual content of .extra() of the
others. That was happening because the cache is keyed by .rev(), but all memctx
instances have the same .rev() = None.

Source: mercurial-evolve
Section: vcs
Priority: optional
Maintainer: Logilab <[e-mail]>
Uploaders:
 Julien Cristau <[e-mail]>,
 Pierre-Yves David <[e-mail]>,
Standards-Version: 4.3.0
Build-Depends:
 mercurial (>= 4.6),
 python,
 python3,
 debhelper (>= 10),
 dh-python,
 python-sphinx,
 imagemagick,
 librsvg2-bin,
 graphviz,
X-Python3-Version: >= 3.6
Homepage: https://www.mercurial-scm.org/doc/evolution/
Vcs-Browser: https://www.mercurial-scm.org/repo/evolve/
Vcs-Hg: https://www.mercurial-scm.org/repo/evolve/

Package: mercurial-evolve
Architecture: all
Depends:
 ${python:Depends},
 ${python3:Depends},
 ${misc:Depends},
 ${sphinxdoc:Depends},
 mercurial (>= 4.6),
Built-Using: ${sphinxdoc:Built-Using}
Description: evolve extension for Mercurial
 This package provides the experimental "evolve" extension for the Mercurial
 DVCS.
 .
 This extension provides several commands to mutate history and deal with issues
 it may raise.