Howdy, how doth one do this?

1. I exported from git into new fossil repo.
2. created 2 repos on Chisel - one with "override project code" set to some random string (didn't know what else to put there) and one leaving it blank.
3. fossil push <url>

Pushing to either chisel repo results in:

                Bytes      Cards  Artifacts     Deltas
Sent:             158          1          0          0
processed: 38%
Error: login failed
Received:          52          1          0          0
Pull done, sent: 391  received: 318  ip: 74.208.146.128

I've tried giving every capability to my user in both the local and remote repos, verified passwords (I can clone the remote... well one of them, see below), and disabled firewalls (running Win10 through WSL). Also tried the native windows client as well as a linux vm - the result is identical each time.

The output is bizarre, it's like it half works (similar result when running pull) but nothing appears on the remote.

I would assume the "override code" repo should be the-way-to-go but the error is the same, with the addition of this error when cloning:

Round-trips: 1   Artifacts sent: 0  received: 0
unknown command: [push]

Round-trips: 2   Artifacts sent: 0  received: 1
unknown command: [push]

Round-trips: 2   Artifacts sent: 0  received: 2
Clone done, sent: 628  received: 4621  ip: 74.208.146.128
server returned an error - clone aborted

I've spent all day trying to troubleshoot this and scour (what little exists) on the web - please have pity on my soul (my first attempt at using fossil).

one with "override project code" set to some random string (didn't know what else to put there)

This needs to be set to the project code from the Fossil repo created from the git repo.

Fossil uses the project code during sync'ing to verify the 2 repos are for the same project.

Also, you need to make sure your primary user ID on your local Fossil repo is also present on the Chisel hosted repo and has commit permission.

Ah, gees, I knew it had to be simple. It would be handy if the import command spat out the project-code, and to mention it's usage on the git import page, too. The only docs that mention it are not very illuminating on this particular usage - which, coming from git, is likely to be the first thing you'll want to do post import.

Thanks for your help, all working now.

make sure your primary user ID on your local Fossil repo is also present on the Chisel hosted repo and has commit permission

PS: to anyone encountering this in the future you can just use the remote user ID (and password) for less hassle.

Hi, geburashka,

Perhaps, this would help:

http://chiselapp.com/user/aplsimple/repository/HOWTO_chisel/index

---

Привет, Чебурашка!

Может, поможет этот док:

http://chiselapp.com/user/aplsimple/repository/HOWTO_chisel/doc/trunk/doc/www/chisel_ru.html

Пока! Крокодил Гена.

Unfortunately, that document says to leave Project Code Override blank.

That is fine when you are right at the start of a project. In which case, you clone from the Chisel hosted repo and make your commits to the local clone.

If you already have made any commits, even just 1, you need to set the Project Code of the Chisel hosted repo to match the existing repo when creating it.

That's correct, it's odd why that page doesn't explain why, or more importantly how/where, to get the project-code.

The fossil error message could be less misleading, too.

Привет! I was just reading up on some of your Tcl tools, pretty cool :).

Unfortunately that's exactly the page I was following - a short explanation about the project-code would help save lives!

I assume you can import arbitrary artifacts into any repo provided you override their project-code to match...?

All I had to do after that was to shun the automatic initial commit by chisel and rebuild/reclone to get a 'pristine' trunk/master.

See also this thread.

Possibly, the fossil gurus would advise something valuable to you.

means that you can only create NEW-REPOSITORY from exported data

Actually, only the initial import needs to be to a new repo. After that, you can perform additional, incremental imports:

    --incremental     allow importing into an existing repository

Maybe this could be used to trick Fossil into importing into an unrelated, existing repo. I don't know. Not that I would recommend doing that.