Comment 3 for bug 1852789

The original trunk repo was created by breezy?

What happens if you run 'git fsck' in it?

On 18 November 2019 11:54:51 GMT-08:00, Sam Bull <email address hidden> wrote:
>Output from git:
>> git clone trunk test123
>Cloning into 'test123'...
>done.
>
>hint: The remote resolves to a file:// URL, which can only work with a
>hint: standalone transfer agent. See section "Using a Custom Transfer
>Type
>hint: without the API server" in custom-transfers.md for details.
>
>hint: The remote resolves to a file:// URL, which can only work with a
>hint: standalone transfer agent. See section "Using a Custom Transfer
>Type
>hint: without the API server" in custom-transfers.md for details.
>^Cwarning: Clone succeeded, but checkout failed.
>You can inspect what was checked out with 'git status'
>and retry the checkout with 'git checkout -f HEAD'
>
>
>Exiting because of "interrupt" signal.
>
>
>--
>
>So, it hung (and I used Ctrl+C after a few minutes), although it looked
>like the files were there. So, it performed better than breezy, but
>still got stuck. I guess that means breezy managed to corrupt the repo
>in some way.
>
>--
>You received this bug notification because you are subscribed to
>Breezy.
>https://bugs.launchpad.net/bugs/1852789
>
>Title:
> branch zlib error
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/brz/+bug/1852789/+subscriptions