Yes, clearly this is a malformed manifest. Fossil should have never
generated this manifest. It is clearly a bug.
How did you say it came to be? A git import?
On Wed, Oct 8, 2014 at 10:29 AM, Tomek Kott <tkott.onl...@outlook.com>
wrote:
> The result is:
>
> ERROR: line 21: T-card in the wrong order
>
>
> The file itself is attached. Looks like a potential duplicate Tag? Though
> if I delete that then the check-sum doesn't match....
>
> Forgot to mention the client computer has: This is fossil version 1.29
> [3e5ebe2b90] 2014-06-12 17:25:56 UTC
>
> Tomek
>
> ------------------------------
> From: d...@sqlite.org
> Date: Wed, 8 Oct 2014 10:23:16 -0400
> Subject: Re: [fossil-users] parent/root disappeared
> To: fossil-users@lists.fossil-scm.org
> CC: tk...@outlook.com
>
>
>
>
> On Wed, Oct 8, 2014 at 10:15 AM, Tomek Kott <tkott.onl...@outlook.com>
> wrote:
>
> Hi all,
>
> I have a repository that was (once upon a time) a former git repository. I
> just noticed, upon cloning to a new computer, that the root checkin is no
> longer showing up in the timeline. I'll be a bit more specific, judging
> from the artifacts I've found upon deconstruction etc. There are two
> computers, call them server and client.
>
> On the server, I see a checkin 31e481e120f0, whose manifest lists the 'P'
> card (parent, I assume) as '7116833a14'. This checkin does not show up in
> the timeline on the server. When I deconstruct the fossil repository, I can
> see the manifest for that checkin, and the checkin comment states "Initial
> commit" or some such with no other P card.
>
>
> Please save off the 7116833a14 manifest into a file. (You can perhaps use
> "fossil 7116833a14 test.txt" to do this.) Then run "fossil
> test-parse-manifest test.txt" and let us know what you see as a result.
>
> Or, email the test.txt file.
>
>
>
> On the client (after clone), I DON'T SEE 31e481e12, only its next
> available child. All the data is still obviously there after
> deconstruction, although it still doesn't appear after reconstructing from
> the artifacts.
>
> I've tried rebuild (using --randomize and not) with no luck. I'm guessing
> that I've simply run into a very odd git-influenced bug of one sort or
> another, but would love to figure out what went wrong.
>
> As a note, I know that at some point I could see the original
> ('7116833...') checking because the client (though oddly not the server)
> lists a tag change in which I added a propagating tag 'trunk' to that
> checkin. So at some point in the past I could see it through the timeline
> and edit it. Maybe something in the intervening rebuilds broke things?
>
> Is there anything else I can do to debug the issue?
>
> Thanks,
>
> Tomek
> PS. Please CC me on responses since I get digests, so I will be delayed in
> responding otherwise.
>
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
>
>
> --
> D. Richard Hipp
> d...@sqlite.org
>
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
