mercurial-lang-5.9.1-150400.3.3.1 < > , 5x de(rp9| \9a}.KS-oPBbLz%Mv=V maNy[@ x4P]KB*/VH)jlmusD'(xHe:u8N=hf%n"ZlڮC\1CtELCzRV
gk;kLT8LȌÐM /qc.ͣ;Ժ4G ?gקf,S60-/mXSR > > - ? , d $ G | & 0 ` x
D } ( 8 R 9 R : R F (4 G (H H (x I ( X ( Y ( \ ( ] ) ^ )h b + c + d ,6 e ,; f ,> l ,@ u ,T v , z , , , , , , , , C mercurial-lang 5.9.1 150400.3.3.1 Translations for package mercurial Provides translations for the "mercurial" package. de(rsheep74 O=SUSE Linux Enterprise 15 SUSE LLC GPL-2.0-or-later https://www.suse.com/ System/Localization https://www.mercurial-scm.org/ linux noarch w z ( S r_ m ) jF de( de(de(
de(
de(
de( de( de( de(
de(
de(
de( a43b4ad25c6a2fa545749ec3990ff54975e707b237e07b04e97ab564b551675a d51ad7efcfaa1bae612645684537c25e286910ddedb639fc21a9f9ec4a641679 64b21b2f94371d6b2f64bfecb0466bfb4062b3d16e0b47780a3353c2f890a597 a94643864c022b8a8cad86c0dbd11b324045db9eaf329f962e91e649485e26df 8ad918317c2ee1804e638adcb90c7dd01ec52d050dc21f1e195bee1456a186c0 a706dc8b4601763debc1228ad231d76166f30949afd66d69b89ca35adf80f3a6 6a018a6d0fed3f4814beca30b72df626dbd634515eb30f3e68e4349dbee270c5 efec3481352f093a5bba864b33028b899ae0d61edd3e5f86bb849ed683abd3df c6aacd631bdce6821bb3844b2d46cec15a4f6432df6d8f43f2620da9e1dd59a5 4f9115e5549598d13e8bad281a0582a98136222976f62fd886fc3a8aa0c3a6a0 6508c0142ed6f44aa94b00d8a3a57ae90035a7636d99601f254b18e38bb48f0d 2eea3ec47386792043c7afd1f0351a8492340070c25b7dbe2025b82dabdc503f root root root root root root root root root root root root root root root root root root root root root root root root mercurial-5.9.1-150400.3.3.1.src.rpm mercurial-lang mercurial-lang-all
mercurial rpmlib(CompressedFileNames) rpmlib(FileDigests) rpmlib(PayloadFilesHavePrefix) rpmlib(PayloadIsXz) 5.9.1 3.0.4-1 4.6.0-1 4.0-1 5.2-1 4.14.3 dGaMaHwa0````j`!'_v@_u@_xg_P_)M^@^ۅ@^@^@^s^^AE^,]B]6@]]~']D%]$]
#\@\}\\T4\4\[@[ݍ[][@[p!@[;e@[oZZľ@ZZ@ZvZ@Y@Y@YJY\Y @XXXoX@W@W9W]NW;W(W'A@VVV@VwV@Vd#@VC-V?9@VUU@Uz@UF
U TT@T T@T T@Tg@@tiwai@suse.com sweiberg@suse.com expeehaa@outlook.com develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info andreas.stieger@gmx.de develop7@develop7.info andreas.stieger@gmx.de develop7@develop7.info develop7@develop7.info andreas.stieger@gmx.de andreas.stieger@gmx.de andreas.stieger@gmx.de andreas.stieger@gmx.de andreas.stieger@gmx.de develop7@develop7.info mcepl@suse.com andreas.stieger@gmx.de develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info wr@rosenauer.org develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info tiwai@suse.de tiwai@suse.de develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info mpluskal@suse.com develop7@develop7.info develop7@develop7.info develop7@develop7.info astieger@suse.com develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info wr@rosenauer.org develop7@develop7.info wr@rosenauer.org wr@rosenauer.org wr@rosenauer.org wr@rosenauer.org wr@rosenauer.org develop7@develop7.info develop7@develop7.info develop7@develop7.info wr@rosenauer.org matwey.kornilov@gmail.com develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info develop7@develop7.info - Fix unexprted abort at cloning a repo (bsc#1210707):
mercurial-5.9.1-bsc1210707.patch - Adding bug and CVE references from SLE to prepare the submission
for SLE 15 SP4/Leap 15.4
- CVE-2019-3902 (bsc#1133035) not affecting versions 5.0+ SLE
internal patches removed:
* hg-CVE-2019-3902-fix1.patch
* hg-CVE-2019-3902-fix2.patch
* hg-CVE-2019-3902-fix3.patch
- CVE-2018-17983 (bsc#1110899) not affecting versions 4.7.2+ SLE
internal patch removed:
* hg-CVE-2018-17983.patch
- CVE-2018-13346 (bsc#1100354), CVE-2018-13347 (bsc#1100355),
CVE-2018-13348 (bsc#1100353) not affecting versions 4.6.1+ SLE
internal patches removed:
* hg-mpatch-fix01.patch
* hg-mpatch-fix02.patch
* hg-mpatch-fix03.patch
* hg-mpatch-fix04.patch
* hg-mpatch-fix05.patch
* hg-mpatch-fix06.patch
* hg-mpatch-fix07.patch
* hg-mpatch-fix08.patch
* hg-mpatch-fix09.patch - Provide mercurial tests in a package mercurial-tests. - Mercurial 5.9.1
No upstream release notes, see
https://www.mercurial-scm.org/repo/hg/log?rev=5.9..5.9.1 for changelog
- Mercurial 5.9
+ New Features
* `hg config` now has a `--source` option to show where each configuration
value comes from. - Mercurial 5.8.1
No upstream release notes, see
https://www.mercurial-scm.org/repo/hg/log?rev=5.8..5.8.1 for changes - Mercurial 5.8
+ New Features
* `hg purge` is now a core command using `--confirm` by default.
* The `rev-branch-cache` is now updated incrementally whenever changesets
are added.
* The new options `experimental.bundlecompthreads` and
`experimental.bundlecompthreads.` can be used to instruct the
compression engines for bundle operations to use multiple threads for
compression. The default is single threaded operation. Currently only
supported for zstd.
+ Default Format Change
These changes affects newly created repositories (or new clone) done with
Mercurial 5.8.
* The `ZSTD` compression will now be used by default for new repositories
when available. This compression format was introduced in Mercurial 5.0,
released in May 2019. See `hg help config.format.revlog-compression` for
details.
* Mercurial installation built with the Rust parts will now use the
"persistent nodemap" feature by default. This feature was introduced in
Mercurial 5.4 (May 2020). However Mercurial instalation built without
the fast Rust implementation will refuse to interract with them
by default. This restriction can be lifted through configuration.
See `hg help config.format.use-persistent-nodemap` for details
+ New Experimental Features
* There's a new `diff.merge` config option to show the changes relative to
an automerge for merge changesets. This makes it easier to detect and
review manual changes performed in merge changesets. It is supported
by `hg diff --change`, `hg log -p` `hg incoming -p`,
and `hg outgoing -p` so far.
+ Bug Fixes
* gracefully recover from inconsistent persistent-nodemap data from disk.
+ Backwards Compatibility Changes
* In normal repositories, the first parent of a changeset is not null,
unless both parents are null (like the first changeset). Some legacy
repositories violate this condition. The revlog code will now silentely
swap the parents if this condition is tested. This can change the output
of `hg log` when explicitly asking for first or second parent. The
changesets "nodeid" are not affected.
+ Internal API Changes
* `changelog.branchinfo` is deprecated and will be removed after 5.8.
It is superseded by `changelogrevision.branchinfo`.
* Callbacks for revlog.addgroup and the changelog._nodeduplicatecallback
hook now get a revision number as argument instead of a node.
* revlog.addrevision returns the revision number instead of the node.
* `nodes.nullid` and related constants are being phased out as part of
the deprecation of SHA1. Repository instances and related classes
provide access via `nodeconstants` and in some cases `nullid` attributes.
- updated mercurial-locale-path-fix.patch - enable building `chg` (thanks @expehaa) - Mercurial 5.7.1
* No upstream release notes, see
https://www.mercurial-scm.org/repo/hg/log?rev=tag%28%225.7%22%29%3A%3Atag%28%225.7.1%22%29 - added the _service file for updating sources with single command
- Mercurial 5.7
This is a regularly-scheduled quarterly feature release.
+ New Features
* There is a new config section for templates used by hg commands. It
is called `[command-templates]`. Some existing config options have
been deprecated in favor of config options in the new
section. These are: `ui.logtemplate` to `command-templates.log`,
`ui.graphnodetemplate` to `command-templates.graphnode`,
`ui.mergemarkertemplate` to `command-templates.mergemarker`,
`ui.pre-merge-tool-output-template` to
`command-templates.pre-merge-tool-output`.
* There is a new set of config options for the template used for the
one-line commit summary displayed by various commands, such as
`hg rebase`. The main one is `command-templates.oneline-summary`. That
can be overridden per command with
`command-templates.oneline-summary.`, where ``
can be e.g. `rebase`. As part of this effort, the default format
from `hg rebase` was reorganized a bit.
* `hg purge` is now a core command using `--confirm` by default.
* `hg strip`, from the strip extension, is now a core command,
`hg debugstrip`. The extension remains for compatibility.
* `hg diff` and `hg extdiff` now support `--from ` and `--to `
arguments as clearer alternatives to `-r `. `-r ` has been
deprecated.
* The memory footprint per changeset during pull/unbundle
operations has been further reduced.
* There is a new internal merge tool called `internal:mergediff` (can
be set as the value for the `merge` config in the `[ui]`
section). It resolves merges the same was as `internal:merge` and
`internal:merge3`, but it shows conflicts differently. Instead of
showing 2 or 3 snapshots of the conflicting pieces of code, it
shows one snapshot and a diff. This may be useful when at least one
side of the conflict is similar to the base. The new marker style
is also supported by "premerge" as
`merge-tools..premerge=keep-mergediff`.
* External hooks are now called with `HGPLAIN=1` preset. This has the side
effect of ignoring aliases, templates, revsetaliases, and a few other config
options in any `hg` command spawned by the hook. The previous behavior
can be restored by setting HGPLAINEXCEPT appropriately in the parent process.
See `hg help environment` for the list of items, and how to set it.
* The `branchmap` cache is updated more intelligently and can be
significantly faster for repositories with many branches and changesets.
* The `rev-branch-cache` is now updated incrementally whenever changesets
are added.
+ New Experimental Features
* `experimental.single-head-per-branch:public-changes-only` can be used
restrict the single head check to public revision. This is useful for
overlay repository that have both a publishing and non-publishing view
of the same storage.
+ Backwards Compatibility Changes
* `--force-lock` and `--force-wlock` options on `hg debuglock` command are
renamed to `--force-free-lock` and `--force-free-wlock` respectively.
+ Internal API Changes
* `changelog.branchinfo` is deprecated and will be removed after 5.8.
It is superseded by `changelogrevision.branchinfo`. - mercurial 5.6.1:
* no upstream changelog - Mercurial 5.6
This is a regularly-scheduled quarterly feature release.
* New Features
+ `hg mv -A` can now be used with `--at-rev`. It behaves just like
`hg cp -A --at-rev`, i.e. it marks the destination as a copy of the
source whether or not the source still exists but the source must exist
in the parent revision).
+ New revset predicate `diffcontains(pattern)` for filtering revisions the
same way as `hg grep --diff pattern`.
+ The memory footprint per changeset and per file during pull/unbundle
operations has been significantly reduced.
* Internal API Changes
+ `merge.update()` is now private (renamed to `_update()`). Hopefully the
higher-level functions available in the same module cover your use cases.
+ `phases.registernew` now takes a set of revisions instead of a list
of nodes. `phases.advanceboundary` takes an optional set of revisions in
addition to the list of nodes. The corresponding members of the
`phasecache` class follow this change.
+ The `addgroup` member of `revlog` classes no longer keeps a list of all
found nodes. It now returns `True` if a node was found in the group.
An optional callback for duplicated nodes can be used by callers to keep
track of all nodes themselve.
+ The `_chaininfocache` of `revlog` classes has been changed from a dict
to a LRU cache. - Mercurial 5.5.2:
* fix a crash in the log command
* bug fixes in hgdemandimport
* stip: with --keep, consider all revs "removed" from the wcp - Mercurial 5.5.1:
Regularly scheduled bug fix release.
* bug fixes
+ keepalive: Do not append _rbuf if _raw_readinto exists (issue6356) - Mercurial 5.5:
This is a regularly-scheduled quarterly feature release
* New Features
+ clonebundles can be annotated with the expected memory requirements
using the `REQUIREDRAM` option. This allows clients to skip bundles
created with large zstd windows and fallback to larger, but less
demanding bundles.
+ The `phabricator` extension now provides more functionality of the
arcanist CLI like changing the status of a differential.
+ Phases processing is much faster, especially for repositories with old
non-public changesets.
* New Experimental Features
+ The core of some hg operations have been (and are being) implemented in
rust, for speed. `hg status` on a repository with 300k tracked files
goes from 1.8s to 0.6s for instance. This has currently been tested only
on linux, and does not build on windows. See rust/README.rst in the
mercurial repository for instructions to opt into this.
+ An experimental config `rewrite.empty-successor` was introduced
to control what happens when rewrite operations result
in empty changesets.
* Bug Fixes
+ For the case when connected to a TTY, stdout was fixed
to be line-buffered on Python 3 (where it was block-buffered before,
causing the process to seem hanging) and Windows on Python 2 (where it
was unbuffered before).
+ Subversion sources of the convert extension were fixed to work
on Python 3.
+ Subversion sources of the convert extension now interpret the encoding
of URLs like Subversion. Previously, there were situations where
the convert extension recognized a repository as present but Subversion
did not, and vice versa.
+ The empty changeset check of in-memory rebases was fixed to match that
of normal rebases (and that of the commit command).
+ The push command now checks the correct set of outgoing changesets for
obsolete and unstable changesets. Previously, it could happen that the
check prevented pushing changesets which were already on the server.
* Backwards Compatibility Changes
+ Mercurial now requires at least Python 2.7.9 or a Python version that
backported modern SSL/TLS features (as defined in PEP 466), and that
Python was compiled against a OpenSSL version supporting TLS 1.1 or
TLS 1.2 (likely this requires the OpenSSL version to be at least 1.0.1).
+ The `hg perfwrite` command from contrib/perf.py was made more flexible
and changed its default behavior. To get the previous behavior, run
`hg perfwrite --nlines=100000 --nitems=1 --item='Testing write performance' --batch-line`.
+ The absorb extension now preserves changesets with no file changes that
can be created by the commit command (those which change the branch name
compared to the parent and those closing a branch head). - Mercurial 5.4.2:
* rebase: avoid clobbering wdir() with --dry-run or --confirm
* curses: do not initialize LC_ALL to user settings - Mercurial 5.4.1:
* graft-state: save --base in graft's state, fixing bug with
graft --continue
* graft: fix --base value to be saved in state file
* dirstate: make sure the dirstate is loaded before the changelog
* bash_completion: do not use aliased hg if it sources a script
* demandimport: fix compatibility with meta path finders w/o
find_spec() method
* flags: read flag from dirstate/disk for workingcopyctx
* fsmonitor: coerce 'clock' variable to byte-string
* url: fix a bytes vs str crash in processing proxy headers - Mercurial 5.4:
* hg purge/hg clean can now delete ignored files instead of
untracked files, with the new -i flag.
* hg pull now has a --confirm flag to prompt before applying
changes. Config option pull.confirm is also added for that.
* hg log now defaults to using an '%' symbol for commits involved
in unresolved merge conflicts. That includes unresolved
conflicts caused by e.g. hg update --merge and hg graft. '@'
still takes precedence, so what used to be marked '@' still is.
* hg copy --forget can be used to unmark a file as copied.
* The format.revlog-compression configuration entry now accept
a list. The first available option will be used. for example
setting::
[format]
revlog-compression=zstd, zlib
Will use zstd compression for new repositories is available,
and will simply fall back to zlib if not.
* hg debugmergestate output is now templated, which may be useful
e.g. for IDEs that want to help the user resolve merge
conflicts.
* hg copy now supports a --at-rev argument to mark files as
copied in the specified commit. It only works with --after for
now (i.e., it's only useful for marking files copied using non-hg
cp as copied).
* Use hg copy --forget --at-rev REV to unmark already committed
copies.
* bug fixes
* changes that may affect backwards compatibility
- there is no canonical upstream signing key, remove - fix bash completion script (boo#1170703) - Mercurial 5.3.1 - Mercurial 5.3
This is a regularly-scheduled quarterly feature release.
See release notes at https://www.mercurial-scm.org/wiki/Release5.3
- drop mercurial-4.8-python2-shebang.patch because of switch to Python 3
- fixed and refreshed mercurial-locale-path-fix.patch - Switch Mercurial to Python 3 (it should be supported already,
according to https://www.mercurial-scm.org/wiki/Python3)
- Fix rpmlint warnings. - Mercurial 5.2.1 - Mercurial 5.2
This is a regularly-scheduled quarterly feature release.
+ New Features
* The amend extension supports the `--currentuser` argument.
* The amend extension supports the `--close-branch` argument.
* The amend extension supports the `--secret` argument.
* The uncommit extension supports the `rewrite.update-timestamp` config
option.
+ Backwards Compatibility Changes
* A shell that supports `$(command)` syntax for command substitution is
now required for running the test suite. The test runner normally
uses `sh`, so if that is a shell that doesn't support `$(command)`
syntax, you can override it by setting `$HGTEST_SHELL` or by passing it
to `run-tests.py --shell `.
* The (experimental) narrow extension's wire protocol changed. If you're
using it, you'll need to make sure to upgrade server and client at the
same time.
- refreshed mercurial.keyring - Mercurial 5.1.2
Regularly scheduled bug fix release.
* extensions
+ phabricator: don't abort if property writing fails during amending
* tests
+ test: allow different result for zstd compression (issue6188) - Mercurial 5.1.1
Regularly scheduled bug fix release.
* commands
+ bookmarks: actual fix for race condition deleting bookmark
* core
+ exchange: abort on pushing bookmarks pointing to secret changesets (issue6159)
+ python-zstandard: apply big-endian fix (issue6188)
+ fncache: make debugrebuildfncache not fail on broken fncache
* tests
+ various test runner fixes
+ fixed use of `tr --delete` for tr(1) portability - Mercurial 5.1
This is a regularly-scheduled quarterly feature release.
* New Features
+ New config `commands.commit.post-status` shows status after successful
commit.
+ `hg root` now has templating support, including support for showing
where a repo share's source is. See `hg help -v root` for details.
+ New `--force-close-branch` flag for `hg commit` to forcibly close branch
from a non-head changeset.
+ The curses-based interface for commands like `hg commit -i` now supports
a range-select mechanism. Select the first line using space like before,
navigate to the last line, and press X (capital x) to set all items in
the range at once. Lowercase x has been added as a synonym for space to
help reinforce the mechanism, and pressing enter/return continues to be a
synonym for "toggle the current line and move down to the next item in
this section."
* New Experimental Features
+ New config `experimental.log.topo` makes `hg log -G` use topological
sorting. This is especially useful for aliases since it lets the alias
accept an `-r` option while still using topological sorting with or
without the -r (unlike if you use the `sort(..., topo)` revset).
* Bug Fixes
+ issue4292: "hg log and {files} {file_adds} {file_mods} {file_dels} in
template show wrong files on merged revision". See details in "Backwards
Compatibility Changes".
* Backwards Compatibility Changes
+ Removed (experimental) support for log graph lines mixing
parent/grandparent styles. Setting e.g.
`experimental.graphstyle.parent = !` and
`experimental.graphstyle.grandparent = 3.` would use `!` for the first
three lines of the graph and then `..`. This is no longer supported.
+ If ui.origbackuppath had been (incorrectly) configured to point to a
file, we will now replace that file by a directory and put backups in
that directory. This is similar to how we would previously replace files
* in* the configured directory by subdirectories.
+ Template keyword `{file_mods}`, `{file_adds}`, and `{file_dels}` have
changed behavior on merge commits. They used to be relative to the first
parent, but they now consider both parents. `{file_adds}` shows files
that exists in the commit but did not exist in either parent.
`{file_dels}` shows files that do not exist in the commit but existed in
either parent. `{file_mods}` show the remaining files from `{files}`
that were not in the other two sets.
* Internal API Changes
+ Matchers are no longer iterable. Use `match.files()` instead.
+ `match.visitdir()` and `match.visitchildrenset()` now expect the empty
string instead of `'.'` to indicate the root directory.
+ `util.dirs()` and `util.finddirs()` now include an entry for the root
directory (empty string).
+ `shelve` is no longer an extension now. It will be turned on by default.
+ New API to manage unfinished operations: Earlier there were distinct APIs
which dealt with unfinished states and separate lists maintaining them
that are `cmdutil.afterresolvestates`, `cmdutil.unfinishedstates`
and `cmdutil.STATES`. Now these have been unified to a single API which
handles the various states and their utilities. This API has been added
to `state.py`. Now instead of adding to these 3 lists independently a
state for a new operation can be registered using `addunfinished()`
in `state` module.
+ `cmdutil.checkunfinished()` now includes detection for merge too.
+ merge abort has been disallowed in case an operation of higher
precedence is in progress to avoid cases of partial abort of operations.
+ We used to automatically attempt to make extensions compatible with
Python 3 (by translating their source code while loading it).
We no longer do that. - Mercurial 5.0.2
A regularly scheduled bugfix release.
+ commands
* Help fixes on hg mv and hg cp
+ unsorted
* debugrevlog: fix average size computation for empty data (issue6167)
* Fix an obscure data corruption bug with musl libc
(and presumably others).
See https://www.mercurial-scm.org/repo/hg-committed/rev/97ada9b8d51b
for more details. - Mercurial 5.0.1
A regularly scheduled bugfix release.
+ commands
* bookmark: also make bookmark cache depends of the changelog
* commit: allow --interactive to work again when naming a directory (issue6131)
+ unsorted
* manifest: avoid corruption by dropping removed files with pure (issue5801)
* sslutil: fsencode path returned by certifi (issue6132) - Mercurial 5.0
This is a regularly-scheduled quarterly feature release.
+ New Features
* Python 3 Support (Beta)
* `ui.relative-paths` option for getting relative path output from most
commands. This is enabled when `ui.tweakdefaults` is enabled.
* `expectsize()` revset errors out if revset has unexpected number
of elements.
* `config()` template function for getting a config value.
* `{negrev}` template keyword shows the negative revision number. This is
convenient because it is usually shorter than the positive number, but
note that it is less stable.
* `hg uncommit` now has an `--allow-dirty-working-copy` option.
* `hg shelve` now has `--keep` option, which shelves but also leaves the
working directory unchanged.
* `hg diff` will now include specified files in subrepos.
* `hg recover` now has a `--no-verify` option
+ Other Improvements
* Improved color scheme for histedit's curses interface, making it more
consistent with the curses hunk selector.
+ Bug Fixes
* Histedit's curse interface has improved support for non ascii characters.
+ Backwards Compatibility Changes
* color: change color of grep.rev label (BC)
* commit: if interactive, look elsewhere for whitespace settings (BC)
* diff: make sure we output stat even when --git is not passed (issue4037) (BC)
* uncommit: abort if an explicitly given file cannot be uncommitted (BC) - require openssl python module for runtime (not only build)
(boo#1132347) - Mercurial 4.9.1
A regularly scheduled bugfix release, late due to vacations and similar
disruptions at the regular time.
* commands
+ record: prevent commits that don't pick up dirty subrepo
changes (issue6102)
* extensions
+ rebase: add missing dashes in help text
* unsorted
+ subrepo: avoid false unsafe path detection on Windows
+ test-https: add some more known failure messages of client
certs (issue6030) - Mercurial 4.9
This is a regularly-scheduled quarterly feature release.
See complete changelog at
https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.9_.282019-02-01.29
* Security Fixes
It was possible to use symlinks and subrepositories to defeat Mercurial's
path-checking logic and write files outside a repository. This has been
fixed. Users on older versions can either disable subrepositories witt
```
[subrepos]
allowed = false
```
in their configuration or by ensuring any cloned repositories don't
contain malicious symlinks.
* New Features
+ 'hg histedit' will now present a curses UI if curses is available and
'ui.interface' or 'ui.interface.histedit' is set to 'curses'.
+ The 'sparse-revlog' delta strategy is enabled by default for new
repositories. See `hg help config.format.sparse-revlog` for details.
* Other Notable Features
+ New `rewrite.update-timestamp=True` option to update the commit
timestamp on history editing (e.g. amend.)
+ New `ui.message-output=stderr` option for scripting, which prevents
status messages from interleaved.
+ New `rootglob:` filename pattern for a glob that is rooted at the root
of the repository. See `hg help patterns` and `hg help hgignore` for
details.
+ Some more reimplementation of ancestry algorithms in Rust for better
performance.
* Backwards Compatibility Changes
+ Boolean options passed to the logtoprocess extension are now formatted
as "0" or "1" instead of "None", "False", or "True".
+ The logtoprocess extension no longer supports invalid "ui.log()"
arguments. A log message is always formatted and passed in to the
"$MSG1" environment variable.
* Internal API Changes
+ Status messages may be sent to a dedicated stream depending on
configuration. Don't use "ui.status()", etc. as a shorthand for
conditional writes. Use "ui.write()" for data output.
+ Add 'exthelper' class to simplify extension writing by allowing
functions, commands, and configitems to be registered via annotations.
The previous APIs are still available for use.
+ The extension hook "extsetup" without a 'ui' argument has been
deprecated, and will be removed in the next version. Add a 'ui' argument
to avoid the deprecation warning. - Mercurial 4.8.2
This is a regularly-scheduled bugfix release containing following fixes:
* commands
+ update: do not pass in user revspec as default destination (issue6044)
* core
+ match: fix assertion for fileset with no context (issue6046)
+ revlog: catch delta base value under -1
+ revlog: catch revlog corruption in index_baserev
+ server: always close http socket if responding with an error (issue6033)
+ vfs: ensure closewrapbase fh doesn't escape by entering context manager
* extensions
+ phabricator: properly encode boolean types in the request body
* unsorted
+ windows: ensure mixedfilemodewrapper fd doesn't escape by entering context mgr
+ worker: do not swallow exception occurred in main process - Mercurial 4.8.1
A regularly scheduled bugfix release. Some security fixes are included, but
all are expected to be low-risk.
* commands
- commandserver: get around ETIMEDOUT raised by selectors2
- graft: do not try to skip rev derived from ancestor more than
once (issue6024)
- verify: provide unit to ui.makeprogress()
* core
- revlog: fix out-of-bounds access by negative parents read from
revlog (SEC)
* extensions
- rebase: abort in-mem rebase if there's a dirty merge state
- rebase: fix dir/file conflict detection when using in-mem merge
- rebase: fix path auditing to audit path relative to repo root (issue5818)
- rebase: preserve working copy when redoing in-mem rebase on disk
* unsorted
- tests: stabilize test-inherit-mode.t on FreeBSD and macOS (issue6026) - mercurial-4.8-python2-shebang.patch: fixes boo#1114895
- explicitly depend on Python 2.7+ - Mercurial 4.8
This is a regularly-scheduled quarterly feature release.
See release overview at https://www.mercurial-scm.org/wiki/Release4.8 and
complete changelog at
https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.8_.282018-11-02.29 - Mercurial 4.7.2
This is a regularly-scheduled bugfix release containing following fixes:
* security
+ Fix a potential out-of-bounds read in manifest parsing C code.
* core
+ various minor correctness fixes in revsets for commonancestors() and
similar
* unsorted
+ chgserver: do not send system() back to client if stdio
redirected (issue5992)
+ procutil: compare fd number to see if stdio protection
is needed (issue5992) - Mercurial 4.7.1
This is a regularly-scheduled bugfix release containing following fixes:
* commands
+ merge: do not delete untracked files silently (issue5962)
* core
+ revlog: fix descendant deprecated method
* hgweb
+ hgweb: load revcount + 1 entries to fill nextentry in log page (issue5972)
* performance
+ remotephase: avoid full changelog iteration (issue5964)
+ remotephase: fast path newheads computation in simple case (issue5964)
+ scmutil: avoid quadratic membership testing (issue5969)
+ sparse-revlog: fix delta validity computation - Mercurial 4.7
This is a regularly-scheduled quarterly feature release and has it's own
release notes page which can be found here:
[Full release notes](https://www.mercurial-scm.org/wiki/Release4.7) - Mercurial 4.6.2
This is a regularly-scheduled bugfix release containing following fixes:
* merge: do not fill manifest of committed revision with pseudo node
(issue5526)
* crecord: fix line number in hunk header (issue5917)
* lazymanifest: don't crash when out of memory (issue5916)
* procutil: use unbuffered stdout on Windows - Mercurial 4.6.1
This is a regularly-scheduled bugfix release that also contains security
fixes.
* Security Fixes
Multiple issues found in mpatch.c with a fuzzer:
+ OVE-20180430-0001
+ OVE-20180430-0002
+ OVE-20180430-0004
With the following fixes:
mpatch: be more careful about parsing binary patch data (SEC)
mpatch: protect against underflow in mpatch_apply (SEC)
mpatch: ensure fragment start isn't past the end of orig (SEC)
mpatch: fix UB in int overflows in gather() (SEC)
mpatch: fix UB integer overflows in discard() (SEC)
mpatch: avoid integer overflow in mpatch_decode (SEC)
mpatch: avoid integer overflow in combine() (SEC)
No exploits are known at the time, however, it is highly recommended that
all users upgrade.
* Bug Fixes
Also included in this release are the following,
+ zstandard: pull in bug fixes from upstream 0.9.1 (issue5884)
+ bundle2: fix old clients from reading newer format (issue5872)
+ bdiff: fix xdiff long/int64 conversion (issue5885)
+ push: continue without locking on lock failure other than EEXIST (issue5882)
+ lfs: fix crash in command server (issue5902)
+ hghave: fix deadlock in test runner
+ rebase: fix error when computing obsoletenotrebased (issue5907)
+ rebase: prioritize indicating an interrupted rebase over update (issue5838)
+ revset: pass in lookup function to matchany() (issue5879) - Mercurial 4.6
This is a regularly-scheduled quarterly feature release.
See complete changelog at https://www.mercurial-scm.org/wiki/Release4.6 - Mercurial 4.5.3
This is a regularly-scheduled bugfix release.
* Bug Fixes
+ rebase: on abort, don't strip commits that didn't need to be rebased
(issue5822)
+ hgweb: garbage collect on every request
+ amend: abort if unresolved merge conflicts found (issue5805) - Modernize spec-file by calling spec-cleaner - Mercurial 4.5.2
(4.5.2 was released immediately after 4.5.1 to fix a release oversight.)
1. Security Fixes (CVE-2018-1000132,bsc#1085211)
All versions of Mercurial prior to 4.5.2 have vulnerabilities in the HTTP
server that allow permissions bypass to:
* Perform writes on repositories that should be read-only
* Perform reads on repositories that shouldn't allow read access
2. Backwards Compatibility Changes
The "batch" wire protocol command now enforces permissions of each invoked
sub-command. Wire protocol commands must define their operation type or the
"batch" command will assume they can write data and will prevent their
execution on HTTP servers unless the HTTP request method is POST, the
server is configured to allow pushes, and the (possibly authenticated) HTTP
user is authorized to perform a push.
Wire protocol commands not defining their operation type in
"wireproto.PERMISSIONS" are now assumed to be used for "push" operations
and access control to run those commands is now enforced accordingly.
3. Bug Fixes
fileset: don't abort when running copied() on a revision with a removed file
date: fix parsing months
setup: only allow Python 3 from a source checkout (issue5804)
annotate: do not poorly split lines at CR (issue5798)
subrepo: don't attempt to share remote sources (issue5793)
subrepo: activate clone pooling to enable sharing with remote URLs
changegroup: do not delta lfs revisions
revlog: do not use delta for lfs revisions
revlog: resolve lfs rawtext to vanilla rawtext before applying delta
See full cnahgelog on
https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.5.1_.2F_4.5.2_.282018-03-06.29 - Mercurial 4.5
See full changelog on
https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.5-rc_.282018-01-22.29
1. New Features
1.1. revert --interactive
The revert command now accepts the flag --interactive to allow reverting
only some of the changes to the specified files.
1.2. Accessing hidden changesets
Set config option `experimental.directaccess = True` to access hidden
changesets from read only commands.
1.3. githelp extension
The githelp extension provides the `hg githelp` command. This command
attempts to convert a git command to its Mercurial equivalent. The
extension can be useful to Git users new to Mercurial.
1.4. Largefiles changes
largefiles: add a 'debuglfput' command to put largefile into the store
largefiles: add support for 'largefiles://' url scheme
largefiles: allow to run 'debugupgraderepo' on repo with largefiles
largefiles: convert EOL of hgrc before appending to bytes IO
largefiles: explicitly set the source and sink types to 'hg' for lfconvert
largefiles: modernize how capabilities are added to the wire protocol
2. hgweb changes
hgweb now shows more information about commits: phase (if it's not public),
obsolescence status (with a short explanation and links to the successors)
and instabilities (e.g. orphan, phase-divergent or content-divergent).
Client-side graph code has been simplified by delegating more work to the
backend, so /graph page is now more in sync with /log page, visually and
feature-wise. Unfortunately, this code change means that 3rd-party themes
for 4.5+ are required to have graphentry.tmpl template available (copy it
from the base theme if you don't use %include and then reference it in map
file) and render entries in graph.tmpl -- look at one of the core themes to
see what it needs to look like. JS functions that create graph vertices and
edges are now available in Graph.prototype, making it possible to call the
original functions from custom theme-specific functions if needed.
Graph now shows different symbols for normal, branch-closing, obsolete and
unstable commits, and marks currently checked out commit with a circle
around its graph node.
There's also now json-graph API endpoint that can be used for rendering
commit graph in 3rd-party applications.
2.1. Other Changes
When interactive revert is run against a revision other than the working
directory parent, the diff shown is the diff to _apply_ to the working
directory, rather than the diff to _discard_ from the working copy. This is
in line with related user experiences with 'git' and appears to be less
confusing with 'ui.interface=curses'.
Let 'hg rebase' avoid content-divergence by skipping obsolete changesets
(and their descendants) when they are present in the rebase set along with
one of their successors but none of their successors is in destination.
A new experimental config flag, `rebase.experimental.inmemory`, makes
rebase perform an in-memory merge instead of doing it on-disk in the
working copy.
The `HGPLAINEXCEPT` environment variable can now include color to allow
automatic output colorization in otherwise automated environments.
A new `unamend` command in `uncommit` extension which undoes the effect of
the amend command by creating a new changeset which was there before amend
and moving the changes that were amended to the working directory.
A '--abort' flag to merge command to abort the ongoing merge.
An experimental flag '--rev' to 'hg branch' which can be used to change
branch of changesets.
bundle2 read I/O significantly improved
bundle2 memory use significantly reduced during read
clonebundle: it is now possible to serve the clonebundle using a git-lfs
compatible server.
templatefilters: add slashpath() to convert path separator to slash
(issue5572)
A new experimental config flag, 'inline-color-diff', adds within-line color
diff capacity
histedit: add support to output nodechanges using formatter to help with
editor integrations
3. Backwards Compatibility Changes
`log --follow-first -rREV`, which is deprecated, now follows the first
parent of merge revisions from the specified REV just like
`log --follow -rREV`.
`log --follow -rREV FILE..` now follows file history across copies and
renames.
transaction: register summary callbacks only at start of transaction
hgweb's graph view no longer supports browsers that lack