contrib/packaging/debian/control

configitems: add a new config option to control new filenode functionality

This series is adding functionality where we can force create a new filenode for
some files on a merge-commit. This is meant to represent an explicit choice made
by user and hence distingusing the file in the merged commit with the file in
parent by creating a new filenode instead of using the parent one.

This introduces a experimental config option under which this functionality
will be hidden.

A new testcase is added in tests/test-merge-criss-cross.t to test the new
functionality while making the option does not break other scenarios.

Differential Revision: https://phab.mercurial-scm.org/D9026

Source: mercurial
Section: vcs
Priority: optional
Maintainer: Mercurial Developers <[e-mail]>
Build-Depends:
 debhelper (>= 9),
 dh-python,
 less,
 netbase,
 python3-all,
 python3-all-dev,
 python3-docutils,
 unzip,
 zip
Standards-Version: 3.9.4
X-Python3-Version: >= 3.5

Package: mercurial
Depends:
 sensible-utils,
 ${shlibs:Depends},
 ${misc:Depends},
 ${python3:Depends},
Recommends: ca-certificates
Suggests: wish
Replaces: mercurial-common
Breaks: mercurial-common
Architecture: any
Description: fast, easy to use, distributed revision control tool.
 Mercurial is a fast, lightweight Source Control Management system designed
 for efficient handling of very large distributed projects.
 .
 Its features include:
  * O(1) delta-compressed file storage and retrieval scheme
  * Complete cross-indexing of files and changesets for efficient exploration
    of project history
  * Robust SHA1-based integrity checking and append-only storage model
  * Decentralized development model with arbitrary merging between trees
  * Easy-to-use command-line interface
  * Integrated stand-alone web interface
  * Small Python codebase