Maybe this shoud be reported as bug?

ST

On Wed, 2012-03-21 at 11:05 -0400, Tomek Kott wrote:
> I've noticed that myself, so I never to 'fossil config export all'. I
> only export 'tickets' or 'skins' usually, so not a big deal. I avoid
> every pulling / pushing the users table.
> 
> Tomek
> 
> On Wed, Mar 21, 2012 at 7:20 AM, ST <[email protected]> wrote:
>         On Tue, 2012-03-20 at 08:27 -0400, Richard Hipp wrote:
>         >
>         >
>         > On Tue, Mar 20, 2012 at 6:19 AM, ST <[email protected]>
>         wrote:
>         >         Hi,
>         >         1) I've just configured my first fossil repo and now
>         would
>         >         like to copy
>         >         this configuration to other projects. Is it
>         possible?
>         >         Most problematic part is enabling "assigned_to" and
>         >         "opened_by" in
>         >         tickets as per this:
>         >
>         http://fossil-scm.org/index.html/doc/trunk/www/custom_ticket.wiki . 
> Why
>         >         isn't it actually there out of the box? Or it is
>         there and I
>         >         just missed
>         >         it? It is a bit painful to go through this process
>         for all the
>         >         project
>         >         that I have...
>         >
>         > On the repo you've already set up:
>         >
>         >      fossil configuration export all config.txt -R
>         alreadysetup.fossil
>         >
>         > Then on your new repo:
>         >
>         >     fossil configuration import config.txt -R newrepo.fossil
>         >
>         > All the configuration information is transferred through the
>         filed
>         > "config.txt" in the example above.  That file is pure SQL so
>         it is
>         > ASCII text and readable.  You can move the file across
>         systems in
>         > between the two operations, if you need to.
>         >
>         > If you only want to transfer some subset of the
>         configuration, you can
>         > replace "all" by "email", "project", "shun", "skin",
>         "ticket", or
>         > "user".
>         
>         
>         I tried that but after this I can no longer login neither with
>         my
>         password from alreadysetup.fossil nor with the default
>         password
>         generated by fossil which was created during repo
>         initialization.
>         
>         Thank you,
>         ST
>         
>         
>         _______________________________________________
>         fossil-users mailing list
>         [email protected]
>         http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>         
> 
> _______________________________________________
> fossil-users mailing list
> [email protected]
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to