Related to my previous question...
But if no solution for that is forthcoming... one solution would be to
update to the changeset before the one that did the last "hg copy" and redo
and prune that that changeset .
But the question then becomes... how do I find all hg copy's?
--
This
On 4/28/22 5:58 PM, Dennis Lee Bieber wrote:
On Thu, 28 Apr 2022 16:12:16 -0700, Ernie Rael declaimed
the following:
check around these? Not with an editor I think...
evoext_obshashrange_v2.sqlite: SQLite 3.x database, last written using
SQLite version 3035005
evoext_stablerange_v2.sqlite:
I'm getting some very uncomfortable merges due to using a combination of hg
copy and hg rebase.
What seems to be happening is when I rebase, changes that were made to the
file that was copied from (after the copy), are being now applied to the
destination file when I rebase.
Is there a way of
On 4/28/22 12:46 PM, Anton Shestakov wrote:
Looks like either another process is holding a lock on caches or the
FS doesn't support locking mechanisms that sqlite3 needs.
If you want to dig further into this, check around these files:
.hg/cache/evoext_stablerange_v2.sqlite and
On 4/28/22 12:46 PM, Anton Shestakov wrote:
Looks like either another process is holding a lock on caches or the
FS doesn't support locking mechanisms that sqlite3 needs.
If you want to dig further into this, check around these files:
.hg/cache/evoext_stablerange_v2.sqlite and
> On Apr 28, 2022, at 3:46 PM, Anton Shestakov wrote:
>
> Looks like either another process is holding a lock on caches or the
> FS doesn't support locking mechanisms that sqlite3 needs.
>
> If you want to dig further into this, check around these files:
>
Looks like either another process is holding a lock on caches or the
FS doesn't support locking mechanisms that sqlite3 needs.
If you want to dig further into this, check around these files:
.hg/cache/evoext_stablerange_v2.sqlite and
.hg/cache/evoext_obshashrange_v2.sqlite
Oh, interesting. Maybe we could get away with "whatever MSRV Firefox uses"
as a baseline?
On Thu, Apr 28, 2022 at 10:38 AM Julien Cristau wrote:
> On Thu, Apr 28, 2022 at 10:29:21AM -0400, Augie Fackler wrote:
> > I think Debian (at least) has a mechanism to build packages with a newer
> rustc
mharbison72 created this revision.
Herald added a reviewer: hg-reviewers.
Herald added a subscriber: mercurial-patches.
REVISION SUMMARY
PyOxidizer binaries are built with py 3.9.6, so not even Windows 7 is
supported.
Unfortunately, there don't appear to be more recent values for newer
mharbison72 created this revision.
Herald added a reviewer: hg-reviewers.
Herald added a subscriber: mercurial-patches.
REPOSITORY
rHG Mercurial
BRANCH
default
REVISION DETAIL
https://phab.mercurial-scm.org/D12595
AFFECTED FILES
contrib/packaging/wix/mercurial.wxs
Alphare created this revision.
Herald added a reviewer: hg-reviewers.
Herald added a subscriber: mercurial-patches.
REVISION SUMMARY
This is replaced by the more complete `--docket` option to `debugstate`.
REPOSITORY
rHG Mercurial
BRANCH
stable
REVISION DETAIL
Alphare created this revision.
Herald added a reviewer: hg-reviewers.
Herald added a subscriber: mercurial-patches.
REVISION SUMMARY
This is useful information that we don't easily have access to currently,
unless you speak fluent xxd.
This replaces `debugdirstateignorepatternshash`,
Alphare created this revision.
Herald added a reviewer: hg-reviewers.
Herald added a subscriber: mercurial-patches.
REVISION SUMMARY
As per the previous patch, the counter was incorrectly carried over from the
old docket when it should be reset for a complete rewrite.
REPOSITORY
rHG
Alphare created this revision.
Herald added a reviewer: hg-reviewers.
Herald added a subscriber: mercurial-patches.
REVISION SUMMARY
This was picked up by @aalekseyev when doing unrelated debugging.
The Rust implementation was never resetting this counter, so a brand new file
would carry
Alphare created this revision.
Herald added a reviewer: hg-reviewers.
Herald added a subscriber: mercurial-patches.
REVISION SUMMARY
This is more robust.
REPOSITORY
rHG Mercurial
BRANCH
stable
REVISION DETAIL
https://phab.mercurial-scm.org/D12592
AFFECTED FILES
tests/test-dirstate.t
On Thu, Apr 28, 2022 at 10:29:21AM -0400, Augie Fackler wrote:
> I think Debian (at least) has a mechanism to build packages with a newer
> rustc than they actually distribute.
>
I don't think we do. :)
E.g. we had to add a rustc-mozilla package to Debian stable when moving
from firefox ESR 78
I think Debian (at least) has a mechanism to build packages with a newer rustc
than they actually distribute.
(Note that both your messages got marked as spam for me!)
> On Apr 27, 2022, at 5:56 AM, Raphaël Gomès wrote:
>
> Hi all,
>
> (Sorry in advance if this mail is a duplicate, we've had
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
On 4/28/22 6:16 AM, Scott Palmer wrote:
Scott
On Apr 28, 2022, at 9:01 AM, Ernie Rael wrote:
On 4/28/22 12:59 AM, Anton Shestakov wrote:
There are also --debug and --profile, maybe they can help. Although
some parts of the push process may not have debug logging, and
profiling is for when
Scott
> On Apr 28, 2022, at 9:01 AM, Ernie Rael wrote:
>
> On 4/28/22 12:59 AM, Anton Shestakov wrote:
>> There are also --debug and --profile, maybe they can help. Although
>> some parts of the push process may not have debug logging, and
>> profiling is for when you wish to delve into
On 4/28/22 12:59 AM, Anton Shestakov wrote:
There are also --debug and --profile, maybe they can help. Although
some parts of the push process may not have debug logging, and
profiling is for when you wish to delve into source code.
I suspect there's something in the setup of the network or
There are also --debug and --profile, maybe they can help. Although
some parts of the push process may not have debug logging, and
profiling is for when you wish to delve into source code.
I suspect there's something in the setup of the network or network
file system, because 1 minute looks like
Hi,
It might be unrelated but I remember I had a similar problem years ago.
It was an IPV6 configuration problem.
Nicolas
Le 27/04/2022 à 16:23, Scott Palmer a écrit :
This is interesting to me. I have a similar issue with pushes to a repo hosted
on a Linux server that uses a
23 matches
Mail list logo
