[fossil-users] Error: wrong project
Hello, I have a fossil repository that I would like to put on chiselapp.com. I cannot upload it because it is larger than 8M. Chiselapp website suggests to create a new project then push to it: Limit 8M in size. If your repository is larger than this, create a new empty project and push to it instead. When I try to push from my current local repository to new on chiselapp, I get this error: Error: wrong project Is there a way to push/pull/sync between unrelated repositories? Thanks. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Error: wrong project
There is a mismatch in the project-codes. Fortunately chiselapp provides functionality to fix this. When creating the repository on chiselapp override the project code with the project-code you get when doing fossil info -R repository. On Tue, Dec 20, 2011 at 11:05 AM, bobef...@free.fr wrote: Hello, I have a fossil repository that I would like to put on chiselapp.com. I cannot upload it because it is larger than 8M. Chiselapp website suggests to create a new project then push to it: Limit 8M in size. If your repository is larger than this, create a new empty project and push to it instead. When I try to push from my current local repository to new on chiselapp, I get this error: Error: wrong project Is there a way to push/pull/sync between unrelated repositories? Thanks. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Error: wrong project
Just a quick reminder, please submit bug reports for chisel at [0]. I don't always watch this list. Thanks. [0] https://chiselapp.com/user/james/repository/chisel On Tue, Dec 20, 2011 at 11:05:26AM +0100, bobef...@free.fr wrote: Hello, I have a fossil repository that I would like to put on chiselapp.com. I cannot upload it because it is larger than 8M. Chiselapp website suggests to create a new project then push to it: Limit 8M in size. If your repository is larger than this, create a new empty project and push to it instead. When I try to push from my current local repository to new on chiselapp, I get this error: Error: wrong project Is there a way to push/pull/sync between unrelated repositories? Thanks. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- James Turner ja...@calminferno.net ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] unexpected results when branching
Hello list, I wanted to checkout how branching works but I got unexpected results. Here is the session. In en empty directory I did: sh-4.1# fossil new test project-id: 788376d693c5a597f327fb01901ab263e333870d server-id: 52a134e7d9d44f546d033b914322a2962da1d756 admin-user: root (initial password is 957271) sh-4.1# fossil open test sh-4.1# touch file1 sh-4.1# fossil add file1 ADDED file1 sh-4.1# fossil commit -m one New_Version: e5eb048857578372dace96a98579b7fd99849b72 sh-4.1# fossil branch new esp trunk gpg: no default secret key: secret key not available gpg: out-E128D037D5A8CDA68BE8: clearsign failed: secret key not available unable to sign manifest. continue (y/N)? y New branch: fa005bdc7d8f72a8d3aa6be4573ddfdad4d857f5 sh-4.1# fossil branch esp * trunk sh-4.1# fossil checkout esp file1 sh-4.1# fossil rm * DELETED file1 sh-4.1# fossil add file1 # nothing added ?! sh-4.1# fossil ls file1 sh-4.1# fossil branch * esp trunk sh-4.1# fossil commit -m two New_Version: 537f08cc487c572a781888c73b4e6d6811fef9a9 sh-4.1# fossil checkout trunk # file1 is there. sh-4.1# fossil checkout esp sh-4.1# fossil ls sh-4.1# # file1 is gone. If I do rm * , then commit, then add file1 again in the new branch, the result is different. I read the archives and the branching tutorial, did I miss something ? (fossil version 1.20) Regards, urban ps. my project is here: http://chiselapp.com/user/jcage/repository/rdk/ Thanks Richard for fossil and James for the web space! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] unexpected results when branching
On Tue, Dec 20, 2011 at 06:02:36PM +, urban wrote: Hello list, I wanted to checkout how branching works but I got unexpected results. Here is the session. In en empty directory I did: sh-4.1# fossil new test project-id: 788376d693c5a597f327fb01901ab263e333870d server-id: 52a134e7d9d44f546d033b914322a2962da1d756 admin-user: root (initial password is 957271) sh-4.1# fossil open test sh-4.1# touch file1 sh-4.1# fossil add file1 ADDED file1 sh-4.1# fossil commit -m one New_Version: e5eb048857578372dace96a98579b7fd99849b72 sh-4.1# fossil branch new esp trunk gpg: no default secret key: secret key not available gpg: out-E128D037D5A8CDA68BE8: clearsign failed: secret key not available unable to sign manifest. continue (y/N)? y New branch: fa005bdc7d8f72a8d3aa6be4573ddfdad4d857f5 sh-4.1# fossil branch esp * trunk sh-4.1# fossil checkout esp file1 sh-4.1# fossil rm * DELETED file1 sh-4.1# fossil add file1 # nothing added ?! sh-4.1# fossil ls file1 sh-4.1# fossil branch * esp trunk sh-4.1# fossil commit -m two New_Version: 537f08cc487c572a781888c73b4e6d6811fef9a9 sh-4.1# fossil checkout trunk # file1 is there. sh-4.1# fossil checkout esp sh-4.1# fossil ls sh-4.1# # file1 is gone. If I do rm * , then commit, then add file1 again in the new branch, the result is different. I read the archives and the branching tutorial, did I miss something ? (fossil version 1.20) You say nothing added?. Right. Nothing added. fossil revert file1 would have brought your file back at that time. Therefore, you commited removal of file1 at commit 'two'. Does this make more sene? Regards, Lluís. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] bug in user handling
On Thu, Dec 15, 2011 at 3:56 PM, Matt Welland estifo...@gmail.com wrote: Based on what I've tried so far fossil ui will *always* choose the first user listed in the user table. None of $USER, --user, -U, default-user in global-config or in config will override fossil ui using the first user listed. I guess this was implemented this way for ticket c9e84b5671 (which I don't think makes necessarily makes sense) so the solution is in fixing clone to add the target user as #1 when cloning from a file. Wouldn't it make more sense for fossil ui to use the logged in user? Also, in fossil server, I agree it would make more sense to default treating local user as super user to off. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
