- Nov 15, 2024
-
-
Pierre-Yves David authored
We now have image to make that work.
-
- Nov 14, 2024
-
-
Pierre-Yves David authored
These can be installed on alpine… which is quite useful.
-
- Nov 15, 2024
-
-
Pierre-Yves David authored
This will make introduction of more variant simpler and testing quicker
-
Pierre-Yves David authored
It is currently broken.
-
Pierre-Yves David authored
The image should now have the proper config set globally to access this
-
Pierre-Yves David authored
We also make is a bit narrower so that it is less surprising.
-
- Nov 12, 2024
-
-
Pierre-Yves David authored
This reuse the script extracted in the previous changeset and now build the wheels with the same image and code as the CI.
-
- Sep 10, 2024
-
-
Pierre-Yves David authored
As discussed on the mailing list¹, these are old version that seems safe to drop. Python 3.8 comes with various improvement especially regarding typing capabilities. [1] https://lists.mercurial-scm.org/pipermail/mercurial-devel/2024-July/297998.html
-
- Jul 12, 2024
-
-
Anton Shestakov authored
-
- Dec 06, 2022
-
-
Matt Harbison authored
Otherwise, we get a bunch of test failures for missing things like pygments, or tests skipped entirely. The input file is a copy/paste from the equivalent Windows file, but with dulwich, pygit2, and pytest-vcr commented out because the build process errors out with them, flagging them as incompatible with loading from memory. I have no idea if that's actually true or not, because I've noticed that if I don't `make clean` after every build, the next build flags the watchman stuff as incompatible with loading from memory. The remaining failures are: Failed test-alias.t: output changed Failed test-basic.t: output changed Failed test-check-help.t: output changed Failed test-commit-interactive.t: output changed Failed test-extension.t: output changed Failed test-help.t: output changed Failed test-i18n.t: output changed Failed test-log.t: output changed Failed test-qrecord.t: output changed Failed test-share-safe.t: output changed Most of the issues seem related to loading help for disabled extensions from `hgext.__index__`, namely the full extension help being unavailable, not being able to resolve what commands are provided by what extension, and not having the command level help available. test-log.t, test-commit-interactive.t, and test-i18n.t look like i18n (or lack thereof) issues. test-basic.t is just odd: @@ -55,7 +55,7 @@ On Python 3, stdio may be None: $ hg debuguiprompt --config ui.interactive=true 0<&- - abort: Bad file descriptor (no-rhg !) + abort: response expected abort: response expected (rhg !) [255] $ hg version -q 0<&-
-
- Jan 02, 2023
-
-
Matt Harbison authored
-
- Nov 02, 2022
-
-
Jason R. Coombs authored
Also, add some documentation to the `.in` files.
-
- Sep 06, 2022
-
-
Matt Harbison authored
The presence of `certifi` causes the system certificate store to be ignored, which was reported as a bug against TortoiseHg[1]. It was only pulled in on Windows because of `dulwich`, which was copied from the old TortoiseHg install scripts, in order to support `hg-git`. This version of `dulwich` raises the minimum `urllib3` to a version (1.25) that does certificate verification by default, without the help of `certifi`[2]. We already bundle a newer version of `urllib3`. Note that `certifi` can still be imported from the user site directory, if installed there. But the installer no longer disables the system certificates by default. [1] mercurial/tortoisehg/thg#5825 [2] https://github.com/jelmer/dulwich/issues/1025
-
- Aug 08, 2022
-
-
Mathias De Mare authored
-
Mathias De Mare authored
-
- Jul 19, 2022
-
-
Matt Harbison authored
I'm told the new dulwich avoids hg-git test failures.
-
Matt Harbison authored
When challenged for a network password, this would spew on Windows before it actually used the stored password: ``` Error initializing plugin EntryPoint(name='libsecret', value='keyring.backends.libsecret', group='keyring.backends'). Traceback (most recent call last): File "keyring.backend", line 198, in _load_plugins init_func = ep.load() File "importlib.metadata", line 77, in load module = import_module(match.group('module')) File "importlib", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked ModuleNotFoundError: No module named 'keyring.backends.libsecret' Error initializing plugin EntryPoint(name='macOS', value='keyring.backends.macOS', group='keyring.backends'). Traceback (most recent call last): File "keyring.backend", line 198, in _load_plugins init_func = ep.load() File "importlib.metadata", line 77, in load module = import_module(match.group('module')) File "importlib", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1030, in _gcd_import File "<frozen importlib._bootstrap>", line 1007, in _find_and_load File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked ModuleNotFoundError: No module named 'keyring.backends.macOS' ``` We're kinda threading a needle here because the next version of `keyring` (currently at 23.7.0) requires `importlib-metadata` 3.6+, which PyOxidizer 0.22 doesn't support[1]. [1] https://github.com/indygreg/PyOxidizer/issues/609
-
- Jun 08, 2022
-
-
Mathias De Mare authored
-
- May 04, 2022
-
-
Matt Harbison authored
I noticed this when diffing the thg installer against Mercurial to see what was missing. There are a handful of other URLs in i18n and extension example help text if anyone cares to update those. Differential Revision: https://phab.mercurial-scm.org/D12606
-
- Apr 28, 2022
-
-
Matt Harbison authored
PyOxidizer binaries are built with py 3.9.6, so not even Windows 7 is supported. Unfortunately, there don't appear to be more recent values for newer versions of Windows, but at least Windows 8.1 is still in extended support for another 9 months or so. Differential Revision: https://phab.mercurial-scm.org/D12596
-
Matt Harbison authored
Differential Revision: https://phab.mercurial-scm.org/D12595
-
- Apr 18, 2022
-
-
Matt Harbison authored
Flagged by PyCharm. Differential Revision: https://phab.mercurial-scm.org/D12571
-
Matt Harbison authored
I also diffed these two files and eliminated cosmetic differences to make it easier to ensure both are in alignment. Differential Revision: https://phab.mercurial-scm.org/D12570
-
Matt Harbison authored
Differential Revision: https://phab.mercurial-scm.org/D12569
-
- Mar 25, 2022
-
-
Matthew Martin authored
Installs the bash and zsh completers to the convential locations so they will automatically be picked up without user intervention. The zsh completer on Debian is still installed to vendor-completions to match their policy. bash: https://github.com/scop/bash-completion#faq zsh: https://github.com/zsh-users/zsh/blob/57305cf245853b8b30895b41a90142dffab97e38/INSTALL#L254 Debian zsh: https://salsa.debian.org/debian/zsh/-/blob/5086b5356abcef8849dc8a09902b7c55f01db3c0/debian/README.Debian#L73
-
- Feb 20, 2022
-
-
Gregory Szorc authored
We just deleted support for Python 2 from the packaging code. We no longer need these package constraints in the requirements file to support Python 2. Differential Revision: https://phab.mercurial-scm.org/D12267
-
Gregory Szorc authored
This commit started by deleting references to py2exe (which is only used on Python 2). After pulling the thread, quite a lot of code was orphaned and was deleted. Differential Revision: https://phab.mercurial-scm.org/D12265
-
- Feb 16, 2022
-
-
Martin von Zweigbergk authored
-
- Feb 15, 2022
-
-
Raphaël Gomès authored
Differential Revision: https://phab.mercurial-scm.org/D12183
-
Mathias De Mare authored
Differential Revision: https://phab.mercurial-scm.org/D12182
-
- Feb 14, 2022
-
-
Mathias De Mare authored
Differential Revision: https://phab.mercurial-scm.org/D12172
-
- Nov 25, 2021
-
-
Matt Harbison authored
Differential Revision: https://phab.mercurial-scm.org/D11805
-
Matt Harbison authored
This is required for Python 3.10 support. Differential Revision: https://phab.mercurial-scm.org/D11804
-
Matt Harbison authored
Somewhere along the line, the formatting changed. There's no change in package content here- it's just some minor text changes. Py2 doesn't have any packages we'll be updating, so I'm not bothering there. Differential Revision: https://phab.mercurial-scm.org/D11803
-
- Nov 17, 2021
-
-
Mathias De Mare authored
This makes it possible to install multiple Mercurial rpms on the same machine in different locations. Differential Revision: https://phab.mercurial-scm.org/D11768
-
Mathias De Mare authored
Using uid 1000 and gid 1000 works by default in some cases, but 'id -u' and 'id -g' should work in all cases. Differential Revision: https://phab.mercurial-scm.org/D11767
-
- Oct 04, 2021
-
-
Matt Harbison authored
Not sure if this helps with recent certificate issues[1], but we might as well keep this modern. Note that certifi no longer claims py2 support, and there's a PR to add it back in[2]. Py2 support was dropped in 2020.04.05.2 (which predates what's being updated here). None of the *.py files have changed since the 2020.6.20 release, and I was able to call `certifi.where()` in both a virtualenv and with `hg debugshell` from an MSI install with this version, so we shouldn't be any worse off than before. [1] mercurial/tortoisehg/thg#5745 [2] https://github.com/certifi/python-certifi/pull/154 Differential Revision: https://phab.mercurial-scm.org/D11609
-
- Aug 27, 2021
-
-
Gregory Szorc authored
9438e9b7321a changed the name of the PyOxidizer target, which changed the name of the output directory. The code changed by this patch wasn't properly updated by that changeset. This resulted in a run-time failure due to trying to read from a non-existent directory. This change should fix the building of Python 3 Inno installers. Differential Revision: https://phab.mercurial-scm.org/D11356
-
- Aug 26, 2021
-
-
Gregory Szorc authored
Before, we would attempt to call a function (build_installer_py2exe) that didn't accept this keyword argument. This was preventing the building of py2exe installers. Differential Revision: https://phab.mercurial-scm.org/D11355
-
- Aug 18, 2021
-
-
Pierre-Yves David authored
This will lead to pyoxidizer including it in its binary. This fix test-phabricator.t Differential Revision: https://phab.mercurial-scm.org/D11301
-