[Bug 6877] New: baltimore child custody lawyer

2024-05-14 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6877

Bug ID: 6877
   Summary: baltimore child custody lawyer
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: keyword
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jdjackdaniels@gmail.com
CC: bcc@phloxic.productions,
mercurial-de...@mercurial-scm.org
Python Version: ---

In Baltimore, securing the services of a skilled child custody lawyer is vital
for families navigating custody disputes. These legal experts specialize in
Maryland family law, adeptly guiding clients through the complexities of the
legal process. Whether advocating through negotiation, mediation, or
litigation, they prioritize the best interests of the child while striving to
secure favorable custody arrangements and visitation schedules for their
clients. Baltimore-based child custody lawyers bring invaluable experience and
knowledge to help families achieve optimal outcomes in challenging custody
cases. https://childcustodylawyers.info/baltimore-child-custody-lawyer/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6876] New: Happy Eyeballs / more resilient connection establishment

2024-05-09 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6876

Bug ID: 6876
   Summary: Happy Eyeballs / more resilient connection
establishment
   Product: Mercurial
   Version: 6.3.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: z...@zash.se
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Problem: Sometimes the Internet is acting up and connectivity via IPv6 or IPv4
works better than the other or not at all.

In such cases following 'Happy Eyeballs', trying both and using whichever
connects first, would help reduce the time it takes to wait for a timeout when
doing a pull, push or otherwise interacting with the network.

See https://datatracker.ietf.org/doc/html/rfc8305

I did not see anything in changelogs for later versions that touched on this.

I expect connectivity over ssh would need to be improved in ssh rather than
Mercurial, so I expect this mostly concerns the http protocol.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6875] New: "unknown exception" using `hg split` or `hg commit --interactive`

2024-04-28 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6875

Bug ID: 6875
   Summary: "unknown exception" using `hg split` or `hg commit
--interactive`
   Product: Mercurial
   Version: 6.7.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: err...@raelity.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

This is on linux, working with a clone of a githug repo; probably developed on
windows.
Wondering if this could be a line ending issue.
To experiment, since `hg split` failed, tried `hg amend --extract; hg commit
-i`, same thing.

Entered command
```
$ hg split xscreen.cpp
```

`y` for the first hunk
then `e` for the second
```
record change 2/9 to 'xscreen.cpp'?
(enter ? for help) [Ynesfdaq?] e
```

When it brings up the editor, gvim, there is the message
```
"/tmp/hg-editor-xxx.diff" [CR missing][dos]53L, 1799B
File has 39 DOS-style endings out of 53 lines.
```

In the editor, there were only `+` lines. Deleted some of them,
wrote the file, exited the editor, crash.
```
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
** Mercurial Distributed SCM (version 6.7.2)
** Extensions loaded: convert, evolve 11.1.3, extdiff, fsmonitor, graphlog,
hggit 1.1.1 (dulwich 0.21.7), histedit, purge, rebase, share, topic 1.1.3,
transplant
Traceback (most recent call last):
  File "/home/err/.venv/bin/hg", line 59, in 
dispatch.run()
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 142, in run
status = dispatch(req)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 231, in dispatch
status = _rundispatch(req)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 275, in _rundispatch
ret = _runcatch(req) or 0
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 456, in _runcatch
return _callcatch(ui, _runcatchfunc)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 466, in _callcatch
return scmutil.callcatch(ui, func)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/scmutil.py",
line 152, in callcatch
return func()
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 446, in _runcatchfunc
return _dispatch(req)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1271, in _dispatch
return runcommand(
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 904, in runcommand
ret = _runcommand(ui, options, cmd, d)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1283, in _runcommand
return cmdfunc()
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1269, in 
d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/util.py", line
1878, in check
return func(*args, **kwargs)
  File
"/home/err/.venv/lib/python3.10/site-packages/hgext3rd/evolve/cmdrewrite.py",
line 1169, in cmdsplit
cmdutil.dorecord(ui, repo, commands.commit, b'commit',
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/cmdutil.py",
line 687, in dorecord
return commit(ui, repo, func, pats, opts)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/cmdutil.py",
line 2953, in commit
return commitfunc(ui, repo, message, matcher, opts)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/cmdutil.py",
line 527, in _record
chunks, newopts = filterfn(ui, original_headers, match)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/cmdutil.py",
line 435, in recordfilter
newchunks, newopts = filterchunks(
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/cmdutil.py",
line 421, in filterchunks
return patch.filterpatch(ui, originalhunks, match, operation)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/patch.py", line
1335, in filterpatch
applied[newhunk.filename()].append(newhunk)
KeyError: b'xscreen.cpp\r'
```

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6874] New: Attorney bankruptcies

2024-04-15 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6874

Bug ID: 6874
   Summary: Attorney bankruptcies
   Product: Mercurial
   Version: earlier
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bugzilla
  Assignee: bugzi...@mercurial-scm.org
  Reporter: johnsnow75...@gmail.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Take into account getting in touch with bankruptcy law specialists if you need
help filing for bankruptcy. You can look for local bankruptcy lawyers by using
internet law firm directories such as Avvo, FindLaw, or Justia. You might also
want to ask for recommendations or referrals from the local bar associations.
It can also be beneficial to ask friends, relatives, or coworkers who have
dealt with bankruptcy procedures for recommendations. In conclusion, you may
find more results by performing a web search with terms like "bankruptcy
attorney" and your location.

Visit site: https://srislawyer.com/attorney-bankruptcies/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6873] New: rhg crashes on Python 3.12: undefined symbol: _PyUnicode_Ready

2024-04-07 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6873

Bug ID: 6873
   Summary: rhg crashes on Python 3.12: undefined symbol:
_PyUnicode_Ready
   Product: Mercurial
   Version: 6.7.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: cedric.kr...@b2ck.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

When running `rhg status` (or any other command) with Python 3.12, I got this
traceback:

Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.12/hg", line 57, in 
from mercurial import dispatch
  File "/usr/lib/python3.12/site-packages/mercurial/dispatch.py", line 24, in

from . import (
  File "/usr/lib/python3.12/site-packages/mercurial/cmdutil.py", line 36, in

from . import (
  File "/usr/lib/python3.12/site-packages/mercurial/bookmarks.py", line 17, in

from . import (
  File "/usr/lib/python3.12/site-packages/mercurial/scmutil.py", line 27, in

from . import (
  File "/usr/lib/python3.12/site-packages/mercurial/copies.py", line 16, in

from . import (
  File "/usr/lib/python3.12/site-packages/mercurial/match.py", line 17, in

from . import (
  File "/usr/lib/python3.12/site-packages/mercurial/pathutil.py", line 23, in

rustdirs = policy.importrust('dirstate', 'Dirs')
   ^
  File "/usr/lib/python3.12/site-packages/mercurial/policy.py", line 138, in
importrust
mod = _importfrom('rustext', modname)
  ^^^
  File "/usr/lib/python3.12/site-packages/mercurial/policy.py", line 61, in
_importfrom
pkg = __import__(pkgname, globals(), fakelocals, [modname], level=1)
  ^^
ImportError:
/usr/lib/python3.12/site-packages/mercurial/rustext.cpython-312-x86_64-linux-gnu.so:
undefined symbol: _PyUnicode_Ready


Using the same installation but for Python 3.11 does not crash.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6872] New: Compression level option not making it to compressstream function of compression engine

2024-04-01 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6872

Bug ID: 6872
   Summary: Compression level option not making it to
compressstream function of compression engine
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bundle2
  Assignee: bugzi...@mercurial-scm.org
  Reporter: eric-mercur...@omnifarious.org
CC: mercurial-de...@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

I used this command:

hg bundle -a -t 'zstd;level=22' foo.mbdl

with data that I had explicitly formulated to compress very different with
different zstd compression levels. And I had tested that this was indeed the
case when using the zstd command line.

The resulting file was the right size for level 3, not level 22.

I went into utils/compression.py and stuck in a debugging print statement, and
the level that's being passed to _zstdengine.compressstream is 3. So, somewhere
between the command line parsing and the creation of the stream compressor, the
compression level is being lost.

It also appears that the 'revlog.zstd.level' option has no effect, possibly for
similar reasons.

This is the Python I used to create the file I checked in for testing purposes.
It's specifically designed to make sure that the compression ratio will change
at least very noticeably as the compression level being used goes up.

import itertools, random
pl = [''.join(p) for p in itertools.permutations([chr(65 + x) for x in
range(11)])]
sections = set()
while len(sections) < 3500:
sections.add(random.randint(0, 480924 * 83))
sectstrs = ['\n'.join(pl[x:x+83]) for x in sections]
with open('permutes.txt', 'w') as pf:
for _ in range(19):
random.shuffle(sectstrs)
pf.write('\n'.join(sectstrs) + '\n')

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6871] New: Some commands that accept Bookmarks do not resolve . (dot) to current Bookmark

2024-03-28 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6871

Bug ID: 6871
   Summary: Some commands that accept Bookmarks do not resolve .
(dot) to current Bookmark
   Product: Mercurial
   Version: 6.5.1
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: nils.reib...@aldente-it.de
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

For example it is not possible to use
hg log -B .
in order to see the history of the current Bookmark. Instead it reports that
there is no Bookmark named "."

hg push -B .
Resolves to the active Bookmark correctly

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6869] New: Command '['hg', 'clone', 'https://foss.heptapod.net/tryton/tryton']' returned non-zero exit status 1.

2024-03-17 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6869

Bug ID: 6869
   Summary: Command '['hg', 'clone',
'https://foss.heptapod.net/tryton/tryton']' returned
non-zero exit status 1.
   Product: Mercurial
   Version: 6.7
  Hardware: Other
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: nio772...@yahoo.it
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

I I get an error whit the command

cookiecutter hg+https://code.tryton.org/tryton --directory cookiecutter-module

Result:

adding changesets
adding manifests
adding file changes
transaction abort!
rollback completed
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.8.10 (default, Nov 22 2023, 10:22:35) [GCC 9.4.0]
** Mercurial Distributed SCM (version 6.7)
** Extensions loaded: 
Traceback (most recent call last):
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/bin/hg", line
59, in 
dispatch.run()
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/dispatch.py",
line 142, in run
status = dispatch(req)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/dispatch.py",
line 231, in dispatch
status = _rundispatch(req)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/dispatch.py",
line 275, in _rundispatch
ret = _runcatch(req) or 0
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/dispatch.py",
line 456, in _runcatch
return _callcatch(ui, _runcatchfunc)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/dispatch.py",
line 466, in _callcatch
return scmutil.callcatch(ui, func)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/scmutil.py",
line 152, in callcatch
return func()
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/dispatch.py",
line 446, in _runcatchfunc
return _dispatch(req)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/dispatch.py",
line 1271, in _dispatch
return runcommand(
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/dispatch.py",
line 904, in runcommand
ret = _runcommand(ui, options, cmd, d)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/dispatch.py",
line 1283, in _runcommand
return cmdfunc()
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/dispatch.py",
line 1269, in 
d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/util.py",
line 1878, in check
return func(*args, **kwargs)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/commands.py",
line 2033, in clone
r = hg.clone(
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/hg.py",
line 1016, in clone
exchange.pull(
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/exchange.py",
line 1709, in pull
_maybeapplyclonebundle(pullop)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/exchange.py",
line 2837, in _maybeapplyclonebundle
if trypullbundlefromurl(repo.ui, repo, url, remote):
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/exchange.py",
line 2879, in trypullbundlefromurl
bundle2.applybundle(repo, cg, tr, b'clonebundles', url)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/bundle2.py",
line 383, in applybundle
return processbundle(
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/bundle2.py",
line 508, in processbundle
processparts(repo, op, unbundler)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/bundle2.py",
line 516, in processparts
_processpart(op, part)
  File
"/home/trytond/projects/docker-tryton-off-7/custom_modules/.venv/lib/python3.8/site-packages/mercurial/bundle2.py",
line 594, in _processpart

[Bug 6868] New: Mercurial cloning fails on a very large monolithic repository

2024-03-11 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6868

Bug ID: 6868
   Summary: Mercurial cloning fails on a very large monolithic
repository
   Product: Mercurial
   Version: 6.5
  Hardware: All
OS: Other
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: tripivc...@hotmail.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

hg clone, as well as hg clone -U on a very large, monolithic repository
comprising mixture source code and of binary files, fails with the following
output:

added 2130 changesets with 234347 changes to 190759 files
new changesets af1464ce40d3:6d39b030b280
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.11.4 (main, Sep 10 2023, 11:09:06) [C]
** Mercurial Distributed SCM (version 6.5)
** Extensions loaded: churn, histedit, pager, purge, relink, schemes
Traceback (most recent call last):
  File "/opt/rtp/bin/hg", line 59, in 
dispatch.run()
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line 143,
in run
status = dispatch(req)
 ^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line 232,
in dispatch
status = _rundispatch(req)
 ^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line 276,
in _rundispatch
ret = _runcatch(req) or 0
  ^^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line 457,
in _runcatch
return _callcatch(ui, _runcatchfunc)
   ^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line 467,
in _callcatch
return scmutil.callcatch(ui, func)
   ^^^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/scmutil.py", line 153,
in callcatch
return func()
   ^^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line 447,
in _runcatchfunc
return _dispatch(req)
   ^^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line
1272, in _dispatch
return runcommand(
   ^^^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line 905,
in runcommand
ret = _runcommand(ui, options, cmd, d)
  
  File "/opt/rtp/lib/python3.11/site-packages/hgext/pager.py", line 77, in
pagecmd
return orig(ui, options, cmd, cmdfunc)
   ^^^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line
1284, in _runcommand
return cmdfunc()
   ^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line
1270, in 
d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/util.py", line 1881, in
check
return func(*args, **kwargs)
   ^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/commands.py", line
1992, in clone
r = hg.clone(
^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/hg.py", line 1125, in
clone
destrepo.updatecaches(caches=repositorymod.CACHES_POST_CLONE)
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/localrepo.py", line
244, in wrapper
return orig(repo.unfiltered(), *args, **kwargs)
   
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/localrepo.py", line
2939, in updatecaches
for entry in self.store.walk():
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/store.py", line 883, in
walk
for x in self.data_entries(matcher):
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/store.py", line 1162,
in data_entries
entry = RevlogStoreEntry(
^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/store.py", line 561, in
__init__
assert b'.i' in details, (path_prefix, details)
   
AssertionError:
(b'data/pkgprotos/RTPCoracle/RTPoracle/i386/opt/rtp/oracle/product/10.2.0/db_1/ctx/data/delx',
{b'-s/drowdD.dat': ret = _runcommand(ui, options, cmd, d)
  
  File "/opt/rtp/lib/python3.11/site-packages/hgext/pager.py", line 77, in
pagecmd
return orig(ui, options, cmd, cmdfunc)
   ^^^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line
1284, in _runcommand
return cmdfunc()
   ^
  File "/opt/rtp/lib/python3.11/site-packages/mercurial/dispatch.py", line
1270, in 
d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)

[Bug 6867] New: test-generaldelta.t failure on s390x (6.7rc0)

2024-03-05 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6867

Bug ID: 6867
   Summary: test-generaldelta.t failure on s390x (6.7rc0)
   Product: Mercurial
   Version: 6.7rc0
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jcris...@debian.org
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

From
https://buildd.debian.org/status/fetch.php?pkg=mercurial=s390x=6.7%7Erc0-1=1709629359=0

--- /<>/tests/test-generaldelta.t
+++ /<>/tests/test-generaldelta.t.err
@@ -271,7 +271,7 @@
51  17  -1   43   50prev3??   
5??6??   1.0   6?? 00.0 (glob)
52  51  -1   44   51  p1 58   
6406??   1.0   6?? 00.0 (glob)
53  52  -1   51   -1base  0
 0  0   0.0 0 00.0
-   54  53  -1   52   53  p13??   
6403??   0.5   3?? 00.0 (glob)
+   54  53  -1   52   53  p1385   
640385   0.60156   385 00.0
   $ hg clone --pull source-repo --config experimental.maxdeltachainspan=2800
relax-chain --config format.generaldelta=yes
   requesting all changes
   adding changesets

ERROR: test-generaldelta.t output changed

Possibly from https://repo.mercurial-scm.org/hg/rev/7083b33a2699?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6866] New: Mercurial crashes when attempting to push to remote repository

2024-02-27 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6866

Bug ID: 6866
   Summary: Mercurial crashes when attempting to push to remote
repository
   Product: Mercurial
   Version: 6.6.3
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: rob...@birddogsw.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Originally seen in 6.5.1. Upgraded to 6.6.3 and the problem persists.

hg push --new-branch http://{remote server}
pushing to http://{remote server}
searching for changes
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64
bit (AMD64)]
** Mercurial Distributed SCM (version 6.6.3)
** Extensions loaded: evolve 11.1.1, rebase, share
Traceback (most recent call last):
  File "hg", line 58, in 
  File "mercurial\dispatch.pyc", line 142, in run
  File "mercurial\dispatch.pyc", line 231, in dispatch
  File "mercurial\dispatch.pyc", line 275, in _rundispatch
  File "mercurial\dispatch.pyc", line 456, in _runcatch
  File "mercurial\dispatch.pyc", line 466, in _callcatch
  File "mercurial\scmutil.pyc", line 152, in callcatch
  File "mercurial\dispatch.pyc", line 446, in _runcatchfunc
  File "mercurial\dispatch.pyc", line 1271, in _dispatch
  File "mercurial\dispatch.pyc", line 904, in runcommand
  File "mercurial\dispatch.pyc", line 1283, in _runcommand
  File "mercurial\dispatch.pyc", line 1269, in 
  File "mercurial\util.pyc", line 1878, in check
  File "mercurial\commands.pyc", line 5866, in push
  File "hgext3rd\evolve\__init__.pyc", line 581, in push
  File "mercurial\exchange.pyc", line 501, in push
  File "mercurial\exchange.pyc", line 1168, in _pushbundle2
  File "mercurial\exchange.pyc", line 901, in _pushb2ctx
  File "mercurial\exchange.pyc", line 784, in _pushcheckoutgoing
  File "mercurial\discovery.pyc", line 377, in checkheads
  File "mercurial\discovery.pyc", line 270, in _headssummary
KeyError: b'{branch name}'

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6864] New: checknewlabel: integer special case not coarse enough

2024-02-05 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6864

Bug ID: 6864
   Summary: checknewlabel: integer special case not coarse enough
   Product: Mercurial
   Version: stable branch
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: georges.raci...@octobus.net
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Seen in scmutil.checknewlabel on current stable (e7be2ddfb4c2), and is the same
in current default:


try:
int(lbl)
if b'_' in lbl:
# If label contains underscores, Python might consider it an
# integer (with "_" as visual separators), but we do not.
# See PEP 515 - Underscores in Numeric Literals.
raise ValueError
raise error.InputError(_(b"cannot use an integer as a name"))
except ValueError:
pass


If I understand correctly, this forbids decimal integers as labels, unless they
were parsed ok by Python because it ignores underscores, as we want `12_34` to
be a valid label.

The problem is that it is not the only valid integer literal not made of only
decimal digits. For instance "+12" and "-4" would be.
Whether Mercurial should allow them in bookmark and topic names is debatable,
but the intended rule (integer that Mercurial would not consider an integer)
does not seem to be exactly the one implemented.

Also this "we do not" is not a specification. I guess it would mean something
like "revsets would not" or just "repo[lbl] would not", with the actual intent
probably being that it cannot be a revision number. Given that revision numbers
are 32-bit signed (with only a few negative ones for special meanings) this
also raises the question whether 12121212121212121212121212121 should be a
valid label or not.

Context: I am currently implementing the same rules in Heptapod (Ruby side)
https://foss.heptapod.net/heptapod/heptapod/-/issues/1350

There is no urgency: in the first version, due tomorrow, I will of course
simply forbid strings made only of decimal digits. But I feel this should be
tightened and not depend on a programming langage rule for literals.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6863] New: hg uncommit -i does not work when editing patches.

2024-01-31 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6863

Bug ID: 6863
   Summary: hg uncommit -i does not work when editing patches.
   Product: Mercurial
   Version: 6.4.3
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: sebunge...@gmail.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Created attachment 2166
  --> https://bz.mercurial-scm.org/attachment.cgi?id=2166=edit
Script to demonstrate the bug

Hi,

I just found my self needing to `hg uncommit -i` some stuff and in one hunk
there was only part of the patch I wanted to uncommit and that did not work.

No matter how one edits the patch it always fails to apply.

I'll attach a script that will hopefully make what I mean clear. Please note
that that script will silently delete and recreate /tmp/UncommitProblemDemo !!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6862] New: ProgrammingError: cannot call command branches: method of same name not available on peer

2024-01-22 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6862

Bug ID: 6862
   Summary: ProgrammingError: cannot call command branches: method
of same name not available on peer
   Product: Mercurial
   Version: 6.6.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: err...@raelity.com
CC: mercurial-de...@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

** Unknown exception encountered with possibly-broken third-party extension
"evolve" 11.1.0
** ProgrammingError: cannot call command branches: method of same name not
available on peer

$ hg --version -v
Mercurial Distributed SCM (version 6.6.2)
  evolve  external  11.1.0
  extdiff internal  
  fsmonitor   internal  
  graphloginternal  
  hggit   external  1.1.0 (dulwich 0.21.7)
  histeditinternal  
  purge   internal  
  rebase  internal  
  share   internal  
  topic   external  1.1.0
  transplant  internal  

 hg out
comparing with git+ssh://g...@github.com:bpangburn/swingset.git
searching for changes
** Unknown exception encountered with possibly-broken third-party extension
"evolve" 11.1.0
** which supports versions 6.5 of Mercurial.
** Please disable "evolve" and try your action again.
** If that fixes the bug please report it to https://bz.mercurial-scm.org/
** Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
** Mercurial Distributed SCM (version 6.6.2)
** Extensions loaded: convert, evolve 11.1.0, extdiff, fsmonitor, graphlog,
hggit 1.1.0 (dulwich 0.21.7), histedit, purge, rebase, share, topic 1.1.0,
transplant
** ProgrammingError: cannot call command branches: method of same name not
available on peer
Traceback (most recent call last):
  File "/home/err/.venv/bin/hg", line 59, in 
dispatch.run()
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 142, in run
status = dispatch(req)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 231, in dispatch
status = _rundispatch(req)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 275, in _rundispatch
ret = _runcatch(req) or 0
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 456, in _runcatch
return _callcatch(ui, _runcatchfunc)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 466, in _callcatch
return scmutil.callcatch(ui, func)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/scmutil.py",
line 152, in callcatch
return func()
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 446, in _runcatchfunc
return _dispatch(req)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1271, in _dispatch
return runcommand(
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 904, in runcommand
ret = _runcommand(ui, options, cmd, d)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1283, in _runcommand
return cmdfunc()
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1269, in 
d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/util.py", line
1878, in check
return func(*args, **kwargs)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/util.py", line
1878, in check
return func(*args, **kwargs)
  File
"/home/err/.venv/lib/python3.10/site-packages/hgext3rd/topic/__init__.py", line
1620, in pushoutgoingwrap
return orig(ui, repo, *args, **opts)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/util.py", line
1878, in check
return func(*args, **kwargs)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/commands.py",
line 5081, in outgoing
return hg.outgoing(ui, repo, dests, opts)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/hg.py", line
1503, in outgoing
o, others = _outgoing(ui, repo, dests, opts, subpath=subpath)
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/hg.py", line
1449, in _outgoing
outgoing = discovery.findcommonoutgoing(
  File "/home/err/.venv/lib/python3.10/site-packages/hggit/gitrepo.py", line
166, in findcommonoutgoing
commoninc = discovery.findcommonincoming(
  File "/home/err/.venv/lib/python3.10/site-packages/mercurial/discovery.py",
line 54, in findcommonincoming
return treediscovery.findcommonincoming(repo, remote, heads, force)
  File
"/home/err/.venv/lib/python3.10/site-packages/mercurial/treediscovery.py", line
82, in findcommonincoming
branches = e.callcommand(b'branches', {b'nodes': unknown}).result()
  File 

[Bug 6861] New: Purge will abort if a directory junction does not point to a valid directory

2023-12-21 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6861

Bug ID: 6861
   Summary: Purge will abort if a directory junction does not
point to a valid directory
   Product: Mercurial
   Version: 6.5.1
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: david.a.holl...@carrier.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

What I had expected is that a junction would be removed whether or not it
points to a valid directory or not, assuming it contains no tracked files.

While its true the junction is not "valid" in some sense, I'm not sure why hg
purge should *abort* as a result. A warning message (if anything) would seem to
be sufficient. 

While this can be cleaned up manually, it breaks certain automated use cases.

I'm curious if Linux behavior would be the same (assuming an equivalent
scenario is possible, I can't really recall the nuances there).


Below is a series of steps to reproduce the issue:

D:\source>mkdir test

D:\source>cd test

D:\source\test>hg init

D:\source\test>mkdir ..\target

D:\source\test>mklink /j linked ..\target
Junction created for linked <<===>> ..\target

D:\source\test>rmdir ..\target

D:\source\test>hg purge
linked: The system cannot find the path specified
abort: The system cannot find the path specified: 'D:\source\test/linked'

D:\source\test>hg --version
Mercurial Distributed SCM (version 6.5.1)


This was running on Windows 10 but I've seen in on Win7 also.

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6860] New: bug in revset optimization involving null commit

2023-12-20 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6860

Bug ID: 6860
   Summary: bug in revset optimization involving null commit
   Product: Mercurial
   Version: default branch
  Hardware: PC
OS: Mac OS
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: martinv...@google.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

I haven't even tried to figure out where in the revset optimization this bug
lies, but here's a test that demonstrates it:

```
  $ hg init
  $ echo a > file
  $ hg ci -Am foo
  adding file
  $ hg co -q null
  $ hg debugrevspec --no-optimized  '(parents(only(., public())) | .) &
public()'
  -1
  $ hg debugrevspec  '(parents(only(., public())) | .) & public()'
  -1 (missing-correct-output !)
```

The unoptimized output is correct, the optimized output is not.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6859] New: histedit broken with ncurses patchlevel 20231111

2023-12-12 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6859

Bug ID: 6859
   Summary: histedit broken with ncurses patchlevel 2023
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: histedit
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jcris...@debian.org
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

>From https://bugs.debian.org/1058041:

Since a ncurses upgrade in testing recently `hg histedit` seems to
crash consistently, upon trying to apply the changes:

> Traceback (most recent call last):
>   File "/usr/bin/hg", line 59, in 
> dispatch.run()
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 142, in 
> run
> status = dispatch(req)
>  ^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 231, in 
> dispatch
> status = _rundispatch(req)
>  ^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 275, in 
> _rundispatch
> ret = _runcatch(req) or 0
>   ^^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 456, in 
> _runcatch
> return _callcatch(ui, _runcatchfunc)
>^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 466, in 
> _callcatch
> return scmutil.callcatch(ui, func)
>^^^
>   File "/usr/lib/python3/dist-packages/mercurial/scmutil.py", line 152, in 
> callcatch
> return func()
>^^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 446, in 
> _runcatchfunc
> return _dispatch(req)
>^^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1271, in 
> _dispatch
> return runcommand(
>^^^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 904, in 
> runcommand
> ret = _runcommand(ui, options, cmd, d)
>   
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1283, in 
> _runcommand
> return cmdfunc()
>^
>   File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1269, in 
> 
> d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
> ^
>   File "/usr/lib/python3/dist-packages/mercurial/util.py", line 1878, in check
> return func(*args, **kwargs)
>^
>   File "/usr/lib/python3/dist-packages/hgext/histedit.py", line 1918, in 
> histedit
> return _chistedit(ui, repo, freeargs, opts)
>
>   File "/usr/lib/python3/dist-packages/hgext/histedit.py", line 1764, in 
> _chistedit
> curses.endwin()
> _curses.error: endwin() returned ERR

Debian's ncurses package maintainer says:

> > I am not familiar with Mercurial, but most likely this has been
> > triggered by the following change in the 2023111 patchlevel:
> >
> > ,
> > | 2023
> > |   + modify endwin() to return an error if it is called again without an
> > | intervening screen update (report by Rajeev Pillai, NetBSD #57592).
> > `

> I now had a look at the histedit code, and it does this:

> ,
> | with util.with_lc_ctype():
> | rc = curses.wrapper(functools.partial(_chisteditmain, repo, 
> rules))
> | curses.echo()
> | curses.endwin()
> `

> AFAICS, invoking curses.echo() and curses.endwin() is superfluous
> because curses.wrapper already does that for you, and calling
> curses.endwin() twice throws an error with the newer ncurses.  Removing

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6858] New: test-censor.t test failure

2023-12-10 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6858

Bug ID: 6858
   Summary: test-censor.t test failure
   Product: Mercurial
   Version: 6.6.1
  Hardware: All
OS: NetBSD
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: t...@giga.or.at
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

There is a new test failure in 6.6.1 on NetBSD:

--- /scratch/devel/py-mercurial/work/mercurial-6.6.1/tests/test-censor.t
+++
/scratch/devel/py-mercurial/work/mercurial-6.6.1/tests/test-censor.t#revlogv1.err
 
@@ -301,6 +301,7 @@ 
   8 ??? no  file  target (glob) (revlogv2 !)   
   8 ??? yes file  target (glob) (revlogv1 !)   
   $ cat /dev/rand?m | dd status=none count=200 | f --hexdump > target  
+  dd: unknown operand status   
   $ hg ci -m 'add 100k passwords'  
   $ H2=`hg id --debug -i`  
   $ C5=$H2 
@@ -309,7 +310,7 @@ 
   $ H2=`hg id --debug -i`  
   $ hg debugrevlogstats | grep target  
   rev-count   data-size inl type  target   
- 10  ?? no  file  target (glob)
+ 10 185 yes file  target   
   $ hg --config extensions.censor= censor -r $C5 target

 The important part is for the censor operation to not crash and the repository
@@ -317,7 +318,7 @@ 

   $ hg debugrevlogstats | grep target
   rev-count   data-size inl type  target 
- 10 ??? no  file  target (glob)
+ 10 199 yes file  target
   $ hg cat -r $C5 target | head -n 10
   $ hg cat -r $H2 target | head -n 10
   fresh start

ERROR: test-censor.t#revlogv1 output changed

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6857] New: hg rollback randomly has no effect,

2023-12-07 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6857

Bug ID: 6857
   Summary: hg rollback randomly has no effect,
   Product: Mercurial
   Version: 6.5.3
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: php4...@gmail.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Unfortunately I don't know how to reproduce this at will.
This just happened to me for no apparent reason.
I tried reproducing at will but couldn't.

What I did was:
- in a repository where there were no uncommitted changes, I made some changes
- I committed with 'hg commit -m "bla bla bla"' (note: i did NOT push)
- I made some more changes
- I ran the command: "hg rollback"

I got this strange output, which makes no sense whatsoever to me:
```
repository tip rolled back to revision 351 (undo push-response)
```

Normally when I do rollback I get this:
```
repository tip rolled back to revision 351 (undo commit)
```

After that, the repository was NOT rolled back. The last commit was still
there. hg status and hg diff would still show only changes I had made after the
last commit, as if I hadn't rolled back.

Basically, the rollback command had no effect whatsoever.

I tried running "hg rollback" again. This time I got the message:
```
no rollback information available
```

which would be expected if the rollback had had effect.

I could not roll back in any way, I had to keep the commit and move on.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6855] New: Copy information is lost on fold

2023-11-30 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6855

Bug ID: 6855
   Summary: Copy information is lost on fold
   Product: Mercurial
   Version: 6.5.2
  Hardware: PC
OS: Mac OS
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jar...@jaraco.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

When using fold, the copy information is lost:

```
 draft @ hg init changeset-copies; cd changeset-copies
 changeset-copies default @ touch foo
 changeset-copies default @ hg commit -A -m "Adding foo"
adding foo
 changeset-copies default @ hg mv foo bar
 changeset-copies default @ hg commit -m "Renaming foo to bar"
 changeset-copies default @ hg status --change .
A bar
  foo
R foo
 changeset-copies default @ touch baz
 changeset-copies default @ hg commit -A -m "Adding baz"
adding baz
 changeset-copies default @ hg fold --from .^1 -m "folded"
2 changesets folded
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
 changeset-copies default @ hg status --change .
A bar
A baz
R foo
```

Instead users expect the copy information to be retained:

```
A bar
  foo
A baz
R foo
```

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6854] New: crush report: on incoming

2023-11-25 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6854

Bug ID: 6854
   Summary: crush report: on incoming
   Product: Mercurial
   Version: 6.6rc0
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: alexraynepe...@gmail.com
CC: mercurial-de...@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

hallow!
here is my try 'incoming' evolve with mercurial 6.6 and evolve 11.1.0

```
% hg incoming --quiet --bundle
"C:\Users\netuser\AppData\Local\Temp\thg.cn25p30n\ssh__hg@foss.heptapod.net_mercurial_evolve_j2f4bfdq.hg"
--force --debug ssh://h...@foss.heptapod.net/mercurial/evolve
running C:\util\TortoisePlink.exe -ssh -2 "h...@foss.heptapod.net" "hg -R
mercurial/evolve serve --stdio"
sending hello command
sending between command
remote: 610
remote: capabilities: _evoext_getbundle_obscommon _evoext_obshashrange_v1
_exttopics_heads batch branchmap
bundle2=HG20%0Abookmarks%0Achangegroup%3D01%2C02%2C03%0Acheckheads%3Drelated%0Adigests%3Dmd5%2Csha1%2Csha512%0Aerror%3Dabort%2Cunsupportedcontent%2Cpushraced%2Cpushkey%0Aext-configexpress%0Ahgtagsfnodes%0Alistkeys%0Aobsmarkers%3DV0%2CV1%0Aphases%3Dheads%0Apushkey%0Aremote-changegroup%3Dhttp%2Chttps%0Astream%3Dv2
changegroupsubset ext-topics-publish=auto getbundle known lookup protocaps
pushkey streamreqs=generaldelta,revlogv1,sparserevlog topics topics-namespaces
unbundle=HG10GZ,HG10BZ,HG10UN unbundlehash
remote: 1
sending protocaps command
сравниваем с ssh://h...@foss.heptapod.net/mercurial/evolve
obscache is out of date
query 1; heads
sending batch command
поиск изменений
taking initial sample
query 2; still undecided: 8, sample size is: 8
sending known command
2 total queries in 0.3322s
sending getbundle command
bundle2-input-part: total payload size 245733
bundle2-input-part: total payload size 1160
preparing listkeys for "phases"
sending listkeys command
received listkey for "phases": 53534 bytes
obsolete feature not enabled but 33237 markers found!
obscache is out of date
changeset:   6821:017fd6b302eb4d31138dc002408db032c401e9f8
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.8.3 (tags/v3.8.3:6f8c832, May 13 2020, 22:37:02) [MSC v.1924 64 bit
(AMD64)]
** Распределенная система контроля версий Mercurial (версия 6.5.3)
** Загруженные расширения: absorb, amend, censor, convert, eol, evolve
11.1.1.dev0, fix, histedit, mq, narrow, patchbomb, rebase, record, share,
sparse, strip, topic 1.1.1.dev0, tortoisehg.util.hgcommands
6.5.1+16-191a6f1e65e7, tortoisehg.util.hgdispatch 6.5.1+16-191a6f1e65e7,
tortoisehg.util.partialcommit 6.5.1+16-191a6f1e65e7, tortoisehg.util.pipeui
6.5.1+16-191a6f1e65e7, tortoisehg.util.win32ill 6.5.1+16-191a6f1e65e7,
transplant
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.8.3 (tags/v3.8.3:6f8c832, May 13 2020, 22:37:02) [MSC v.1924 64 bit
(AMD64)]
** Распределенная система контроля версий Mercurial (версия 6.5.3)
** Загруженные расширения: absorb, amend, censor, convert, eol, evolve
11.1.1.dev0, fix, histedit, mq, narrow, patchbomb, rebase, record, share,
sparse, strip, topic 1.1.1.dev0, tortoisehg.util.hgcommands
6.5.1+16-191a6f1e65e7, tortoisehg.util.hgdispatch 6.5.1+16-191a6f1e65e7,
tortoisehg.util.partialcommit 6.5.1+16-191a6f1e65e7, tortoisehg.util.pipeui
6.5.1+16-191a6f1e65e7, tortoisehg.util.win32ill 6.5.1+16-191a6f1e65e7,
transplant
Traceback (most recent call last):
  File "D:\projects\hg\thg\thg.work\venv.py38\Scripts\hg", line 59, in 
dispatch.run()
  File
"D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\dispatch.py",
line 143, in run
status = dispatch(req)
  File
"D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\dispatch.py",
line 232, in dispatch
status = _rundispatch(req)
  File
"D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\dispatch.py",
line 276, in _rundispatch
ret = _runcatch(req) or 0
  File
"D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\dispatch.py",
line 457, in _runcatch
return _callcatch(ui, _runcatchfunc)
  File
"D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\dispatch.py",
line 467, in _callcatch
return scmutil.callcatch(ui, func)
  File
"D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\scmutil.py",
line 153, in callcatch
return func()
  File
"D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\dispatch.py",
line 447, in _runcatchfunc
return _dispatch(req)
  File
"D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\dispatch.py",
line 1272, in _dispatch
return runcommand(
  File

[Bug 6853] New: cannot call command tns_heads: method of same name not available on peer when pulling with chg

2023-11-22 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6853

Bug ID: 6853
   Summary: cannot call command tns_heads: method of same name not
available on peer when pulling with chg
   Product: Mercurial
   Version: 6.6rc0
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: p...@philpep.org
CC: mercurial-de...@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

Hi,

I just upgraded my servers to mercurial 6.6 and hg-evolve 11.1.0.

Both server and client config have evolve and topic enabled:

[extensions]
evolve =
topic =

(I changed evolve.serveronly to evolve as documented on the server in evolve
changelog).

I pull a repo using ssh and chg and get traceback bellow (on client side, no
related errors on server side). I noticed that:

* disabling topic extension on client side doesn't trigger the bug
* using python hg instead of chg on client side doesn't trigger the bug

Thanks!


** Unknown exception encountered with possibly-broken third-party extension
"evolve" 11.1.0
** which supports versions 6.5 of Mercurial.
** Please disable "evolve" and try your action again.
** If that fixes the bug please report it to https://bz.mercurial-scm.org/
** Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
** Mercurial Distributed SCM (version 6.6)
** Extensions loaded: absorb, evolve 11.1.0, histedit, pager, patchbomb,
phabricator, purge, rebase, record, schemes, show, strip, topic 1.1.0
** ProgrammingError: cannot call command tns_heads: method of same name not
available on peer
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mercurial/commandserver.py", line 490,
in _serverequest
sv.serve()
  File "/usr/lib/python3/dist-packages/mercurial/commandserver.py", line 394,
in serve
while self.serveone():
  ^^^
  File "/usr/lib/python3/dist-packages/mercurial/commandserver.py", line 368,
in serveone
handler(self)
  File "/usr/lib/python3/dist-packages/mercurial/chgserver.py", line 570, in
runcommand
return super(chgcmdserver, self).runcommand()
   ^^
  File "/usr/lib/python3/dist-packages/mercurial/commandserver.py", line 349,
in runcommand
ret = self._dispatchcommand(req) & 255
  ^^
  File "/usr/lib/python3/dist-packages/mercurial/commandserver.py", line 288,
in _dispatchcommand
return dispatch.dispatch(req)
   ^^
  File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 231, in
dispatch
status = _rundispatch(req)
 ^
  File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 275, in
_rundispatch
ret = _runcatch(req) or 0
  ^^
  File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 456, in
_runcatch
return _callcatch(ui, _runcatchfunc)
   ^
  File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 466, in
_callcatch
return scmutil.callcatch(ui, func)
   ^^^
  File "/usr/lib/python3/dist-packages/mercurial/scmutil.py", line 152, in
callcatch
return func()
   ^^
  File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 446, in
_runcatchfunc
return _dispatch(req)
   ^^
  File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1271, in
_dispatch
return runcommand(
   ^^^
  File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 904, in
runcommand
ret = _runcommand(ui, options, cmd, d)
  
  File "/usr/lib/python3/dist-packages/hgext/pager.py", line 77, in pagecmd
return orig(ui, options, cmd, cmdfunc)
   ^^^
  File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1283, in
_runcommand
return cmdfunc()
   ^
  File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1269, in

d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
^
  File "/usr/lib/python3/dist-packages/mercurial/util.py", line 1878, in check
return func(*args, **kwargs)
   ^
  File "/usr/lib/python3/dist-packages/mercurial/util.py", line 1878, in check
return func(*args, **kwargs)
   ^
  File "/usr/lib/python3/dist-packages/hgext3rd/evolve/__init__.py", line 565,
in wrapmayobsoletewc
res = origfn(ui, repo, *args, **opts)
  ^^^
  File "/usr/lib/python3/dist-packages/mercurial/util.py", line 1878, in check
return func(*args, **kwargs)
   

[Bug 6851] New: hg pull raises TypeError

2023-11-14 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6851

Bug ID: 6851
   Summary: hg pull raises TypeError
   Product: Mercurial
   Version: 6.5rc0
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: friedric...@gmx.de
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Since 6.4.1+hg70.3a2df812e1c7 I get the following traceback while

% hg pull
pulling from https://www.mercurial-scm.org/repo/hg
real URL is https://repo.mercurial-scm.org/hg
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0]
** Mercurial Distributed SCM (version 6.4.1+hg70.3a2df812e1c7)
** Extensions loaded: absorb, evolve 11.1.0, fix, graphlog, hggit 1.0.2
(dulwich 0.20.50), histedit, rebase, show, topic 1.1.0
Traceback (most recent call last):
  File "/home/friedrich/.local/bin/hg", line 59, in 
dispatch.run()
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 143, in run
status = dispatch(req)
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 232, in dispatch
status = _rundispatch(req)
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 276, in _rundispatch
ret = _runcatch(req) or 0
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 451, in _runcatch
return _callcatch(ui, _runcatchfunc)
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 461, in _callcatch
return scmutil.callcatch(ui, func)
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/scmutil.py",
line 153, in callcatch
return func()
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 441, in _runcatchfunc
return _dispatch(req)
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1266, in _dispatch
return runcommand(
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 899, in runcommand
ret = _runcommand(ui, options, cmd, d)
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1278, in _runcommand
return cmdfunc()
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1264, in 
d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
  File "/home/friedrich/.local/lib/python3.10/site-packages/mercurial/util.py",
line 1881, in check
return func(*args, **kwargs)
  File "/home/friedrich/.local/lib/python3.10/site-packages/mercurial/util.py",
line 1881, in check
return func(*args, **kwargs)
  File
"/home/friedrich/.local/lib/python3.10/site-packages/hgext3rd/evolve/__init__.py",
line 565, in wrapmayobsoletewc
res = origfn(ui, repo, *args, **opts)
  File "/home/friedrich/.local/lib/python3.10/site-packages/mercurial/util.py",
line 1881, in check
return func(*args, **kwargs)
  File "/home/friedrich/.local/lib/python3.10/site-packages/mercurial/util.py",
line 1881, in check
return func(*args, **kwargs)
  File "/home/friedrich/.local/lib/python3.10/site-packages/hgext/rebase.py",
line 2188, in pullrebase
ret = orig(ui, repo, *args, **opts)
  File "/home/friedrich/.local/lib/python3.10/site-packages/mercurial/util.py",
line 1881, in check
return func(*args, **kwargs)
  File
"/home/friedrich/.local/lib/python3.10/site-packages/mercurial/commands.py",
line 5477, in pull
revs, checkout = hg.addbranchrevs(
TypeError: safebranchrevs() got an unexpected keyword argument 'remotehidden'


Is this a known bug?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6850] New: rust: cpython crate is unmaintained and doesn't work with Python 3.12 - switch to pyo3

2023-11-12 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6850

Bug ID: 6850
   Summary: rust: cpython crate is unmaintained and doesn't work
with Python 3.12 - switch to pyo3
   Product: Mercurial
   Version: stable branch
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: m...@kiilerich.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Summarizing https://bugzilla.redhat.com/show_bug.cgi?id=2249383 :

The "cpython" crate is now officially unmaintained [0], and it does not support
Python 3.12 [1].

c.f.
https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/XG7GMDZFL2RO4QHEFBJKU7YDE3AZBRVM/#XG7GMDZFL2RO4QHEFBJKU7YDE3AZBRVM

The upstream author of the "cpython" crate recommends to migrate to pyo3.
Versions 0.19.2 and newer of pyo3 support Python 3.12.

[0]: https://github.com/dgrunwald/rust-cpython/commit/e81
[1]: https://github.com/dgrunwald/rust-cpython/issues/294

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6849] New: error running hgweb.wsgi: TypeError: write() argument 1 must be read-only bytes-like object, not memoryview

2023-10-31 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6849

Bug ID: 6849
   Summary: error running hgweb.wsgi: TypeError: write() argument
1 must be read-only bytes-like object, not memoryview
   Product: Mercurial
   Version: 6.5.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: hgweb
  Assignee: bugzi...@mercurial-scm.org
  Reporter: djer...@cfa.harvard.edu
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Created attachment 2162
  --> https://bz.mercurial-scm.org/attachment.cgi?id=2162=edit
hgweb.wsgi configuration file

I’m using mercurial 6.5.2,running hgweb.wsgi under Apache/2.4.37, with system
python 3.6.8 on RHEL8.

I’m using the web interface to view a number of mercurial repos in the same
directory (see the hgweb.config at the end of this email).

The web interface to the the list of repositories comes up fine, and if I click
on any of the individual repos, their repo is displayed properly.

However, if I click on one of the column names to sort it (e.g. by “Last
Modified”), and then subsequently clicking on a repo in the now-sorted page to
view the repo, the server returns a 500 reply, and hgweb.wsgi tosses out a

TypeError: write() argument 1 must be read-only bytes-like object, not
memoryview, referer

I've attached the stack trace, as well as the hgweb.wsgi and hgweb.config
files.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6848] New: hg incoming: unknown exception encountered

2023-10-25 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6848

Bug ID: 6848
   Summary: hg incoming:  unknown exception encountered
   Product: Mercurial
   Version: 6.5.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: richard.p...@free.fr
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

On Arch (well, EndeavourOS), 
> Linux 6.5.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 19 Oct 2023 22:52:14 + 
> x86_64 unknown unknown GNU/Linux

after updating to Mercurial 6.5.2, I can no longer do an `hg incoming' on
[some] mercurial repositories.

In particular the repository indicated below:

$ hg inc
comparaison avec https://foss.heptapod.net/tryton/tryton/
searching for changes
changeset:   96805:17b0d04b3258
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.11.5 (main, Sep  2 2023, 14:16:33) [GCC 13.2.1 20230801]
** Mercurial version 6.5.2, système de gestion de sources distribué
** Extensions chargées : absorb, evolve 11.1.0, graphlog, hgk, highlight,
histedit, rebase, show, topic 1.1.0
Traceback (most recent call last):
  File "/usr/sbin/hg", line 59, in 
dispatch.run()
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 143, in
run
status = dispatch(req)
 ^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 232, in
dispatch
status = _rundispatch(req)
 ^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 276, in
_rundispatch
ret = _runcatch(req) or 0
  ^^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 457, in
_runcatch
return _callcatch(ui, _runcatchfunc)
   ^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 467, in
_callcatch
return scmutil.callcatch(ui, func)
   ^^^
  File "/usr/lib/python3.11/site-packages/mercurial/scmutil.py", line 153, in
callcatch
return func()
   ^^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 447, in
_runcatchfunc
return _dispatch(req)
   ^^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 1272, in
_dispatch
return runcommand(
   ^^^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 905, in
runcommand
ret = _runcommand(ui, options, cmd, d)
  
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 1284, in
_runcommand
return cmdfunc()
   ^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 1270, in

d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
^
  File "/usr/lib/python3.11/site-packages/mercurial/util.py", line 1881, in
check
return func(*args, **kwargs)
   ^
  File "/usr/lib/python3.11/site-packages/mercurial/commands.py", line 4426, in
incoming
return hg.incoming(ui, repo, source, opts)
   ^^^
  File "/usr/lib/python3.11/site-packages/mercurial/hg.py", line 1419, in
incoming
return _incoming(
   ^^
  File "/usr/lib/python3.11/site-packages/mercurial/hg.py", line 1385, in
_incoming
displaychlist(other, chlist, displayer)
  File "/usr/lib/python3.11/site-packages/mercurial/hg.py", line 1417, in
display
displayer.show(other[n])
  File "/usr/lib/python3.11/site-packages/mercurial/logcmdutil.py", line 304,
in show
self._show(ctx, copies, props)
  File "/usr/lib/python3.11/site-packages/mercurial/logcmdutil.py", line 337,
in _show
for name in ns.names(self.repo, changenode):
^^^
  File "/usr/lib/python3.11/site-packages/mercurial/namespaces.py", line 220,
in names
return sorted(self.nodemap(repo, node))
  
  File "/usr/lib/python3.11/site-packages/mercurial/namespaces.py", line 49, in

tagnodemap = lambda repo, node: repo.nodetags(node)
^^^
  File "/usr/lib/python3.11/site-packages/mercurial/localrepo.py", line 2219,
in nodetags
if not self._tagscache.nodetagscache:
   ^^^
  File "/usr/lib/python3.11/site-packages/mercurial/util.py", line 1760, in
__get__
result = self.func(obj)
 ^^
  File "/usr/lib/python3.11/site-packages/mercurial/localrepo.py", line 2140,
in _tagscache
cache.tags, cache.tagtypes = self._findtags()
 
  File 

[Bug 6847] New: wow gold

2023-10-16 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6847

Bug ID: 6847
   Summary: wow gold
   Product: Mercurial
   Version: earlier
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: bookmarks
  Assignee: bugzi...@mercurial-scm.org
  Reporter: hulingqing0...@outlook.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Dear immortals, I need some [url=http://www.wowtot.com/]wow gold[/url]
inspiration to create.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6846] New: hg serve with lsprof enabled throws exceptions on cpython 3.12

2023-10-11 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6846

Bug ID: 6846
   Summary: hg serve with lsprof enabled throws exceptions on
cpython 3.12
   Product: Mercurial
   Version: stable branch
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: hgweb
  Assignee: bugzi...@mercurial-scm.org
  Reporter: coral.p...@disr.it
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Due to changes in python 3.12 in _lsprof module
(https://github.com/python/cpython/issues/103533) multiple profiling contexts
no longer work - at least that's what I think.

The first profiler starts in mercurial.dispatch on start up, and the second one
fails to start in mercurial.hgweb on WSGI request, which crashes request
handling. Removing profiling contexts in mercurial.hgweb makes error go away.

This also causes test-profile.t to fail.

To reproduce:

> hg init
> hg serve --profile --config profiling.type=ls &
listening at http://127.0.0.1:8000/ (bound to *:8000)
> hg clone 'http://127.0.0.1:8000'
127.0.0.1 - - [11/Oct/2023 18:37:08] Exception happened during processing
request '/?cmd=capabilities':
Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/mercurial/hgweb/server.py", line 123,
in do_POST
self.do_write()
  File "/usr/lib/python3.12/site-packages/mercurial/hgweb/server.py", line 117,
in do_write
self.do_hgweb()
  File "/usr/lib/python3.12/site-packages/mercurial/hgweb/server.py", line 232,
in do_hgweb
for chunk in self.server.application(env, self._start_response):
  File "/usr/lib/python3.12/site-packages/mercurial/hgweb/hgweb_mod.py", line
364, in run_wsgi
with profiling.profile(repo.ui, enabled=profile):
  File "/usr/lib/python3.12/site-packages/mercurial/profiling.py", line 197, in
__enter__
self.start()
  File "/usr/lib/python3.12/site-packages/mercurial/profiling.py", line 262, in
start
self._profiler.__enter__()
  File "/usr/lib/python3.12/contextlib.py", line 137, in __enter__
return next(self.gen)
   ^^
  File "/usr/lib/python3.12/site-packages/mercurial/profiling.py", line 58, in
lsprofile
p.enable(subcalls=True)
ValueError: Another profiling tool is already active

127.0.0.1 - - [11/Oct/2023 18:37:08] "GET /?cmd=capabilities HTTP/1.1" 500 -
abort: HTTP Error 500: Internal Server Error

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6845] New: streaming clonebundle publishes draft changesets

2023-10-10 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6845

Bug ID: 6845
   Summary: streaming clonebundle publishes draft changesets
   Product: Mercurial
   Version: stable branch
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: clonebundles
  Assignee: bugzi...@mercurial-scm.org
  Reporter: mathias.dem...@gmail.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

I see it on 6.5.1, but it's also on stable (and I expect on default as well).

Running on the mercurial-devel repository itself:
./hg bundle --all --type "none-streamv2;obsolescence=true;phases=true"
foo.bundle
./hg init someclone
./hg -R someclone unbundle foo.bundle
./hg -R someclone log -G #<-- everything became public

Digging a bit further in the code, I see 'unbundlepart' instances being called.
In order:
1. streamv2
2. obsmarkers
3. phase-heads

The phase-heads unbundlepart tries to call 'phases.updatephases', but in
'advanceboundary', the filter for revs that can have their phase changed, comes
up empty: revs = [rev for rev in revs if self.phase(repo, rev) >= phase]

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6844] New: stable-range cache: skipping write, database drifted under my feet

2023-09-28 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6844

Bug ID: 6844
   Summary: stable-range cache: skipping write, database drifted
under my feet
   Product: Mercurial
   Version: 6.3.1
  Hardware: Other
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: zeger.van_de_van...@nokia.com
CC: mercurial-de...@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

When pulling from a repo (mirror server) which was pulling at that time I got
the following error:

---
remote: stable-range cache: skipping write, database drifted under my feet
remote: (disk: ac8d1535db673f2462a59b31d9931fd2e0b6b9ad-22370 vs mem:
167b64c54fecd6d5fffa0f305850429a9684b815-22367)
remote: abort: 00changelog@ac8d1535db673f2462a59b31d9931fd2e0b6b9ad: filtered
node
abort: stream ended unexpectedly (got 0 bytes, expected 4)
---


I had just pushed from my workspace (WS1) to our central server (Central).
This push triggers a pull on our local read-only mirror (Mirror), from which I
immediately tried to pull in my other workspace (WS2).

So: 

WS1 --push--> Central --pull--> Mirror --pull--> WS2

I was pushing a rather large set of commits (~500) and the Central server was
experiencing some heavy load which caused it to respond sluggishly.

I understood that these updates should be atomically and this error should not
occur.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6843] New: test-remotefilelog-gc.t: embedded null character in path

2023-08-26 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6843

Bug ID: 6843
   Summary: test-remotefilelog-gc.t: embedded null character in
path
   Product: Mercurial
   Version: 6.5.1
  Hardware: All
OS: NetBSD
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: t...@giga.or.at
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

In 6.5.1 with Python 3.11.5 on NetBSD there is a new test failure:

---
/scratch/devel/py-mercurial/work/mercurial-6.5.1/tests/test-remotefilelog-gc.t
+++
/scratch/devel/py-mercurial/work/mercurial-6.5.1/tests/test-remotefilelog-gc.t.err
@@ -108,7 +108,8 @@
   $ printf "asdas\0das" >> $CACHEDIR/repos
 #if py311
   $ hg gc
-  finished: removed 0 of 4 files (0.00 GB to 0.00 GB)
+  abort: invalid path asdas\x00da: stat: embedded null character in path (esc)
+  [255]
 #else
   $ hg gc
   abort: invalid path asdas\x00da: .*(null|NULL).* (re)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6842] New: Is JetBlue Safe

2023-08-25 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6842

Bug ID: 6842
   Summary: Is JetBlue Safe
   Product: Mercurial project
   Version: unspecified
  Hardware: PC
   URL: https://travelraval.com/blog/is-jetblue-safe-to-fly/
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: website
  Assignee: bugzi...@mercurial-scm.org
  Reporter: nancyrgalindonan...@gmail.com
CC: mercurial-de...@mercurial-scm.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6841] New: draft topic changeset already in server not found in discovery branch info with topic has trailing //

2023-08-22 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6841

Bug ID: 6841
   Summary: draft topic changeset already in server not found in
discovery branch info with topic has trailing //
   Product: Mercurial
   Version: unspecified
  Hardware: All
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: melutov...@gmail.com
CC: mercurial-de...@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

I have a draft changeset on a topic that exists in my real repo on the server,
accessible by a draft repo using server.view=visible a repo share of the real
repo; I pulled that into a local repo, when I attempt to push to the public
share repo of the real server (server.view=immutable).
=I get an error on the push
summary of the error:
File "/usr/local/lib64/python2.7/site-packages/mercurial/discovery.py", line
279, in _headssummary
headssum[branch][1][:] = newheads
'prod_10200//topicName123//'

fuller details

hg outgoing
comparing with ssh://h...@xyz.com/joined/public
searching for changes
changeset:   27507:c71732efd61a
branch:  prod_10200
tag: tip
topic:   topicName123
parent:  27393:260655a366ec
user:Mitchell Elutovich 
date:Mon Aug 07 13:05:54 2023 +0100
summary: ABC123

pushing to ssh://h...@hg.xyz.com/joined/public
searching for changes
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 2.7.5 (default, Jun 28 2022, 15:30:04) [GCC 4.8.5 20150623 (Red Hat
4.8.5-44)]
** Mercurial Distributed SCM (version 5.6.1)
** Extensions loaded: share, keyword, extdiff, transplant, convert, graphlog,
purge, strip, mq, rebase, hggit, evolve, topic
Traceback (most recent call last):
  File "/usr/local/bin/hg", line 43, in 
dispatch.run()
  File "/usr/local/lib64/python2.7/site-packages/mercurial/dispatch.py", line
113, in run
status = dispatch(req)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/dispatch.py", line
303, in dispatch
ret = _runcatch(req) or 0
  File "/usr/local/lib64/python2.7/site-packages/mercurial/dispatch.py", line
479, in _runcatch
return _callcatch(ui, _runcatchfunc)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/dispatch.py", line
488, in _callcatch
return scmutil.callcatch(ui, func)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/scmutil.py", line
153, in callcatch
return func()
  File "/usr/local/lib64/python2.7/site-packages/mercurial/dispatch.py", line
469, in _runcatchfunc
return _dispatch(req)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/dispatch.py", line
1233, in _dispatch
lui, repo, cmd, fullargs, ui, options, d, cmdpats, cmdoptions
  File "/usr/local/lib64/python2.7/site-packages/mercurial/dispatch.py", line
917, in runcommand
ret = _runcommand(ui, options, cmd, d)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/dispatch.py", line
1244, in _runcommand
return cmdfunc()
  File "/usr/local/lib64/python2.7/site-packages/mercurial/dispatch.py", line
1230, in 
d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/util.py", line 1867,
in check
  File "/usr/local/lib64/python2.7/site-packages/mercurial/util.py", line 1867,
in check
return func(*args, **kwargs)
  File "/usr/local/lib64/python2.7/site-packages/hgext/mq.py", line 4222, in
mqcommand
return orig(ui, repo, *args, **kwargs)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/util.py", line 1867,
in check
return func(*args, **kwargs)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/util.py", line 1867,
in check
return func(*args, **kwargs)
  File "/home/melutovich/pkgs/evolve/hgext3rd/topic/__init__.py", line 1465, in
pushoutgoingwrap
return orig(ui, repo, *args, **opts)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/util.py", line 1867,
in check
return func(*args, **kwargs)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/util.py", line 1867,
in check
return func(*args, **kwargs)
  File "/home/melutovich/pkgs/evolve/hgext3rd/topic/flow.py", line 94, in
wrappush
return orig(repo, remote, *args, **newargs)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/util.py", line 1867,
in check
return func(*args, **kwargs)
  File "/usr/local/lib64/python2.7/site-packages/mercurial/commands.py", line
5540, in push
opargs=opargs,
  File "/home/melutovich/pkgs/evolve/hgext3rd/evolve/__init__.py", line 579, in
push
return orig(repo, *args, **opts)
  File "/home/melutovich/pkgs/hg-git/hggit/util.py", line 63, in inner
return f(*args, **kwargs)
  File "/home/melutovich/pkgs/hg-git/hggit/__init__.py", line 596, in
exchangepush

[Bug 6840] New: hg import a file fails for encoding

2023-08-19 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6840

Bug ID: 6840
   Summary: hg import a file fails for encoding
   Product: Mercurial
   Version: 6.5.1
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: cedric.kr...@b2ck.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Here is the traceback:

$ hg import --no-commit /tmp/patch  
applying /tmp/patch 
** unknown exception encountered, please report by visiting 
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.11.4 (main, Jun 24 2023, 08:36:23) [GCC 12.2.1 20230428]
** Mercurial Distributed SCM (version 6.5.1)
** Extensions loaded: absorb, churn, convert, evolve 11.0.2, histedit, rebase,
relink, share, topic 1.0.2  
Traceback (most recent call last):  
  File "/usr/lib/python3.11/site-packages/mercurial/commandserver.py", line
491, in _serverequest   
sv.serve()  
  File "/usr/lib/python3.11/site-packages/mercurial/commandserver.py", line
395, in serve   
while self.serveone():  
  ^^^   
  File "/usr/lib/python3.11/site-packages/mercurial/commandserver.py", line
369, in serveone
handler(self)   
  File "/usr/lib/python3.11/site-packages/mercurial/chgserver.py", line 574, in
runcommand  
return super(chgcmdserver, self).runcommand()
   ^^
  File "/usr/lib/python3.11/site-packages/mercurial/commandserver.py", line
350, in runcommand
ret = self._dispatchcommand(req) & 255
  ^^
  File "/usr/lib/python3.11/site-packages/mercurial/commandserver.py", line
289, in _dispatchcommand
return dispatch.dispatch(req)
   ^^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 232, in
dispatch
status = _rundispatch(req)
 ^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 276, in
_rundispatch
ret = _runcatch(req) or 0
  ^^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 457, in
_runcatch
return _callcatch(ui, _runcatchfunc)
   ^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 467, in
_callcatch
return scmutil.callcatch(ui, func)
   ^^^
  File "/usr/lib/python3.11/site-packages/mercurial/scmutil.py", line 153, in
callcatch
return func()
   ^^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 447, in
_runcatchfunc
return _dispatch(req)
   ^^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 1272, in
_dispatch
return runcommand(
   ^^^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 905, in
runcommand
ret = _runcommand(ui, options, cmd, d)
  
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 1284, in
_runcommand
return cmdfunc()
   ^
  File "/usr/lib/python3.11/site-packages/mercurial/dispatch.py", line 1270, in

d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
^
  File "/usr/lib/python3.11/site-packages/mercurial/util.py", line 1881, in
check
return func(*args, **kwargs)
   ^
  File "/usr/lib/python3.11/site-packages/mercurial/commands.py", line 4275, in
import_
with patch.extract(ui, hunk) as patchdata:
  File "/usr/lib/python3.11/contextlib.py", line 137, in __enter__
return next(self.gen)
   ^^
  File "/usr/lib/python3.11/site-packages/mercurial/patch.py", line 225, in
extract
yield _extract(ui, fileobj, tmpname, tmpfp)
  ^
  File "/usr/lib/python3.11/site-packages/mercurial/patch.py", line 252, in
_extract
b'\n'.join(
  File "/usr/lib/python3.11/site-packages/mercurial/patch.py", line 253, in

b': 

[Bug 6839] New: hg debugssl throws unknown exception - TypeError: coercing to Unicode: need string or buffer, NoneType found

2023-08-09 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6839

Bug ID: 6839
   Summary: hg debugssl throws unknown exception - TypeError:
coercing to Unicode: need string or buffer, NoneType
found
   Product: Mercurial
   Version: 2.7.1
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: hglib
  Assignee: bugzi...@mercurial-scm.org
  Reporter: robert.str...@nccgroup.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Hello,

Mercurial wasn't recognising the SSL certificate for my repository, which was
issued by my organisation's root CA, so I installed the root CA on my Windows
machine.

When I tried to do an "hg pull" from the server, Mercurial issued the following
warning:

% hg pull
pulling from https://hg.xxx.com
(the full certificate chain may not be available locally; see "hg help
debugssl")
URLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
(_ssl.c:727)

I ran "hg debugs" and got the following exception:

[...]
  File "mercurial\debugcommands.pyo", line 3788, in debugssl
  File "ssl.pyo", line 864, in connect
  File "ssl.pyo", line 851, in _real_connect
  File "socket.pyo", line 228, in meth
TypeError: coercing to Unicode: need string or buffer, NoneType found
cmdserver: process exited unexpectedly with code 255

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6838] New: Some tests are failing on PPC

2023-08-05 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6838

Bug ID: 6838
   Summary: Some tests are failing on PPC
   Product: Mercurial
   Version: unspecified
  Hardware: Other
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: cedric.kr...@b2ck.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

I got this bug report from the testing machine on Gentoo:
https://bugs.gentoo.org/843431

Most of the failure seems to be linked to wait_file of testing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6837] New: Logos gone

2023-07-25 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6837

Bug ID: 6837
   Summary: Logos gone
   Product: Mercurial project
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: wiki
  Assignee: bugzi...@mercurial-scm.org
  Reporter: chea...@gmail.com
CC: mercurial-de...@mercurial-scm.org

The wiki is supposed to display a logo in the header to the left of the word
"Mercurial", but it does not show currently because the URL requested
(https://www.mercurial-scm.org/logo-droplets-50.png ) yields a 404.

By the way, for a presumably related reason, the image supposed to display
first on the homepage is also broken (only its URL displays):
https://wiki.mercurial-scm.org/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6836] New: push does not allow simulation

2023-07-25 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6836

Bug ID: 6836
   Summary: push does not allow simulation
   Product: Mercurial
   Version: 6.4.2
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: chea...@gmail.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

hg push can be used to export a subset of local changesets thanks to its --rev
option. hg push --rev foo may export more than foo, but there is unfortunately
no way of simulating what hg push will do to determine which changesets it
would export without actually exporting them.

Adding something like a --simulate option would let users preview how push
behave and use it confidently.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6835] New: cp: use POSIX -R instead of -r

2023-07-19 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6835

Bug ID: 6835
   Summary: cp: use POSIX -R instead of -r
   Product: Mercurial
   Version: 6.5
  Hardware: All
OS: NetBSD
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: t...@giga.or.at
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

NetBSD's copy supports the 'old' -r flag but doesn't like it:

This makes tests/test-bundle-phase-internal.t fail:

   $ cp -ar reference-repo strip-ancestor
+  cp: the -R and -r options may not be specified together.
+  [1]
   $ cd strip-ancestor  
+  cd: can't cd to strip-ancestor  


Please use 'cp -aR' instead to follow POSIX. Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6834] New: provide search capability in interactive commit

2023-07-16 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6834

Bug ID: 6834
   Summary: provide search capability in interactive commit
   Product: Mercurial
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: djer...@cfa.harvard.edu
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

What:

Provide text searches on the changes in interactive commit 

Why:

To quickly identify the changes which involve a particular string that I know
is associated to those changes.


When I've accumulated too many changes and wish to provide an easy to
understand commit history, interactive commit is useful, but it can be
difficult to identify pertinent changes if there are a large number of changes.

The ability to filter or navigate the changes using a text search would be
quite helpful.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6833] New: Im not able to clone the mercurial repository.

2023-06-30 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6833

Bug ID: 6833
   Summary: Im not able to clone the mercurial repository.
   Product: Mercurial
   Version: 6.4.2
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: acl
  Assignee: bugzi...@mercurial-scm.org
  Reporter: madhura.ravin...@nuware.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Getting below error

% hg clone --verbose http://localhost:80/hg/repo1 "D:\repo1"
http authorization required for http://localhost:80/hg/repo1
realm: mercurial repo
 real URL is http://localhost/hg/repo1/
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64
bit (AMD64)]
** Mercurial Distributed SCM (version 6.4.2)
** Extensions loaded: strip, tortoisehg.util.hgcommands 6.4.2,
tortoisehg.util.hgdispatch 6.4.2, tortoisehg.util.partialcommit 6.4.2,
tortoisehg.util.pipeui 6.4.2, tortoisehg.util.win32ill 6.4.2
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64
bit (AMD64)]
** Mercurial Distributed SCM (version 6.4.2)
** Extensions loaded: strip, tortoisehg.util.hgcommands 6.4.2,
tortoisehg.util.hgdispatch 6.4.2, tortoisehg.util.partialcommit 6.4.2,
tortoisehg.util.pipeui 6.4.2, tortoisehg.util.win32ill 6.4.2
Traceback (most recent call last):
  File "mercurial\httppeer.pyc", line 631, in make_peer
  File "mercurial\httppeer.pyc", line 615, in makepeer
  File "mercurial\httppeer.pyc", line 570, in performhandshake
  File "mercurial\httppeer.pyc", line 350, in parsev1commandresponse
mercurial.error.RepoError: b'\'http://localhost:80/hg/repo1\' does not appear
to be an hg repository:\n---%<--- (text/html;charset=UTF-8)\n\n\n \n  Index of
/hg/repo1\n \n \nIndex of /hg/repo1\n Parent Directory\n
.hg/\n .hgignore\n .htaccess\n
odysseyteam.csv\n\n\n\n---%<---\n'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "hg", line 58, in 
  File "mercurial\dispatch.pyc", line 143, in run
  File "mercurial\dispatch.pyc", line 232, in dispatch
  File "mercurial\dispatch.pyc", line 276, in _rundispatch
  File "mercurial\dispatch.pyc", line 451, in _runcatch
  File "mercurial\dispatch.pyc", line 461, in _callcatch
  File "mercurial\scmutil.pyc", line 153, in callcatch
  File "mercurial\dispatch.pyc", line 441, in _runcatchfunc
  File "mercurial\dispatch.pyc", line 1266, in _dispatch
  File "mercurial\dispatch.pyc", line 899, in runcommand
  File "mercurial\dispatch.pyc", line 1278, in _runcommand
  File "mercurial\dispatch.pyc", line 1264, in 
  File "mercurial\util.pyc", line 1881, in check
  File "mercurial\commands.pyc", line 6655, in serve
  File "mercurial\server.pyc", line 166, in runservice
  File "mercurial\commandserver.pyc", line 461, in run
  File "mercurial\commandserver.pyc", line 395, in serve
  File "mercurial\commandserver.pyc", line 369, in serveone
  File "mercurial\commandserver.pyc", line 350, in runcommand
  File "mercurial\commandserver.pyc", line 289, in _dispatchcommand
  File "mercurial\dispatch.pyc", line 232, in dispatch
  File "mercurial\dispatch.pyc", line 276, in _rundispatch
  File "mercurial\dispatch.pyc", line 451, in _runcatch
  File "mercurial\dispatch.pyc", line 461, in _callcatch
  File "mercurial\scmutil.pyc", line 153, in callcatch
  File "mercurial\dispatch.pyc", line 441, in _runcatchfunc
  File "tortoisehg\util\hgdispatch.pyc", line 27, in _dispatch
  File "mercurial\dispatch.pyc", line 1266, in _dispatch
  File "mercurial\dispatch.pyc", line 899, in runcommand
  File "mercurial\dispatch.pyc", line 1278, in _runcommand
  File "mercurial\dispatch.pyc", line 1264, in 
  File "mercurial\util.pyc", line 1881, in check
  File "mercurial\commands.pyc", line 1982, in clone
  File "mercurial\hg.pyc", line 718, in clone
  File "mercurial\hg.pyc", line 257, in peer
  File "mercurial\httppeer.pyc", line 636, in make_peer
  File "mercurial\statichttprepo.pyc", line 266, in make_peer
AttributeError: 'bytes' object has no attribute 'loc'
cmdserver: process exited unexpectedly with code 255

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6832] New: Looping redirect on pipermail

2023-06-29 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6832

Bug ID: 6832
   Summary: Looping redirect on pipermail
   Product: Mercurial project
   Version: unspecified
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: website
  Assignee: bugzi...@mercurial-scm.org
  Reporter: m...@kiilerich.com
CC: mercurial-de...@mercurial-scm.org

For example https://www.mercurial-scm.org/pipermail/mercurial-devel/ (mentioned
on https://wiki.mercurial-scm.org/MailingLists ) redirects to
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-mercurial-devel

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6831] New: clonebundles autogenerate fails with commandline parameters

2023-06-28 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6831

Bug ID: 6831
   Summary: clonebundles autogenerate fails with commandline
parameters
   Product: Mercurial
   Version: 6.5rc0
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: clonebundles
  Assignee: bugzi...@mercurial-scm.org
  Reporter: mathias.dem...@gmail.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

$  hg clone ... -U --config extensions.clonebundles= --config
clone-bundles.auto-generate.on-change=yes --config clone
-bundles.auto-generate.serve-inline=yes --config
clone-bundles.auto-generate.formats=v2 --config devel.debug.clonebundles=yes
requesting all changes
adding changesets
adding manifests
adding file changes
added 19041 changesets with 39835 changes to 9834 files
27799 new obsolescence markers
new changesets ...
clone-bundles: starting bundle generation: bzip2-v2
hg: unknown command 'debug::internal-make-clone-bundles'
(did you mean one of debugapplystreamclonebundle,
debugcreatestreamclonebundle?)


Looks like commandline parameters are not passed along properly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6830] New: hg commands should not work when in a git (or any other CVS-DVCS) subrepo

2023-06-26 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6830

Bug ID: 6830
   Summary: hg commands should not work when in a git (or any
other CVS-DVCS) subrepo
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: axel.p...@xcg-consulting.fr
CC: mercurial-de...@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

lets say i have two projects working together. 
project A is my main project, versioned with hg. 
inside project A, i have a dependencies/ direcetory containing project B,
versioned in git. 
when i am at root and run hg log, i have the log from project A. 
then i run cd dependencies/projectB. here, when i do hg log, it still show me
the logs for project A, since B is not a hg project but a git one. 

Proposed - evolution : when working with subrepos of other DVCS, hg can detect
the .git and not run his commands when in a git subrepo. my optimal evolution
would be an error msg (hg can not run inside a git repo, and maybe some
contextual infos on where the actual hg repo is compared to where i am. 

It would make working with multi DVCS projects less a pain. i would get lost
less. 

Thanks you for your feedback, cant wait for the next Hg meetup 

axel prel

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6828] New: Latest release missing GPG signature

2023-06-24 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6828

Bug ID: 6828
   Summary: Latest release missing GPG signature
   Product: Mercurial
   Version: 6.4.5
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: packaging
  Assignee: bugzi...@mercurial-scm.org
  Reporter: ca...@alerque.com
CC: duri...@gmail.com, mercurial-de...@mercurial-scm.org
Python Version: ---

The `.asc` file with a GPG signature historically found on all releases from
this project is missing from 6.4.5. This is holding up the release on Arch
Linux and possibly other distros that verify chain of trust for projects that
typically publish such artifacts.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6827] New: test-convert-svn-branches.t failures

2023-06-24 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6827

Bug ID: 6827
   Summary: test-convert-svn-branches.t failures
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: convert
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jcris...@debian.org
CC: duri...@gmail.com, mercurial-de...@mercurial-scm.org
Python Version: ---

with mercurial 6.4.4, subversion 1.14.2:

---
/tmp/autopkgtest-lxc.ta8ymcwu/downtmp/build.EHY/src/tests/test-convert-svn-branches.t
+++
/tmp/autopkgtest-lxc.ta8ymcwu/downtmp/build.EHY/src/tests/test-convert-svn-branches.t.err
@@ -39,8 +39,8 @@
   9 644ede6c-2b81-4367-9dc8-d786514f2cde/branches/old@9
   8 644ede6c-2b81-4367-9dc8-d786514f2cde/branches/old2@8
   7 644ede6c-2b81-4367-9dc8-d786514f2cde/branches/old@7
-  6 644ede6c-2b81-4367-9dc8-d786514f2cde/trunk@6
-  5 644ede6c-2b81-4367-9dc8-d786514f2cde/branches/old@6
+  6 644ede6c-2b81-4367-9dc8-d786514f2cde/branches/old@6
+  5 644ede6c-2b81-4367-9dc8-d786514f2cde/trunk@6
   4 644ede6c-2b81-4367-9dc8-d786514f2cde/branches/old@5
   3 644ede6c-2b81-4367-9dc8-d786514f2cde/trunk@4
   2 644ede6c-2b81-4367-9dc8-d786514f2cde/branches/old@3
@@ -67,9 +67,9 @@
   | | |
   | | o  branch=old 7 change b again files: b
   | | |
-  | o |  branch= 6 move and update c files: b
+  | | o  branch=old 6 move and update c files: c
   | | |
-  | | o  branch=old 5 move and update c files: c
+  | o |  branch= 5 move and update c files: b
   | | |
   | | o  branch=old 4 change b files: b
   | | |

ERROR: test-convert-svn-branches.t output changed

E.g.
https://ci.debian.net/data/autopkgtest/testing/amd64/m/mercurial/34485168/log.gz

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6826] New: Show topics in hgweb

2023-06-23 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6826

Bug ID: 6826
   Summary: Show topics in hgweb
   Product: Mercurial
   Version: 6.3.1
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: z...@zash.se
CC: mercurial-de...@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

Topics are currently not show in hgweb. It would be nice if they were, when the
topic extension is enabled.

Currently it seems to be non-trivial to add to a custom theme:

`{topic}` produces the empty string

`{extra.topic}` produces this error:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mercurial/templateutil.py", line 1128,
in runmember
return d.getmember(context, mapping, memb)
  File "/usr/lib/python3/dist-packages/mercurial/templateutil.py", line 183, in
getmember
raise error.ParseError(_(b'%r is not a dictionary') % self._value)
mercurial.error.ParseError: {b'branch': b'default', b'rebase_source':
b'8bd8d9b59169a4a14276012f1f7fa49a2de33d6b', b'topic': b'http-override-cors'}
is not a dictionary

However `{extra|json}` does result in an object containing a 'topic' member, so
the data is there.

evolve 10.5.3
topic 0.24.2

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6825] New: Search for topic() in hgweb

2023-06-23 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6825

Bug ID: 6825
   Summary: Search for topic() in hgweb
   Product: Mercurial
   Version: 6.3.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: z...@zash.se
CC: mercurial-de...@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

Given a Mercurial and hgweb instance with the topic extentsion enabled, one
would expect a search like `topic("my-feature")` to list commits in that topic.

However this does not currently work, hgweb says:
> searching for 'topic("example")'
> Assuming literal keyword search. 

evolve 10.5.3
topic 0.24.2

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6824] New: Provide a more meaningful context during conflicts.

2023-06-22 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6824

Bug ID: 6824
   Summary: Provide a more meaningful context during conflicts.
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: All
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jar...@jaraco.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

We're finding that our users are consistently confused by the messaging when
resolving conflicts for binary files.

The message looks like this:

```
no tool found to merge file
file 'file' needs to be resolved.
You can keep (l)ocal [dest], take (o)ther [source], or leave (u)nresolved.
What do you want to do?
```

But in many contexts, the user is unaware of the internal implementation of a
particular command like "sync", which rebases changes, so "dest" and "source"
aren't intuitive.

On the other hand, if a merge tool is invoked, a helpful context is emitted
before the merge tool is run.

```
Running merge tool for foo ('some/tool'):
 - local (working copy): 984e1e5d Appending a different byte tip
 - base (common ancestor): 104fe963 Adding a binary file
 -other (merge rev): 14655abc Appending another byte
```

The short hashes and commit messages provides a meaningful context to the user
to be able to rapidly choose a winner, independent of how the two parents were
ordered.

This feature proposes to provide that context prior to prompting the user to
resolve any conflicts.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6823] New: behavior of 'locate' changed

2023-06-20 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6823

Bug ID: 6823
   Summary: behavior of 'locate' changed
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: All
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jar...@jaraco.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Consider these steps:

```
hg init foo
cd foo
mkdir bar
touch bar/baz
hg commit -Am baz
cd bar
hg locate -I .
```

On Mercurial 6.1.1, it emits:

```
bar/baz
```

On Mercurial 6.4, it emits:

```
baz
```

This leads to inconsistencies and [this
bug](https://github.com/jaraco/hgtools/issues/34).

I searched the changelogs for Mercurial 6.2, 6.3, and 6.4, but there's no
mention of 'locate'. Was this change in behavior intentional?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6822] New: test-hgrc.t: fails with encoding problem

2023-06-16 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6822

Bug ID: 6822
   Summary: test-hgrc.t: fails with encoding problem
   Product: Mercurial
   Version: unspecified
  Hardware: All
OS: NetBSD
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: t...@giga.or.at
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

With Python 3.11 in my environment, I see:

--- /scratch/devel/py-mercurial/work/mercurial-6.4.4/tests/test-hgrc.t
+++ /scratch/devel/py-mercurial/work/mercurial-6.4.4/tests/test-hgrc.t.err
@@ -310,6 +310,21 @@

 #if no-pyoxidizer-in-filesystem
   $ HGRCSKIPREPO=1 hg paths --config extensions.zeroconf=
+  Traceback (most recent call last):
+File
"/tmp/hgtests.6ypr5aft/install/lib/python/hgext/zeroconf/Zeroconf.py", line
954, in run
+  self.readers[sock].handle_read()
+File
"/tmp/hgtests.6ypr5aft/install/lib/python/hgext/zeroconf/Zeroconf.py", line
1008, in handle_read
+  msg = DNSIncoming(data)
+^
+File
"/tmp/hgtests.6ypr5aft/install/lib/python/hgext/zeroconf/Zeroconf.py", line
524, in __init__
+  self.readQuestions()
+File
"/tmp/hgtests.6ypr5aft/install/lib/python/hgext/zeroconf/Zeroconf.py", line
555, in readQuestions
+  question = DNSQuestion(name, info[0], info[1])
+ ^^^
+File
"/tmp/hgtests.6ypr5aft/install/lib/python/hgext/zeroconf/Zeroconf.py", line
296, in __init__
+  name = name.encode('ascii')
+ 
+  UnicodeEncodeError: 'ascii' codec can't encode character '\u2019' in
position 19: ordinal not in range(128)
   foo = $TESTTMP/bar
 #else
   $ HGRCSKIPREPO=1 hg paths --config extensions.zeroconf=

ERROR: test-hgrc.t output changed

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6821] New: hg init fails when HGENCODING is set to utf-8 and the repository name contains non-ASCII characters

2023-06-16 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6821

Bug ID: 6821
   Summary: hg init fails when HGENCODING is set to utf-8 and the
repository name contains non-ASCII characters
   Product: Mercurial
   Version: 6.4.2
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: rainer.ba...@telenot.de
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Environment: Windows 10 21H2 19044.3086
hg version : Mercurial Distributed SCM (version 6.4.2)
 (I am using the latest version of TortoiseHg)

I was hit by this issue, when I called 'hg log' from my program.

However, when I tried to reproduce it in a command prompt, the error already
occured when I tried to create the repository.

Steps to reproduce:
1) Open command prompt (cmd.exe)
2) cd to a directory with write permission (e.g. %userprofile%)
3) 'hg init ää' (executed successful)
4) 'SET HGENCODING=utf-8'
5) 'hg init üü' (fails with error: 'abort: decoding near
'nd\hg_bug\��/.hg/00c': 'utf-8' codec can't decode byte 0xfc in position 34:
invalid start byte!')

I tried to set the codepage to unicode (CHCP 65001), but the error persists.

Here is the trace when 'hg init --traceback üü' is executed:

Traceback (most recent call last):
  File "mercurial\windows.pyc", line 184, in posixfile
FileNotFoundError: [WinError 2] The system cannot find the file specified:
'C:\\tmp\\hg_bug\\üü/.hg/00changelog.i'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "mercurial\encoding.pyc", line 231, in fromlocal
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in position 34:
invalid start byte

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "mercurial\scmutil.pyc", line 153, in callcatch
  File "mercurial\dispatch.pyc", line 441, in _runcatchfunc
  File "mercurial\dispatch.pyc", line 1266, in _dispatch
  File "mercurial\dispatch.pyc", line 899, in runcommand
  File "mercurial\dispatch.pyc", line 1278, in _runcommand
  File "mercurial\dispatch.pyc", line 1264, in 
  File "mercurial\util.pyc", line 1881, in check
  File "mercurial\commands.pyc", line , in init
  File "mercurial\hg.pyc", line 270, in peer
  File "mercurial\hg.pyc", line 234, in repository
  File "mercurial\hg.pyc", line 147, in instance
  File "mercurial\localrepo.pyc", line 3598, in instance
  File "mercurial\localrepo.pyc", line 3967, in createrepository
  File "mercurial\vfs.pyc", line 124, in append
  File "mercurial\vfs.pyc", line 517, in __call__
  File "mercurial\windows.pyc", line 202, in posixfile
  File "mercurial\encoding.pyc", line 253, in unifromlocal
  File "mercurial\encoding.pyc", line 235, in fromlocal
mercurial.error.Abort: decoding near 'nd\hg_bug\üü/.hg/00c': 'utf-8' codec
can't decode byte 0xfc in position 34: invalid start byte!
abort: decoding near 'nd\hg_bug\��/.hg/00c': 'utf-8' codec can't decode byte
0xfc in position 34: invalid start byte!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6820] New: Strange unshelve behavior with topic extension

2023-06-14 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6820

Bug ID: 6820
   Summary: Strange unshelve behavior with topic extension
   Product: Mercurial
   Version: 6.4.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: shelve
  Assignee: bugzi...@mercurial-scm.org
  Reporter: fah...@faheem.info
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

The following recipe could be made simpler, but suffices to demonstrate the
issue. When unshelving, `unshelve` is trying to apply a patch to a file that
doesn't exist (`bar.txt`). It would normally stop and ask for instructions, but
here it creates a new `bar.txt` with an A (added) flag.

This is one of the options under normal behavior, but should not be the
default.

I'm posting my current recipe here. I might post a simplified version later.

rm -rf test-shelve2
hg init test-shelve2
cd test-shelve2
echo "First line of foo.txt" >> foo.txt
hg add foo.txt
hg ci -m "Add foo.txt"
echo "Second line of foo.txt" >> foo.txt
hg ci -m "foo.txt second line"
hg topic bar
echo "First line of bar.txt" >> bar.txt
hg add bar.txt
hg ci -m "Add bar.txt"
echo "Second line of bar.txt" >> bar.txt
hg ci -m "bar.txt second line"
find . -type f -name '*.txt' -exec sed -i 's/Second line/Second Line/g' {} +
hg shelve
hg shelve -p
hg up default
hg unshelve
hg status

This gives

faheem@orwell:~/test-mercurial$ sh shelve2.sh 
marked working directory as topic: bar
active topic 'bar' grew its first changeset
(see 'hg help topics' for more information)
shelved as default
2 files updated, 0 files merged, 0 files removed, 0 files unresolved
default (1s ago)changes to: bar.txt second line

diff --git a/bar.txt b/bar.txt
--- a/bar.txt
+++ b/bar.txt
@@ -1,2 +1,2 @@
 First line of bar.txt
-Second line of bar.txt
+Second Line of bar.txt
diff --git a/foo.txt b/foo.txt
--- a/foo.txt
+++ b/foo.txt
@@ -1,2 +1,2 @@
 First line of foo.txt
-Second line of foo.txt
+Second Line of foo.txt
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
unshelving change 'default'
rebasing shelved changes
M foo.txt
A bar.txt

Obviously, the `A bar.txt` part is very wrong.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6819] New: amend and --obsolete tip behaves unexpectedly

2023-06-10 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6819

Bug ID: 6819
   Summary: amend and --obsolete tip behaves unexpectedly
   Product: Mercurial
   Version: 6.3.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: z...@zash.se
CC: mercurial-de...@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

Attempted amend a commit and at the same time obsolete a commit that was 'tip'
at the time, but it appears this reference is resolved after the new commit has
been amended, thus itself becoming 'tip'.

$ hg ci --amend --obs tip
starting interactive selection
1 new orphan changesets
abort: changeset e3efd08e9363 cannot obsolete itself

I expected this to work, the reference to 'tip' to be resolved at the beginning
of the transaction before that reference changes.

Mercurial Distributed SCM (version 6.3.2+hg38.7d2199fedac7)
 evolveexternal  11.0.0rc0

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6818] New: doc: 'hg help dates' doesn't describe format strings

2023-05-31 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6818

Bug ID: 6818
   Summary: doc: 'hg help dates' doesn't describe format strings
   Product: Mercurial
   Version: 6.4.3
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: t...@giga.or.at
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

'hg help templates' says:

date(date[, fmt])
  Format a date. See 'hg help dates' for formatting strings.
  The default is a Unix date format, including the timezone:
  "Mon Sep 04 15:13:13 2006 0700".

but 'hg help dates' only describes acceptable date strings, not how to format
date strings.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6817] New: cmdserver: process exited unexpectedly with code 255

2023-05-10 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6817

Bug ID: 6817
   Summary: cmdserver: process exited unexpectedly with code 255
   Product: Mercurial
   Version: 6.4
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jch...@endiag.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

While attempting to clone a git repository using hggit, I get the following
error:

** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64
bit (AMD64)]
** Mercurial Distributed SCM (version 6.4)
** Extensions loaded: hggit 1.0.2 (dulwich 0.21.3), mq, strip,
tortoisehg.util.hgcommands, tortoisehg.util.hgdispatch,
tortoisehg.util.partialcommit, tortoisehg.util.pipeui, tortoisehg.util.win32ill
Traceback (most recent call last):
  File "hg", line 58, in 
  File "mercurial\dispatch.pyc", line 143, in run
  File "mercurial\dispatch.pyc", line 232, in dispatch
  File "mercurial\dispatch.pyc", line 276, in _rundispatch
  File "mercurial\dispatch.pyc", line 451, in _runcatch
  File "mercurial\dispatch.pyc", line 461, in _callcatch
  File "mercurial\scmutil.pyc", line 153, in callcatch
  File "mercurial\dispatch.pyc", line 441, in _runcatchfunc
  File "mercurial\dispatch.pyc", line 1266, in _dispatch
  File "mercurial\dispatch.pyc", line 899, in runcommand
  File "mercurial\dispatch.pyc", line 1278, in _runcommand
  File "mercurial\dispatch.pyc", line 1264, in 
  File "mercurial\util.pyc", line 1881, in check
  File "mercurial\util.pyc", line 1881, in check
  File "hgext\mq.pyc", line 4227, in mqcommand
  File "mercurial\util.pyc", line 1881, in check
  File "mercurial\commands.pyc", line 6655, in serve
  File "mercurial\server.pyc", line 166, in runservice
  File "mercurial\commandserver.pyc", line 461, in run
  File "mercurial\commandserver.pyc", line 395, in serve
  File "mercurial\commandserver.pyc", line 369, in serveone
  File "mercurial\commandserver.pyc", line 350, in runcommand
  File "mercurial\commandserver.pyc", line 289, in _dispatchcommand
  File "mercurial\dispatch.pyc", line 232, in dispatch
  File "mercurial\dispatch.pyc", line 276, in _rundispatch
  File "mercurial\dispatch.pyc", line 451, in _runcatch
  File "mercurial\dispatch.pyc", line 461, in _callcatch
  File "mercurial\scmutil.pyc", line 153, in callcatch
  File "mercurial\dispatch.pyc", line 441, in _runcatchfunc
  File "tortoisehg\util\hgdispatch.pyc", line 23, in _dispatch
  File "mercurial\dispatch.pyc", line 1266, in _dispatch
  File "mercurial\dispatch.pyc", line 899, in runcommand
  File "mercurial\dispatch.pyc", line 1278, in _runcommand
  File "mercurial\dispatch.pyc", line 1264, in 
  File "mercurial\util.pyc", line 1881, in check
  File "mercurial\commands.pyc", line 1982, in clone
  File "hggit\schemes.pyc", line 121, in clone
  File "mercurial\hg.pyc", line 1008, in clone
  File "hggit\util.pyc", line 99, in inner
  File "hggit\gitrepo.pyc", line 196, in exchangepull
  File "hggit\git_handler.pyc", line 365, in fetch
  File "hggit\git_handler.pyc", line 1041, in import_git_objects
  File "hggit\git_handler.pyc", line 1146, in import_git_commit
  File "dulwich\config.pyc", line 765, in parse_submodules
  File "dulwich\config.pyc", line 339, in get
  File "dulwich\config.pyc", line 101, in __getitem__
KeyError: (b'submodule',)
cmdserver: process exited unexpectedly with code 255

Please let me know if there is anything I can do to help debug this, thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6815] New: the imp module is deprecated in favour of importlib and slated for removal in Python 3.12

2023-05-07 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6815

Bug ID: 6815
   Summary: the imp module is deprecated in favour of importlib
and slated for removal in Python 3.12
   Product: Mercurial
   Version: default branch
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: m...@kiilerich.com
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Reporting this to track that Mercurial still has a few references to the imp
module.

For example:
venv/lib64/python3.11/site-packages/mercurial/utils/resourceutil.py:12
  venv/lib64/python3.11/site-packages/mercurial/utils/resourceutil.py:12:
DeprecationWarning: the imp module is deprecated in favour of importlib and
slated for removal in Python 3.12; see the module's documentation for
alternative uses
import imp

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6813] New: test-fix.t intermittent failure

2023-04-19 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6813

Bug ID: 6813
   Summary: test-fix.t intermittent failure
   Product: Mercurial
   Version: 6.4.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jcris...@debian.org
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

Seen in
https://buildd.debian.org/status/fetch.php?pkg=mercurial=all=6.4.2-1=1681833128=0:

--- /<>/tests/test-fix.t
+++ /<>/tests/test-fix.t.err
@@ -680,6 +680,17 @@
   [wdir] fail: error that did stop the tool
   abort: no fixes will be applied
   (use --config fix.failure=continue to apply any successful fixes anyway)
+  Exception ignored in: 
+  Traceback (most recent call last):
+File "/usr/lib/python3.11/threading.py", line 1638, in _after_fork
+  threads.update(_dangling)
+File "/usr/lib/python3.11/_weakrefset.py", line 64, in __iter__
+  with _IterationGuard(self):
+File "/usr/lib/python3.11/_weakrefset.py", line 31, in __exit__
+  s.remove(self)
+File "/tmp/hgtests.dq2rr4cr/install/lib/python/mercurial/dispatch.py",
line 330, in catchterm
+  raise error.SignalInterrupt
+  mercurial.error.SignalInterrupt: 
   [255]
   $ cat hello.txt
   goodbye

ERROR: test-fix.t output changed

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6812] New: chg fails to build after cf4d2f31660d

2023-04-18 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6812

Bug ID: 6812
   Summary: chg fails to build after cf4d2f31660d
   Product: Mercurial
   Version: 6.4.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: chg
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jcris...@debian.org
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

https://www.mercurial-scm.org/repo/hg/rev/cf4d2f31660d uses environ without
declaring it, causing:

/usr/bin/make build-chg
make[2]: Entering directory '/<>'
make -C contrib/chg
make[3]: Entering directory '/<>/contrib/chg'
cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -std=gnu99 -Wdate-time -D_FORTIFY_SOURCE=2  -c
-o chg.o chg.c
chg.c: In function 'main':
chg.c:535:54: error: 'environ' undeclared (first use in this function)
  535 | hgc_setenv(hgc, (const char *const *)environ);
  |  ^~~
chg.c:535:54: note: each undeclared identifier is reported only once for each
function it appears in
make[3]: *** [: chg.o] Error 1
make[3]: Leaving directory '/<>/contrib/chg'
make[2]: *** [Makefile:72: build-chg] Error 2
make[2]: Leaving directory '/<>'

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6811] New: Clone of repository stopped working with changeset 87f0155d68aa

2023-04-17 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6811

Bug ID: 6811
   Summary: Clone of repository stopped working with changeset
87f0155d68aa
   Product: Mercurial
   Version: 6.4.1
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: m...@manueljacob.de
CC: mercurial-de...@mercurial-scm.org
Python Version: ---

With Mercurial cf6e1d535602 (parent of 87f0155d68aa), the following worked:

% ./hg clone https://kallithea-scm.org/repos/kallithea /tmp/kallithea
% cd /tmp/kallithea
% hg id

But with Mercurial 87f0155d68aa, ae9a15267315 (current head of stable) and
a0e39f5bb7cd (current head of default), the last command fails with the
following error:

abort: 00manifest@47652662ac23c386e873c20b84f6aace9cca8bb5: no node

Disabling clone bundles (`--config ui.clonebundles=false`) fixes the problem.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6810] New: Regression: force push needed in 6.4 / hg-evolve 11

2023-04-13 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6810

Bug ID: 6810
   Summary: Regression: force push needed in 6.4 / hg-evolve 11
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: georges.raci...@octobus.net
CC: mercurial-de...@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

Hi, I have a case where a push failed in Heptapod tests after upgrading the
client to Mercurial 6.4.1 and hg-evolve 11.0.1.

If that matters, the server is running the very same versions. The problem does
not occur with 6.3.3 and 10.5.3 on the client side (even on the same server
versions).

It's obviously not the most severe of bugs: users can work around it by adding
`-f`, just like I did in
https://foss.heptapod.net/heptapod/heptapod-tests/-/commit/fe796d4a6e876fb94bd53b247a41251c3560f7a3

I know it's not terribly useful in this form, but I can translate this
reproduction in something better later (mostly trying not to forget about it).

Here is the output of the `print` statements you can see in the above commit:

```
Graph before push/publish:
@  3:3864a8e3a408 Even a horse! (draft)
|
| x  2:169cbdb9bdd8 Even a horse! (draft)
|/ obsolete:date-changed using amend as 3:3864a8e3a408
|
o  1:2705d437970b Même une antilope ! (draft)
|
o  0:1f6fd4542e4b Initial sentence (public)

```

At the time of the failing push, the server has changeset 1 (2705d437970b) and
that's its tip.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6721] New: Crash when pushing to a local clone

2022-06-26 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6721

Bug ID: 6721
   Summary: Crash when pushing to a local clone
   Product: Mercurial
   Version: default branch
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: j...@jcea.es
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

I have a project with a default branch and a "debian-bullseye" branch. My
current work area is "BullsEye", but I needed to do a tiny commit to "default".
Since I have a lot of uncommitted changes, instead of switching branches, I
created a local clone of my local clone, some like this:

```
$ cd /tmp
$ hg clone PATH_TO_MY_CURRENT_CLONE
$ cd /tmp/NEW_CLONE
(edit files there)
$ hg commit ...
$ hg push
```

The push should update the original clone. In this way I don't disturb my
original working directory.

When doing the "hg push", I get this traceback.

```
jcea@jcea:/tmp/ram/radio-utopia/radio-utopia$ hg push
pushing to /home/jcea/hg/radio-utopia
searching for changes
adding changesets
adding manifests
adding file changes
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.10.5 (main, Jun 14 2022, 22:30:02) [GCC 9.4.0]
** Mercurial Distributed SCM (version 6.1.4)
** Extensions loaded: absorb, churn, convert, evolve 10.5.1, graphlog, hggit
1.0.0 (dulwich 0.20.25), mq, narrow, rebase, relink, share, show, strip, topic
0.24.1.dev
Traceback (most recent call last):
  File "/home/jcea/.local/bin/hg", line 61, in 
dispatch.run()
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 144, in run
status = dispatch(req)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 250, in dispatch
status = _rundispatch(req)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 294, in _rundispatch
ret = _runcatch(req) or 0
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 470, in _runcatch
return _callcatch(ui, _runcatchfunc)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 480, in _callcatch
return scmutil.callcatch(ui, func)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/scmutil.py",
line 153, in callcatch
return func()
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 460, in _runcatchfunc
return _dispatch(req)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1273, in _dispatch
return runcommand(
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 918, in runcommand
ret = _runcommand(ui, options, cmd, d)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1285, in _runcommand
return cmdfunc()
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/dispatch.py",
line 1271, in 
d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/util.py", line
1887, in check
return func(*args, **kwargs)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/util.py", line
1887, in check
return func(*args, **kwargs)
  File "/home/jcea/.local/lib/python3.10/site-packages/hgext/mq.py", line 4239,
in mqcommand
return orig(ui, repo, *args, **kwargs)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/util.py", line
1887, in check
return func(*args, **kwargs)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/util.py", line
1887, in check
return func(*args, **kwargs)
  File
"/home/jcea/.local/lib/python3.10/site-packages/hgext3rd/topic/__init__.py",
line 1353, in pushoutgoingwrap
return orig(ui, repo, *args, **opts)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/util.py", line
1887, in check
return func(*args, **kwargs)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/util.py", line
1887, in check
return func(*args, **kwargs)
  File "/home/jcea/.local/lib/python3.10/site-packages/hgext3rd/topic/flow.py",
line 94, in wrappush
return orig(repo, remote, *args, **newargs)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/util.py", line
1887, in check
return func(*args, **kwargs)
  File "/home/jcea/.local/lib/python3.10/site-packages/mercurial/commands.py",
line 5794, in push
pushop = exchange.push(
  File "/home/jcea/.local/lib/python3.10/site-packages/hggit/util.py", line 95,
in inner
return f(*args, **kwargs)
  File "/home/jcea/.local/lib/python3.10/site-packages/hggit/gitrepo.py", line
231, in exchangepush
return orig(
  File
"/home/jcea/.local/lib/python3.10/site-packages/hgext3rd/evolve/__init__.py",

[Bug 6719] New: ttrr

2022-06-24 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6719

Bug ID: 6719
   Summary: ttrr
   Product: Mercurial
   Version: 6.1rc0
  Hardware: Other
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: blackbox
  Assignee: bugzi...@mercurial-scm.org
  Reporter: junaidisto...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Created attachment 2149
  --> https://bz.mercurial-scm.org/attachment.cgi?id=2149=edit
gg

hh

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6718] New: What Should I Do If Looking To Know How To Delete Cash App History?

2022-06-21 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6718

Bug ID: 6718
   Summary: What Should I Do If Looking To Know How To Delete Cash
App History?
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: acl
  Assignee: bugzi...@mercurial-scm.org
  Reporter: reedallen...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Give yourself a time if you are looking to delete the history section of your
Cash App account because there is no safety concern you have to face with the
history part! Still, if you would like to know How To Delete Cash App History,
you have to contact the Cash App geeks right now. 
https://www.emailsupport-contact.com/blog/how-to-delete-cash-app-history/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6717] New: How Do I Know How To Link Cash App With Plaid Easily?

2022-06-18 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6717

Bug ID: 6717
   Summary: How Do I Know How To Link Cash App With Plaid Easily?
   Product: Mercurial project
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: website
  Assignee: bugzi...@mercurial-scm.org
  Reporter: starksteve...@gmail.com
CC: mercurial-devel@mercurial-scm.org

To know all about How to Link Cash App with Plaid, you have to try to link your
Cash App account wallet with your existing bank account. Apart from that, you
can also opt for expert’s backing to avoid almost all sorts of doubts or
concerns within the least time frame. 
https://www.emailsupport-contact.com/blog/how-does-plaid-work-with-cash-app/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6716] New: test-revlog: uses unsupported '--force-local' tar(1) option

2022-06-13 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6716

Bug ID: 6716
   Summary: test-revlog: uses unsupported '--force-local' tar(1)
option
   Product: Mercurial
   Version: 6.1.3
  Hardware: All
OS: NetBSD
Status: UNCONFIRMED
  Severity: bug
  Priority: normal
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: t...@giga.or.at
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

tar on NetBSD does not support --force-local, leading to:

--- /scratch/devel/py-mercurial/work/mercurial-6.1.3/tests/test-revlog.t
+++ /scratch/devel/py-mercurial/work/mercurial-6.1.3/tests/test-revlog.t.err
@@ -74,10 +74,13 @@ 
 - remove some cache files  

   $ tar --force-local -xf
"$TESTDIR"/bundles/test-revlog-diff-relative-to-nullrev.tar 
+  tar: Option --force-local is not supported   
+  Usage:   
+List:tar -tf 
+Extract: tar -xf 
+Create:  tar -cf  [filenames...] 
+Help:tar --help
+  [1]  
   $ cd nullrev-diff
+  cd: can't cd to nullrev-diff 
   $ hg debugdeltachain a   
-  rev  chain# chainlen prev   delta   sizerawsize  chainsize  
  ratio   lindist extradist extraratio   readsize largestblk rddensity srchunks
-0   12   -1  p1 15  3 15  
5.015 00.0 15 15   1.01
-  $ hg cat --config rhg.cat=true -r 0 a
-  hi   
-  $ cd ..  

ERROR: test-revlog.t output changed

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6715] New: mercurial crashes in zstd (arm32)

2022-06-12 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6715

Bug ID: 6715
   Summary: mercurial crashes in zstd (arm32)
   Product: Mercurial
   Version: 6.1
  Hardware: Other
OS: All
Status: UNCONFIRMED
  Severity: bug
  Priority: urgent
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: t...@giga.or.at
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

A bug was filed in pkgsrc against mercurial 6.1: http://gnats.netbsd.org/56880

In short, please update the included zstd.

Here's the main content of the problem:


Cloning a repository with mercurial results in a bus error:

> Thread 1 "" received signal SIGBUS, Bus error.
> 0x7add40e0 in ZSTD_compressBlock_doubleFast ()
>from /usr/pkg/lib/python3.9/site-packages/mercurial/zstd.so

This could be a known bug in zstd on this hardware:

https://github.com/RPi-Distro/repo/issues/179

The bug has been fixed in zstd 1.4.8, but the mercurial package
embeds the older version 1.4.4.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6714] New: Command-line 'config.auth.' options do not override options from config file.

2022-06-12 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6714

Bug ID: 6714
   Summary: Command-line 'config.auth.' options do not override
options from config file.
   Product: Mercurial
   Version: 6.1
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: mr.dmitry.soko...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

1) Local config: %USERPROFILE%\mercurial.ini

[auth]
server1.prefix = hg.example.org
server1.username = john.doe
server1.schemes = https


2) Running

$ hg --config auth.jenkins.prefix=* --config auth.jenkins.username=jenkins
--config auth.jenkins.password=*** --config "auth.jenkins.schemes=http https"
clone --rev default --noupdate https://hg.example.org/JENKINS
C:\Jenkins\workspace\Build_project

abort: keyring: http authorization required but program used in non-interactive
mode
ERROR: Failed to clone https://hg.example.org/JENKINS



The error disappears if the "[auth]" section is deleted from the local config.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6713] New: hg convert TypeError

2022-06-09 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6713

Bug ID: 6713
   Summary: hg convert TypeError
   Product: Mercurial
   Version: 6.1.2
  Hardware: All
OS: NetBSD
Status: UNCONFIRMED
  Severity: bug
  Priority: normal
 Component: convert
  Assignee: bugzi...@mercurial-scm.org
  Reporter: t...@giga.or.at
CC: duri...@gmail.com, mercurial-devel@mercurial-scm.org
Python Version: ---

I just tried 'hg convert' on an old CVS repository (which I can't share, sorry)
and got:

7793 log entries
creating changesets
** unknown exception encountered, please report by visiting
** https://mercurial-scm.org/wiki/BugTracker
** Python 3.10.4 (main, May 27 2022, 06:14:29) [GCC 10.3.0]
** Mercurial Distributed SCM (version 6.1.2)
** Extensions loaded: amend, convert, histedit, pager, patchbomb, purge,
rebase, strip
Traceback (most recent call last):
  File "/usr/pkg/bin/hg", line 61, in 
dispatch.run()
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/dispatch.py", line 144,
in run
status = dispatch(req)
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/dispatch.py", line 250,
in dispatch
status = _rundispatch(req)
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/dispatch.py", line 294,
in _rundispatch
ret = _runcatch(req) or 0
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/dispatch.py", line 470,
in _runcatch
return _callcatch(ui, _runcatchfunc)
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/dispatch.py", line 480,
in _callcatch
return scmutil.callcatch(ui, func)
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/scmutil.py", line 153,
in callcatch
return func()
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/dispatch.py", line 460,
in _runcatchfunc
return _dispatch(req)
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/dispatch.py", line
1273, in _dispatch
return runcommand(
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/dispatch.py", line 918,
in runcommand
ret = _runcommand(ui, options, cmd, d)
  File "/usr/pkg/lib/python3.10/site-packages/hgext/pager.py", line 78, in
pagecmd
return orig(ui, options, cmd, cmdfunc)
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/dispatch.py", line
1285, in _runcommand
return cmdfunc()
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/dispatch.py", line
1271, in 
d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
  File "/usr/pkg/lib/python3.10/site-packages/mercurial/util.py", line 1887, in
check
return func(*args, **kwargs)
  File "/usr/pkg/lib/python3.10/site-packages/hgext/convert/__init__.py", line
511, in convert
return convcmd.convert(ui, src, dest, revmapfile, **opts)
  File "/usr/pkg/lib/python3.10/site-packages/hgext/convert/convcmd.py", line
670, in convert
c.convert(sortmode)
  File "/usr/pkg/lib/python3.10/site-packages/hgext/convert/convcmd.py", line
548, in convert
heads = self.source.getheads()
  File "/usr/pkg/lib/python3.10/site-packages/hgext/convert/cvs.py", line 257,
in getheads
self._parse()
  File "/usr/pkg/lib/python3.10/site-packages/hgext/convert/cvs.py", line 95,
in _parse
db = cvsps.createchangeset(
  File "/usr/pkg/lib/python3.10/site-packages/hgext/convert/cvsps.py", line
691, in createchangeset
t = b'%d %s' % (len(changesets), repr(e.comment)[1:-1])
TypeError: %b requires a bytes-like object, or an object that implements
__bytes__, not 'str'

That's with python3, so perhaps a python 2 -> python 3 conversion bug?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6712] New: Alternative filename suffix for hg revert

2022-05-28 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6712

Bug ID: 6712
   Summary: Alternative filename suffix for hg revert
   Product: Mercurial
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: wolj...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Add configuration option to specify file suffix that is added to the original
files when hg revert is done.

Currently, hg revert creates files with .orig suffix. The suffix could be
user-configurable.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6711] New: Recursive search for .hgignore like in Git

2022-05-28 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6711

Bug ID: 6711
   Summary: Recursive search for .hgignore like in Git
   Product: Mercurial
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: wolj...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

I would like to have an option (enabled using hgrc) that makes the Mercurial
search through the whole directory tree for .hgignore files like Git does.
Every such file would be treated as if it would be subinclude:'d from the
parent directory.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6710] New: Space after the subinclude: in ignore files

2022-05-28 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6710

Bug ID: 6710
   Summary: Space after the subinclude: in ignore files
   Product: Mercurial
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: wolj...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

I would like to be able to add a space after the colon on subinclude:/include:
lines in ignore files. Like this:

  subinclude: dir/other-ignore-file

This breaks when the path to another ignore file actually starts with a space.
(I think that this is very rare situation.) I would also consider allowing
quotes ("") around the included file path or solving the space-related problem
by requiring it to be escaped using a backslash.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6709] New: Glob expressions in subinclude

2022-05-28 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6709

Bug ID: 6709
   Summary: Glob expressions in subinclude
   Product: Mercurial
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: wolj...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

I would like to use glob expressions in ‘subinclude:’ and ‘include:’ lines in
.hgignore files to match multiple ignore files or include files in any
subdirectory.

Use cases
═

Multiple ignore files
─

I have several ignore files that are generated by the build system. It would be
too much error-prone to manage them manually.

Files

  foo.hgignore
  bar.hgignore

I would add this line to the source-root .hgignore file:

  syntax: glob
  include:?*.hgignore

Ignore files in subdirectories
──

The project is divided into multiple parts, each residing in one subdirectory.
To apply all the ignore files, I would add this to the main .hgignore file:

  subinclude:*/.hgignore


Implementation
══

Finding files using glob-expressions that have the wildcards in directory names
can be quite expensive. I suggest also adding some kind of cache (or something)
that would make the lookup faster. If there is no cache, such glob-expressions
would slight higher performance impact on operations that use the ignore files,
but I think that it would not be big problem for most projects.

My idea about the cache:  When the ignore entry list caching is enabled (in
hgrc), only one hgignore file, located in the .hg directory (let's say
.hg/cached-ignore) is used instead of other ignore files. This file contains
all the hgignore files merged, but still with globs and regular expressions
unexpanded. It is updated manually, by invoking command, let's say, hg
update-ignore. This would make the lookup much faster, but at cost of one
additional command after changing the ignore rules. Smarter approaches could be
also used, such as comparing ctimes of .hg/cached-ignore with the other ignore
files etc.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6708] New: unknown exception encountered, on push, with evolve enabled: caused by AttributeError: module 'sqlite3' has no attribute 'connect'

2022-05-23 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6708

Bug ID: 6708
   Summary: unknown exception encountered, on push, with evolve
enabled: caused by AttributeError: module 'sqlite3'
has no attribute 'connect'
   Product: Mercurial
   Version: 6.0.1
  Hardware: Macintosh
OS: Mac OS
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: g...@nxg.name
CC: mercurial-devel@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

When I push a changeset with a topic to a remote server which has the evolve
extension enabled, I get the error below.

At the bottom, there is what is presumably the root cause of the problem, that 

remote: AttributeError: module 'sqlite3' has no attribute 'connect'

On the remote machine:

  * Python version is 3.7.12 (as shown below)
  * Mercurial version 5.3.2
  * hg-evolve extension was freshly installed just now (in a venv), as
hg-evolve-10.5.1.tar.gz

Locally:

  * Python 3.7.3
  * Mercurial 6.0.1
  * hg-evolve freshly installed (with pip --user), version hg_evolve-10.5.1

I appreciate the remote Mercurial revision is rather old; I do need to update
that soon, but it _appears_ that the issue is in the evolve extension.  These
Python and Mercurial versions have worked happily for a couple of years (since
5.3.2 was new!); this is the first time I've used hg-evolve in this context. 
If it would be useful do to that update, to help with a reproduction here, that
would be a useful prod to me, to put aside the time to do that!

This does appear to overlap with issue #6246, or even duplicate it, but that
appears to be with a much older Python version, and the stacktrace doesn't show
the underlying error.  I'm therefore reporting this as a _potentially_ separate
bug, which might shed light on that one.

Best wishes,

Norman




pushing to ssh://h...@code.nxg.name/nxg/tex/exam-n
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: ** unknown exception encountered, please report by visiting
remote: ** https://mercurial-scm.org/wiki/BugTracker
remote: ** Python 3.7.12 (default, Oct  5 2021, 11:42:29) [Clang 10.0.1
(g...@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611a
remote: ** Mercurial Distributed SCM (version 5.3.2)
remote: ** Extensions loaded: evolve, topic
remote: Traceback (most recent call last):
remote:   File "/local/hg/bin/hg-ssh", line 97, in 
remote: main()
remote:   File "/local/hg/bin/hg-ssh", line 82, in main
remote: dispatch.dispatch(req)
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/dispatch.py", line 254,
in dispatch
remote: ret = _runcatch(req) or 0
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/dispatch.py", line 428,
in _runcatch
remote: return _callcatch(ui, _runcatchfunc)
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/dispatch.py", line 437,
in _callcatch
remote: return scmutil.callcatch(ui, func)
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/scmutil.py", line 152, in
callcatch
remote: return func()
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/dispatch.py", line 418,
in _runcatchfunc
remote: return _dispatch(req)
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/dispatch.py", line 1182,
in _dispatch
remote: lui, repo, cmd, fullargs, ui, options, d, cmdpats, cmdoptions
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/dispatch.py", line 866,
in runcommand
remote: ret = _runcommand(ui, options, cmd, d)
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/dispatch.py", line 1193,
in _runcommand
remote: return cmdfunc()
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/dispatch.py", line 1179,
in 
remote: d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
remote:   File "/local/hg/venv/lib/python3.7/site-packages/mercurial/util.py",
line 1854, in check
remote: return func(*args, **kwargs)
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/commands.py", line 6494,
in serve
remote: s.serve_forever()
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/wireprotoserver.py", line
852, in serve_forever
remote: self.serveuntil(threading.Event())
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/wireprotoserver.py", line
858, in serveuntil
remote: _runsshserver(self._ui, self._repo, self._fin, self._fout, ev)
remote:   File
"/local/hg/venv/lib/python3.7/site-packages/mercurial/wireprotoserver.py", line
700, in _runsshserver
remote: rsp = wireprotov1server.dispatch(repo, proto, request)
remote:   File

[Bug 6707] New: How Facebook Number Assists In Getting The Right Assistance And Support?

2022-05-20 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6707

Bug ID: 6707
   Summary: How Facebook Number Assists In Getting The Right
Assistance And Support?
   Product: Mercurial project
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: website
  Assignee: bugzi...@mercurial-scm.org
  Reporter: angelinalaurel...@gmail.com
CC: mercurial-devel@mercurial-scm.org

It is not a shocking moment if you are running into any kind of hassle and
hurdle. In such a case, you have to get in touch with the professionals who
will let you know how you can get a permanent solution. If you are unable to
approach them, you should make a call at Facebook Number and get a solution.
https://www.techjaadu.com/facebook-phone-number/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6706] New: Am I Capable Of Finding Out Cash App Bank Name With Ease?

2022-05-17 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6706

Bug ID: 6706
   Summary: Am I Capable Of Finding Out Cash App Bank Name With
Ease?
   Product: Mercurial
   Version: default branch
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bookmarks
  Assignee: bugzi...@mercurial-scm.org
  Reporter: drisskay8...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Of course, yes. You can without a doubt capable of finding out Cash App Bank
Name without any kind of hassle and hurdle. However, it becomes very easy when
it comes to search for the correct Cash App bank name by making proper
utilization of Cash App routing number. 
https://www.contactmail-support.com/blog/cash-app-bank-name/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6705] New: Py3 MSIs are not removing old py2 files on upgrade

2022-05-13 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6705

Bug ID: 6705
   Summary: Py3 MSIs are not removing old py2 files on upgrade
   Product: Mercurial
   Version: 6.1.2
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: packaging
  Assignee: bugzi...@mercurial-scm.org
  Reporter: matt_harbi...@yahoo.com
CC: duri...@gmail.com, gregory.sz...@gmail.com,
mercurial-devel@mercurial-scm.org
Python Version: ---

I installed the official py2 build of 6.1.1 x64 on Windows 2019, and then
installed the official py3 build of 6.1.2 x64 over the top of it.  I'd expect
it to cleanup the old install and replace it with the new one, but it left
python27.dll (and maybe other things) behind.  It also added a second entry to
the Add/Remove programs list.

I haven't noticed this issue with the thg installers up to this point, but now
that I've ported the packaging from hg there for py3 builds, I'm seeing similar
issues sometimes.  No idea what the issue is (though the current thg issue
might be generating multiple MSIs with the same version number for testing). 
The validation feature in Orca complains about lots of stuff in the py2 MSI
(mostly around the VCRT merge modules), but the only things it flags in py3 are
these (which don't seem relevant):

ICE40   WARNING REINSTALLMODE is defined in the Property table. This may cause
difficulties.
ICE61   WARNING This product should remove only older versions of itself. No
Maximum version was detected for the current product.
(INSTALLEDMERCURIALPRODUCTS)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6701] New: Consider calling the technical team to solve the cash app hack free money glitch

2022-05-10 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6701

Bug ID: 6701
   Summary: Consider calling the technical team to solve the cash
app hack free money glitch
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bookmarks
  Assignee: bugzi...@mercurial-scm.org
  Reporter: avahop...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Are you getting trouble transferring money on the cash app?
Want to rectify cash app hack free money glitch with ease?
If you’re finding difficulty in using the cash app then you must talk to the
executives for instant help. Seek help from them for troubleshooting solutions
to proper instructions.

https://www.techjaadu.com/blog/how-to-hack-cash-app-and-get-free-money/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6700] New: tests/dummysmtpd.py uses deprecated asyncore module

2022-05-09 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6700

Bug ID: 6700
   Summary: tests/dummysmtpd.py uses deprecated asyncore module
   Product: Mercurial
   Version: default branch
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: victor.stin...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

The Python asyncore module will be removed in Python 3.12:
https://peps.python.org/pep-0594/

You should copy asyncore.py to tests/ or maintain this module externally.

In Python 3.11, "import asyncore" emits a DeprecationWarning (silent by
default): use "python -Wdefault" to show deprecation warnings.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6699] New: Can Someone Hack Your Cash App With Your Name Or Login Credentials?

2022-05-09 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6699

Bug ID: 6699
   Summary: Can Someone Hack Your Cash App With Your Name Or Login
Credentials?
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bookmarks
  Assignee: bugzi...@mercurial-scm.org
  Reporter: evaka...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Can Someone Hack Your Cash App With Your Name or not? To have a profound
knowledge of the equivalent in a problem free way, you should make a phone call
at the authority assist with calling number. Fortunately, it will associate you
to a group of experts who will make you mindful of the right direction and
backing.
https://www.techjaadu.com/blog/cash-app-hacked-account/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6698] New: Can I Take Necessary Guidance To Handle If Any Cash App Glitch Occurs?

2022-05-07 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6698

Bug ID: 6698
   Summary: Can I Take Necessary Guidance To Handle If Any Cash
App Glitch Occurs?
   Product: Mercurial
   Version: default branch
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bookmarks
  Assignee: bugzi...@mercurial-scm.org
  Reporter: addymi...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

If you would like to get a permanent solution to handle almost any type of Cash
App Glitch that can take place while working on your Cash App account, you
should directly make a call at the official helpline number and find out the
one-stop solution within the least time frame.
https://www.7qasearch.net/blog/cash-app-glitch/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6697] New: How To Delete Cash App Account? - Check Out the Steps In Detail

2022-05-06 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6697

Bug ID: 6697
   Summary: How To Delete Cash App Account? - Check Out the Steps
In Detail
   Product: Mercurial project
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: website
  Assignee: bugzi...@mercurial-scm.org
  Reporter: mahajansanji...@gmail.com
CC: mercurial-devel@mercurial-scm.org

Created attachment 2147
  --> https://bz.mercurial-scm.org/attachment.cgi?id=2147=edit
If you want to deactivate Cash App account, you need to transfer your funds
first, aka cash-out; then, you can close your Cash app account.

If you want to deactivate Cash App account, you need to transfer your funds
first, aka cash-out; then, you can close your Cash app account. 

Our Website - https://autocashapps.com/delete-cash-app-account/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6696] New: test-dirstate.t#dirstate-v2 failing with Rust detection

2022-05-05 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6696

Bug ID: 6696
   Summary: test-dirstate.t#dirstate-v2 failing with Rust
detection
   Product: Mercurial
   Version: 6.1.2
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: kwalkq.mercurial-bugzi...@pacien.net
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

test-dirstate.t#dirstate-v2 fails on 6.1.2 on NixOS.
This test was passing fine on 6.1.1 in the same environment.

The build has the Rust-related options enabled.

This problem could have been introduced with 682b0ac92c0b or 5d610521a285,
which seem related to Rust detection in tests.

```diff
--- /build/mercurial-6.1.2/tests/test-dirstate.t
+++ /build/mercurial-6.1.2/tests/test-dirstate.t#dirstate-v2.err
@@ -159,6 +159,7 @@
*1 (re)
   $ dirstate_uuid_has_not_changed
   not testing because using Python implementation (no-rust no-rhg !)
+  not testing because using Python implementation
 Trigger an append with a small change
@@ -169,6 +170,7 @@
*1 (re)
   $ dirstate_uuid_has_not_changed
   not testing because using Python implementation (no-rust no-rhg !)
+  not testing because using Python implementation
 Unused bytes counter is non-0 when appending
   $ touch file
@@ -183,6 +185,7 @@
*1 (re)
   $ dirstate_uuid_has_not_changed
   not testing because using Python implementation (no-rust no-rhg !)
+  not testing because using Python implementation
   $ hg debugstate --docket | grep unused
   number of unused bytes: 0 (no-rust no-rhg !)
ERROR: test-dirstate.t#dirstate-v2 output changed
```

Full build and test log:
https://logs.nix.ci/?key=nixos/nixpkgs.171565_id=463df95b-f00b-43af-a5cb-b905536c99b6

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6695] New: DDfree dishnews

2022-05-03 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6695

Bug ID: 6695
   Summary: DDfree dishnews
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bookmarks
  Assignee: bugzi...@mercurial-scm.org
  Reporter: ddfreedishnews...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

DD Freedish News gives all the latest news about DTH, Tech, Entertainment, and
lifestyle. In the review section, you can find reviews of popular products.

https://www.ddfreedishnews.com/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6694] New: Chandu Travels

2022-05-03 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6694

Bug ID: 6694
   Summary: Chandu Travels
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bookmarks
  Assignee: bugzi...@mercurial-scm.org
  Reporter: chandutravels2...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Chandu Travels now is a well-known brand in the bus operating industry. The
vision of Chandu travels is to give a new perspective to the bus operating
industry. The main motive of Chandu travels is the comfort of their passengers.

https://chandutravels.com/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6693] New: Celebrity News

2022-05-03 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6693

Bug ID: 6693
   Summary: Celebrity News
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bookmarks
  Assignee: bugzi...@mercurial-scm.org
  Reporter: celebritynews...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

CelebrityNews is a website, where you can get all information about your
favorite Hollywood celebrity. So if you want to know the full lifestyle of any
Hollywood celebrity then come to visit our website.

https://www.celebritynews.wiki/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6692] New: Biography talk

2022-05-03 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6692

Bug ID: 6692
   Summary: Biography talk
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bookmarks
  Assignee: bugzi...@mercurial-scm.org
  Reporter: biographyt...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

BiographyTalk is a user-friendly website for the users or audience who are
interested as well as keen to know about the celebrities be it, Actors, be it,
Singers, be it YouTubers, be it, Comedians, be it Dancers, or be it other
famous personalities. Moreover, it is the best place for people who want daily
updates related to famous personalities. It is a user-friendly interface
website, which is very handy to use.

https://biographytalk.com/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6691] New: Apk Beasts

2022-05-03 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6691

Bug ID: 6691
   Summary: Apk Beasts
   Product: Mercurial
   Version: 6.1rc0
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bookmarks
  Assignee: bugzi...@mercurial-scm.org
  Reporter: apkbeas...@protonmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

APK BEASTS is an independent website that gives you all the details about the
latest Android Apps, Games and tools & technology. We are here to give your
answer related to games and applications.

https://apkbeasts.com/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6690] New: Unexpected conflicts during evolve involving copies.

2022-05-01 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6690

Bug ID: 6690
   Summary: Unexpected conflicts during evolve involving copies.
   Product: Mercurial
   Version: 6.1.1
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: sebunge...@gmail.com
CC: mercurial-devel@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

Created attachment 2146
  --> https://bz.mercurial-scm.org/attachment.cgi?id=2146=edit
Script to reproduce conflict issue.

I recently upgraded from Ubuntu focal with a locally maintained mercurial 5.5.2
+ evolve 10.0.2 to Ubuntu jammy with the Ubuntu-supplied mercurial 6.1.1 and a
locally supplied evolve 10.5.1 (same result also with 10.5.0).

After the upgrade we started getting conflicts in evolutions that involve
copies of files but that should not produce any conflicts. The same operations
using the previous versions of mercurial and evolve do not produce conflicts.

I have attached as minimal a reproduction script as I could.

WARNING: The script will *delete* and recreate a folder named copyrebaseexample
in the current directory when run. Make sure you don't have one you don't want
to loose before running it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6689] New: hgWeb installed via PIP on IIS breaks when updating to Python 3.x

2022-04-29 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6689

Bug ID: 6689
   Summary: hgWeb installed via PIP on IIS breaks when updating to
Python 3.x
   Product: Mercurial
   Version: 6.1.1
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: hgweb
  Assignee: bugzi...@mercurial-scm.org
  Reporter: leonha...@fosber.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Created attachment 2139
  --> https://bz.mercurial-scm.org/attachment.cgi?id=2139=edit
Screencap of the error message received

Environment:

* Windows Server 2019 or 2022 with IIS Role installed.
** CGI and ISAPI restrictions role features are installed
* Python 2.7.18 installed to directory c:\Python27
* Python 3.10.4 installed to directory c:\Python310
* Mercurial package installed via "pip install mercurial" for the appropriate
Python version
* hgweb.cgi file taken from repository, only modifications are the "shebang"
line on top to point to the Python executables (which doesn't seem to do
anything in IIS) and the config path.

Background:

I have a Mercurial version 6.1.1 site running on Python 2.7 that is serving
repositories as expected. To upgrade the Python version, I expected to be able
to install Python 3.10 , navigate to c:\python310\scripts, run the command "pip
install mercurial", and update my web.config and hgweg.cgi files to point to
the new Python version's executable.

This procedure to upgrade the Python version (minus the web.config part) works
when using ApacheLounge to host the content. When I try it in IIS, I receive
this error message:

**
The specified CGI application misbehaved by not returning a complete set of
HTTP headers. The headers it did return are "Traceback (most recent call
last):File "C:\inetpub\HGWEB_FOSBERSPE\hgweb.cgi", line 22, in
wsgicgi.launch(application)File
"c:\Python310\lib\site-packages\mercurial\hgweb\wsgicgi.py", line 24, in
launchprocutil.setbinary(procutil.stdin)File
"c:\Python310\lib\site-packages\mercurial\windows.py", line 316, in setbinaryif
fno is not None and fno() >= 0: io.UnsupportedOperation: fileno ".
**

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6688] New: Visa Migration

2022-04-29 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6688

Bug ID: 6688
   Summary: Visa Migration
   Product: Mercurial
   Version: 6.1rc0
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: patchbomb
  Assignee: bugzi...@mercurial-scm.org
  Reporter: visandmigratio...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

[url=https://www.visaandmigration.com/service/uk-sole-representative-visa/73.html]UK
Sole Representative Visa[/url]

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6687] New: hg push to NAS hangs for 1 minute when evolve enabled

2022-04-28 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6687

Bug ID: 6687
   Summary: hg push to NAS hangs for 1 minute when evolve enabled
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: evolution
  Assignee: bugzi...@mercurial-scm.org
  Reporter: err...@raelity.com
CC: mercurial-devel@mercurial-scm.org,
pierre-yves.da...@ens-lyon.org
Python Version: ---

Versions:
Mercurial Distributed SCM (version 6.1.1)
  evolve  external  10.5.1

This started with a mailing list discussion
https://www.mercurial-scm.org/pipermail/mercurial/2022-April/053010.html

I finally got around to doing a mercurial push to a NAS from linux today. It
took a long time; it finally finished. I did another push, it quickly prints
"no changes found", and then sits there for one minute and finally finishes.
Windows native hg push to the NAS is as expected.

An hg push to a local filesystem doesn't pause.

Any idea how to track this down? Where's the timer? How to make it happy?

   $ hg --version -v
   Mercurial Distributed SCM (version 6.1)

   $ time hg push
   pushing to /z/repos/jvi-dev/jvi
   searching for changes
   no changes found

   real1m0.761s
   user0m0.210s
   sys0m0.054s 

After suggestion to use --debug --profile I see:

Twice it does:
... pause for 30 seconds ...
evoext-cache: error while saving new data: database is locked

And this, at the end of profile, looks telling
Note: the lines with the "_trysave" are displayed in red.

| 99.4% 60.29s  localrepo.py:   wrapperline 237: return
orig(repo.unfiltered...
 \ 49.6% 30.11s  stablerangecache.py: updatecaches line 532:
super(stablerangerepo, self...
   | 49.6% 30.11s  localrepo.py:   wrapper line 237: return
orig(repo.unfiltered...
   | 49.6% 30.08s  obsdiscovery.py: updatecaches   line 645:
self.obsstore.rangeobshashc...
   | 49.6% 30.08s  obsdiscovery.py: save   line 538: self._save(repo)
   | 49.6% 30.08s  obsdiscovery.py: _save  line 550: return
self._trysave(repo)
   | 49.6% 30.07s  obsdiscovery.py: _trysave   line 607:
self._ondiskcachekey = self...
 \ 49.5% 30.06s  stablerangecache.py: updatecaches line 531:
self.stablerange.save(self)
   | 49.5% 30.06s  stablerangecache.py: save   line 406: self._save(repo)
   | 49.5% 30.06s  stablerangecache.py: _save  line 287: return
self._trysave(repo)
   | 49.5% 30.06s  stablerangecache.py: _trysave   line 348:
con.execute(_updatemeta, meta)


$ hg --profile --debug push
pushing to /z/repos/jvi-dev/jvi
query 1; heads
searching for changes
all remote heads known locally
listing keys for "phases"
listing keys for "namespaces"
listing keys for "namespaces"
checking for updated bookmarks
listing keys for "bookmarks"
no changes found
bundle2-output-bundle: "HG20", 3 parts total
bundle2-output-part: "replycaps" 224 bytes payload
bundle2-output-part: "check:phases" 1032 bytes payload
bundle2-output-part: "obsmarkers" streamed payload
bundle2-input-bundle: with-transaction
bundle2-input-part: "replycaps" supported
bundle2-input-part: total payload size 224
bundle2-input-part: "check:phases" supported
bundle2-input-part: total payload size 1032
bundle2-input-part: "obsmarkers" supported
bundle2-input-part: total payload size 96848
bundle2-input-bundle: 3 parts total
evoext-cache: error while saving new data: database is locked
evoext-cache: error while saving new data: database is locked
bundle2-output-bundle: "HG20", 1 parts total
bundle2-output-part: "reply:obsmarkers" (params: 0 advisory) empty payload
bundle2-input-bundle: no-transaction
bundle2-input-part: "reply:obsmarkers" (params: 0 advisory) supported
bundle2-input-bundle: 1 parts total
listing keys for "phases"
| 100.0% 60.67s  hg:   line 61:   dispatch.run()
| 100.0% 60.67s  dispatch.py:run   line 144: status =
dispatch(req)
| 100.0% 60.67s  dispatch.py:dispatch  line 250: status =
_rundispatch(req)
| 100.0% 60.67s  dispatch.py:_rundispatch  line 294: ret =
_runcatch(req) or 0
| 100.0% 60.67s  dispatch.py:_runcatch line 470: return
_callcatch(ui, _runc...
| 100.0% 60.67s  dispatch.py:_callcatchline 480: return
scmutil.callcatch(ui...
| 100.0% 60.67s  scmutil.py: callcatch line 153: return func()
| 100.0% 60.67s  dispatch.py:_runcatchfunc line 460: return
_dispatch(req)
| 99.9% 60.61s  dispatch.py:_dispatch  line 1273: return
runcommand(
| 99.9% 60.61s  dispatch.py:runcommand line 918: ret =
_runcommand(ui, optio...
| 99.9% 60.61s  dispatch.py:_runcommandline 1285: return cmdfunc()
| 99.9% 60.61s  dispatch.py:   line 1271: d = lambda:
util.checksigna...
| 99.9% 60.61s  util.py:check  line 1887: return

[Bug 6686] New: Come To Know How To Change Cash App From Business To Personal Account

2022-04-27 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6686

Bug ID: 6686
   Summary: Come To Know How To Change Cash App From Business To
Personal Account
   Product: Mercurial
   Version: default branch
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: acl
  Assignee: bugzi...@mercurial-scm.org
  Reporter: seanperez...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Do you want to know How To Change Cash App From Business To Personal Account?
For that, you will need to get in touch with the Cash App support engineers
without wasting your time. Here, these geeks will provide you with the right
guidance and support to understand it in a proper manner. 
https://www.emailsupport-contact.com/blog/how-to-change-cash-app-from-business-to-personal-account/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6685] New: Can someone hack your cash app without your name? Is it possible?

2022-04-27 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6685

Bug ID: 6685
   Summary: Can someone hack your cash app without your name? Is
it possible?
   Product: Mercurial
   Version: earlier
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: automv
  Assignee: bugzi...@mercurial-scm.org
  Reporter: timh...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Cash app users are extremely perplexed as a result of the internet scam. They
want to know Can someone hack your cash app without your name to keep their
cash app account protected. This exists as the usual concern for cash app
users. As a result, they must understand how to keep the cash app secure. Users
may seek assistance from customer service professionals.

https://www.techjaadu.com/blog/cash-app-hacked-account/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6684] New: Can I Call Cash App Support number and Get Connected With Technical Squad?

2022-04-27 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6684

Bug ID: 6684
   Summary: Can I Call Cash App Support number and Get Connected
With Technical Squad?
   Product: Mercurial
   Version: default branch
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: automv
  Assignee: bugzi...@mercurial-scm.org
  Reporter: ana1997j...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Are you one of those Cash App users who are suffering from the Cash App issues
and are trying to fix it on their own? Unfortunately, they could often face
failure due to the lack of information and troubleshooting proficiency. For the
perfect remedy, you should make a call at Cash App Support number.
https://www.techjaadu.com/cash-app-support-number/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6683] New: Using --follow and --removed together gives wrong results

2022-04-27 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6683

Bug ID: 6683
   Summary: Using --follow and --removed together gives wrong
results
   Product: Mercurial
   Version: default branch
  Hardware: PC
OS: Linux
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jwde...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

I have a file that has been renamed, then subsequently removed. It currently
does not exist in my working directory.

I want to see the full history of this file, including the rename and removal.
Simple repro case provided at the bottom of this report.

So far, the only way I've been able to get the full history is to use multiple
commands, including both the new and old names for the file, piecing it all
together myself. I'd like to run one command to get the full history.

I tried:
$ hg log --removed --follow bar.txt

But this only shows the history after the rename. It does not show the original
history of the file - as though "--follow" is ignored.
I feel like this should be a warning, if '--follow' is ignored, or
incompatible?

I also tried using the original name, rather than the new (and now deleted)
one:

$ hg log --removed --follow foo.txt

However, this only shows the history up until the rename, and not following it.

The 'hg help revset' documentation has this to say for 'folow()' - I thought
that providing the optional 'startrev' might solve it for me:

"follow([file[, startrev]])"
  ...
  If file pattern is specified, the histories of files matching given
  pattern in the revision given by startrev are followed, including
  copies.

But alas, this command also does not work (empty results):

hg log --rev "follow('bar.txt', removes('bar.txt'))"


Ultimately, I want a single command that I can run that will give me the entire
history. Ideally, the input to this command would be the most recent name of
the file - otherwise, I would have to remember the old name, which could have
been from a long time ago.

Perhaps there is some combination of revset functions that can achieve this?
I'd be curious to know.


Repro:

$ hg --version
Mercurial Distributed SCM (version 6.1.1+hg12.90e564882f07)

$ export HGPLAIN=1

$ hg ini test2
$ cd test2
$ echo "initial data" > foo.txt
$ hg add
adding foo.txt
$ hg ci -m "initial file"

$ echo "blabla" >> foo.txt 
$ hg ci -m "some edit"

$ hg mv foo.txt bar.txt
$ hg ci -m "moved foo to bar"

$ echo "moretext" >> bar.txt 
$ hg ci -m "edited as bar"
$ hg log

 # shows full history of 4 changesets

$ hg rm bar.txt
$ hg ci -m "removed bar"
$ hg log bar.txt

 # shows 2 changes: the rename of foo->bar, and the first edit of bar. This is
a bit unintuitive to me on its own, but not my main complaint.

$ hg log --follow bar.txt
abort: cannot follow file not in parent revision: "bar.txt"

$ hg log --rev "follow('bar.txt')"

 # (no output)

$ hg log --removed bar.txt

 # shows 3 changes: rename, edit, removal (of bar.txt)

$ hg log --rev "file('bar.txt')"

 # same 3 changes as above

$ hg log --follow --removed bar.txt

 # same 3 changes (!) This is the bug, IMO.

hg log --rev "follow('bar.txt', removes('bar.txt'))"

 # no results. Seems contrary to the 'hg help revset' documentation.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6682] New: Why Cash App Won't Let Me Send Money And How Can I Annihilate It?

2022-04-27 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6682

Bug ID: 6682
   Summary: Why Cash App Won't Let Me Send Money And How Can I
Annihilate It?
   Product: Mercurial
   Version: default branch
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: automv
  Assignee: bugzi...@mercurial-scm.org
  Reporter: ana1997j...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

If the Cash App server is down or you have a low balance in your Cash App
account, Cash App Won't Let Me Send Money. For getting rid of all such
happenings and loopholes permanently from the root, you have to make proper
utilization of the Cash App support without wasting your time. 
https://www.techjaadu.com/blog/cash-app-wont-let-me-send-money/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6681] New: How Can I Deal With The Situation If Cash App Payment Failed For My Protection?

2022-04-27 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6681

Bug ID: 6681
   Summary: How Can I Deal With The Situation If Cash App Payment
Failed For My Protection?
   Product: Mercurial
   Version: default branch
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: automv
  Assignee: bugzi...@mercurial-scm.org
  Reporter: jw918...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

All you need to do is to have a word with the troubleshooting professionals who
will make you understand why Cash App Payment Failed For My Protection in a
hassle-free manner. However, you don’t need to take stress as you will clarify
all your doubts and concerns without any hassle. 
https://www.techjaadu.com/blog/how-do-i-fix-my-cash-app-failed-for-my-protection/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6680] New: distutils warning breaks test

2022-04-27 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6680

Bug ID: 6680
   Summary: distutils warning breaks test
   Product: Mercurial
   Version: 6.1.1
  Hardware: All
OS: NetBSD
Status: UNCONFIRMED
  Severity: bug
  Priority: wish
 Component: Mercurial
  Assignee: bugzi...@mercurial-scm.org
  Reporter: t...@giga.or.at
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

I have seen this test failure in mercurial 6.1.1 with python 3.10.4 and
setuptools-62.1.0:

---
/scratch/devel/py-mercurial/work/mercurial-6.1.1/tests/test-demandimport.py.out 
+++
/scratch/devel/py-mercurial/work/mercurial-6.1.1/tests/test-demandimport.py.err 
@@ -0,0 +1,4 @@ 
+/usr/pkg/lib/python3.10/site-packages/_distutils_hack/__init__.py:17:
UserWarning: Distutils was imported before Setuptools, but importing Setuptools
also replaces the `distutils`
 module in `sys.modules`. This may lead to undesirable behaviors or errors. To
avoid these issues, avoid using distutils directly, ensure that setuptools is
installed in the tradit
ional way (e.g. not an editable install), and/or make sure that setuptools is
always imported before distutils. 
+  warnings.warn(   
+/usr/pkg/lib/python3.10/site-packages/_distutils_hack/__init__.py:30:
UserWarning: Setuptools is replacing distutils.
+  warnings.warn("Setuptools is replacing distutils.")  

ERROR: test-demandimport.py output changed

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


[Bug 6679] New: How To Get A Treatment If Cash App Payment Failed For My Protection?

2022-04-27 Thread mercurial-bugs
https://bz.mercurial-scm.org/show_bug.cgi?id=6679

Bug ID: 6679
   Summary: How To Get A Treatment If Cash App Payment Failed For
My Protection?
   Product: Mercurial
   Version: unspecified
  Hardware: PC
OS: Windows
Status: UNCONFIRMED
  Severity: feature
  Priority: wish
 Component: bugzilla
  Assignee: bugzi...@mercurial-scm.org
  Reporter: avahop...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---

Are you looking to get the fastest treatment right from the comfort of your
home? All you have to do is to refer to the official help and support section.
In such a case, you have to make a call at the helpline number and you will be
able to get rid of all your problems with Cash App Payment Failed For My
Protection.

https://www.techjaadu.com/blog/how-do-i-fix-my-cash-app-failed-for-my-protection/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel


  1   2   3   4   5   6   7   8   9   10   >