Call for testing a fix to 2.53.4 RC1 (Re: "Fatal error: Property lists: paths not yet registered!")

Some users have run into a cryptic error "Fatal error: Property lists:
paths not yet registered!" when trying out 2.53.4 RC1 and then downgrading
back to 2.53.3 (or older) -- see below.

This error is caused by an unintentional archive format upgrade present in
RC1. It only affects users who are downgrading back to an older version.
There is now a fix to this, to be merged soon.

Please test the fix at
https://urldefense.com/v3/__https://github.com/bcpierce00/unison/actions/runs/7942180491?pr=999__;!!IBzWLUs!THNkkUg7Gjz2Bf5iJN33YYUSjH_OcVSQQPqleDdXYDc39YHzpQ6ED4jngKRk4DR2v1eD1VwIkKE6NnPzgdtGUg$  (scroll
to bottom to see the builds). After running the fixed build you should be
able to seamlessly downgrade back to 2.53.3. If you're already running the
RC1 build then the fix will also correct the archives transparently.


On Sat, 17 Feb 2024 at 03:06, H. Mijail <[email protected]> wrote:

> OK, thank you.
> I'd suggest that this should be much clearer in the documentation, in the
> error message, and in the moment that the archives are upgraded to the new
> version. Each of those would have helped me understand what's going on
> without wasting the debugging time - and hopefully even stop me from trying
> an RC build.
>
> I had to re-re-read the manual's section on upgrading to find that this
> case is just maybe implicit in there, if you know what to look for; but
> even then looks like the assumption is that a 2.53.3+ RC build is an
> upgrade over 2.53.3, causing incompatible archive changes. Which is rather
> wild to me, particularly in a section that says "As of version 2.52, Unison
> has a degree of backward and forward compatibility'.
>
> Best,
> --- Horacio
>
> On 16 Feb 2024, at 5:08 pm, Tõivo Leedjärv <[email protected]> wrote:
>
> This is a result of downgrading Unison. You've run one of the recent RC or
> debug builds, which upgraded the archives, and now you're running the older
> version again.
>
> On Fri, 16 Feb 2024 at 05:41, H. Mijail Antón Quiles <[email protected]>
> wrote:
>
>> Hi all,
>>
>> I recently got the error in the title and could find no information on
>> how to get rid of it. After looking at the debug output with -debug all and
>> finding nothing useful there either, I deleted the archive files and
>> finally could run unison again.
>> I suspect unison renamed a folder as part of the sync and then tried to
>> apply changes to the old folder.
>>
>> I could post (here or in GitHub) my logs and debug outputs in case they
>> help pinpoint some bug, but they contain paths that I'd prefer to keep
>> private. So, is there any way to post these somewhere non-public? Or
>> anything I can do to anonymize them a bit? Can I e.g. find path1 and
>> replace it with XXX, path2 with YYY, etc?
>>
>> macOS 14.3
>> Unison 2.53.3 (ocaml 4.14.0)
>> Unison 2.53.3 (ocaml 4.14.1) (app version)
>>
>> --
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>>
>
>

-- 
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].