Re: [fossil-users] Is fossil export known to be broken?

[org.fossil-scm.fossil-users]

On 2015-12-12T16:06:20 -0800
jungle Boogie  wrote:
> 
> Great news!
> 
> Did you happen to change your git version at all during either test?

Nope, same version all along (2.6.2).

M
___
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] Is fossil export known to be broken?

[Martin Gagnon]

On Sun, Dec 13, 2015 at 02:12:01PM +0100, Piotr Orzechowski wrote:
> I've just looked at release notes for 1.34 and 1.33 and there was no
> straightforward note about need to rebuild repositories. Maybe it would
> be better to add such information to requiring release notes, or maybe
> even fossil would be able to suggest repo rebuilding itself?
> 

After bisecting, I found that this commit:
  http://www.fossil-scm.org/index.html/info/8e44cf6f4df4f9f0

Fix the problem. 

Since this fix is about mlink table and not on the export command
directly, updating fossil is not enought to solve the problem, but it
require a rebuild.

Probably a note could be added to the 1.34 release notes.

regards,

-- 
Martin G.
___
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] Is fossil export known to be broken?

[Piotr Orzechowski]

I've just looked at release notes for 1.34 and 1.33 and there was no
straightforward note about need to rebuild repositories. Maybe it would
be better to add such information to requiring release notes, or maybe
even fossil would be able to suggest repo rebuilding itself?

Pozdrawiam / With best regards,
Orzech

W dniu 13.12.2015 o 12:23, org.fossil-scm.fossil-us...@io7m.com pisze:
> On 2015-12-12T16:06:20 -0800
> jungle Boogie  wrote:
>> Great news!
>>
>> Did you happen to change your git version at all during either test?
> Nope, same version all along (2.6.2).
>
> M
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




signature.asc
Description: OpenPGP digital signature
___
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] Is fossil export known to be broken?

[jungle Boogie]

On 13 December 2015 at 05:12, Piotr Orzechowski  wrote:
> I've just looked at release notes for 1.34 and 1.33 and there was no
> straightforward note about need to rebuild repositories.


Admittedly I don't do it every time, but I thought that was something
to be done for every update?


Here's openBSD's port advising it's a good idea to run rebuild:
http://openports.se/devel/fossil

After upgrading to a newer version of fossil, it is always a good idea
to run: "fossil all rebuild". Running "rebuild" this way is not always
necessary, but it never hurts.



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
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] Is fossil export known to be broken?

[Piotr Orzechowski]

I guess it would be better to change help message about rebuild then.
As of now, it says "Run this command after updating the fossil
executable in a way that changes the database schema." So I would
expect to see some information about such need in release notes.
Perhaps it would be better to add to help that it is a good practice
to run this command after each update. But then, why wouldn't rebuild
happen automatically?

Pozdrawiam / With best regards,
Orzech

W dniu 13.12.2015 o 18:00, jungle Boogie pisze:
> On 13 December 2015 at 05:12, Piotr Orzechowski  wrote:
>> I've just looked at release notes for 1.34 and 1.33 and there was no
>> straightforward note about need to rebuild repositories.
>
> Admittedly I don't do it every time, but I thought that was something
> to be done for every update?
>
>
> Here's openBSD's port advising it's a good idea to run rebuild:
> http://openports.se/devel/fossil
>
> After upgrading to a newer version of fossil, it is always a good idea
> to run: "fossil all rebuild". Running "rebuild" this way is not always
> necessary, but it never hurts.
>
>
>




signature.asc
Description: OpenPGP digital signature
___
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] Is fossil export known to be broken?

[Joerg Sonnenberger]

On Sun, Dec 13, 2015 at 09:57:44PM +0100, Piotr Orzechowski wrote:
> I guess it would be better to change help message about rebuild then.
> As of now, it says "Run this command after updating the fossil
> executable in a way that changes the database schema." So I would
> expect to see some information about such need in release notes.
> Perhaps it would be better to add to help that it is a good practice
> to run this command after each update. But then, why wouldn't rebuild
> happen automatically?

I wouldn't advise to run it after every update, especially for large
repos. On something like NetBSD's src.fossil, it can take hours even on
a fast machine.

Joerg
___
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] Is fossil export known to be broken?

[Piotr Orzechowski]

Thanks for clarifying that. So I guess it would be either release note
advise or schema change notification when running maybe even
any command, if it was up to me. ;)

Pozdrawiam / With best regards,
Orzech

W dniu 13.12.2015 o 22:58, Joerg Sonnenberger pisze:
> I wouldn't advise to run it after every update, especially for large
> repos. On something like NetBSD's src.fossil, it can take hours even on
> a fast machine.
>
> Joerg
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




signature.asc
Description: OpenPGP digital signature
___
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] Migrating github issues to fossil

[Tim Johnston]

Thanks a lot for the help.

I ended up building myself something in python to do the following:
1) Pull down the github issues from their API with curl (based on
http://www.fullo.net/blog/2012/06/25/export-github-issues-as-csv-with-v3-api/
).
2) Make 'fossil ticket add' comments (like your Perl)
-> after filtering out unwanted columns, cleaning up escaped characters and
all sorts of other annoying details. (for what it's worth, the python
library 'pandas' was really helpful here)

It worked out nicely, and now I'm really close to ditching all my github
stuff. Awesome!



On Wed, Dec 2, 2015 at 9:50 PM, Ron W  wrote:

> On Wed, Dec 2, 2015 at 5:08 PM, Tim Johnston  wrote:
>
>> I'm wondering about migrating my github 'issues' and turning them into
>> fossil 'tickets'. Does anyone have experience with this? Any
>> recommendations for approaching it?
>>
>
> I can't help with parsing the github tickets, but I can make suggestions
> for automating creation of Fossil tickets.
>
> See "fossil help ticket" for a description of the CLI to Fossil tickets.
> Note that the ticket CLI doesn't perform any TH1/TCL processing you might
> define in the ticket setup via the GUI. What you specify for the fields and
> values will be what gets put in to the tickets created this way.
>
> Here's a partial Perl program to process 1 ticket:
>
> #!Perl
> use strict;
> use warnings;
>
> # List of ticket fields in Fossil (Default fields with addition of gh_id
> to hold the github ticket id. Modify for your needs.)
> my @FossilFields = qw/gh_id title status severity priority resolution
> subsystem private_contact foundin username comment/;
> # List of ticket fields in github project. Use same order as corresponding
> Fossil ticket fields. Modify for your project.
> my @GhFields = qw/id title status severity priority resolution subsystem
> private_contact foundin username comment/;
>
> my %mapGh2F;
> my $i = 0;
> for my $n (@GhFields)
> {
> $mapGh2F{$n} = @FossilFields[$i++];
> }
>
> my %FieldsValues;
>
> # code to parse github ticket record goes here, inserting extracted values
> into %FieldsValues
>
> # build Fossil command to add ticket
> my @cmd = qw/fossil ticket add/;
>
> # might need to: push@cmd, "-q";
> # if needed, make sure ticket parser quotes (escapes) certain character as
> described in "fossil help ticket"
>
> for my $n (@FossilFields)
> {
> push @cmd, $n;
> push @cmd, $FieldsValues{$n};
> }
>
> # now, run it (the following is roughly equivalent, in C, to:
> execvp(cmd[0], cmd);
> system @cmd;
>
>
> ___
> 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