##// END OF EJS Templates
ci: for branches, use a single trigger...
ci: for branches, use a single trigger This trigger will unlock all the job necessary to build wheels and upload nightly build. This should make the nightly build process more pratical. In practice right now, only run pipeline for branch by creating them explicitly on the web. So we could just run everything without trigger, but this is a decision for later. This changeset only focus on making the nightly build process somewhat manageable.

File last commit:

r47270:c82d6363 default
r53151:b65f11f4 stable
Show More
control
43 lines | 1.2 KiB | text/plain | DebianControlLexer
Source: mercurial
Section: vcs
Priority: optional
Maintainer: Mercurial Developers <mercurial-devel@mercurial-scm.org>
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
Provides: python3-mercurial
Architecture: any
Homepage: https://www.mercurial-scm.org/
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