Re: [fossil-users] fast-export to git produces unimportable dump

[Svyatoslav Mishyn]

(Wed, 12 Oct 11:50) Richard Hipp:
> My guess:  Git does not allow more than a single instance of the tag
> named "one".  In other words, all tags must be unique in Git.

yet another Git limitation


-- 
I am not a native English speaker,
so feel free to correct any spelling or grammatical errors!


signature.asc
Description: PGP 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] fast-export to git produces unimportable dump

[Richard Hipp]

On 10/12/16, Svyatoslav Mishyn  wrote:
> (Thu, 13 Oct 00:19) Osamu Aoki:
>> I have no idea for "error: Multiple updates for ref ..." but at least
>> git repo is usable one after executing "git checkout trunk".
>
> to reproduce that error:
> /home/juef/fossil/test: f co trunk
> /home/juef/fossil/test: date >> z && f ci -m t1 --tag one --tag two
> /home/juef/fossil/test: date >> z && f ci -m b1 --tag one --tag two --branch
> br
> /home/juef/fossil/test: f2g test
> Unpacking objects: 100% (7/7), done.
> error: multiple updates for ref 'refs/tags/one' not allowed.

My guess:  Git does not allow more than a single instance of the tag
named "one".  In other words, all tags must be unique in Git.

-- 
D. Richard Hipp
d...@sqlite.org
___
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] fast-export to git produces unimportable dump

[Svyatoslav Mishyn]

(Thu, 13 Oct 00:19) Osamu Aoki:
> I have no idea for "error: Multiple updates for ref ..." but at least
> git repo is usable one after executing "git checkout trunk".

to reproduce that error:
/home/juef/fossil/test: f co trunk
/home/juef/fossil/test: date >> z && f ci -m t1 --tag one --tag two
/home/juef/fossil/test: date >> z && f ci -m b1 --tag one --tag two --branch br
/home/juef/fossil/test: f2g test
Unpacking objects: 100% (7/7), done.
error: multiple updates for ref 'refs/tags/one' not allowed.


-- 
I am not a native English speaker,
so feel free to correct any spelling or grammatical errors!


signature.asc
Description: PGP 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] fast-export to git produces unimportable dump

[Osamu Aoki]

Hi,

On Mon, Oct 10, 2016 at 02:32:51PM +0900, Osamu Aoki wrote:
> On Mon, Oct 10, 2016 at 10:38:45AM +0900, Osamu Aoki wrote:
> ...
> > commit refs/heads/test_ticket_d17d6e5b17
> > mark :37455
> > committer jan.nijtmans  1353531216 +
> > data 82
> > Just commit some weird filenames, even one with a newline in it, to
> ^^^
> > test the code.
>   ^
> 
> Now I realize.
> 
> > from :37577
> > M 100644 :1050 :abc
> > M 100644 :37588 abc
> > def.txt
> 
> I see this should have been "abc\ndef.txt" instead of "abc", real NL
> and "def.txt".
> 
> I tested "git fast-export" with filename with NL in it.
...

I made a proof of concept patch for export after reading the git code
and it works OK.  (Escaping is not just " " and control code.  It also
escaped UTF-8 high bit codes.)

$ fossil export --git ../fossil.fsl | git fast-import
error: Multiple updates for ref 'refs/tags/json_add_tag_test' not allowed.
git-fast-import statistics:
-
Alloc'd objects:  55000
Total objects:50520 (  2996 duplicates  )
  blobs  :19491 ( 0 duplicates  15079 deltas of  
18632 attempts)
  trees  :21041 (  2996 duplicates  18791 deltas of  
19186 attempts)
  commits: 9915 ( 0 duplicates  0 deltas of 
 0 attempts)
  tags   :   73 ( 0 duplicates  0 deltas of 
 0 attempts)
Total branches: 556 (   982 loads )
  marks:1048576 ( 29406 unique)
  atoms:935
Memory total:  4813 KiB
   pools:  2235 KiB
 objects:  2578 KiB
-
pack_report: getpagesize()=   4096
pack_report: core.packedGitWindowSize = 1073741824
pack_report: core.packedGitLimit  = 8589934592
pack_report: pack_used_ctr=   6615
pack_report: pack_mmap_calls  =   1725
pack_report: pack_open_windows=  1 /  1
pack_report: pack_mapped  =  115842232 /  115842232
-

I have no idea for "error: Multiple updates for ref ..." but at least
git repo is usable one after executing "git checkout trunk".

Osamu
___
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] fast-export to git produces unimportable dump

[Ross Berteig]

Some aggressive pr0n-selling spammer is subscribed either directly or 
through an archive site. They are making a sequence of replies directly 
to the original poster, some just plain text, some including a link to 
follow, and some containing NSFW photographs. I've had pretty good luck 
with a black-list approach, where I've told my mail system to blacklist 
the domains the pr0n spam appears to come from. We'll see if this 
message catches some more fodder for my black-list.


I don't have a good answer for what else to do about it. This is a 
particularly pernicious approach to address harvesting that does not 
lend itself well to discovery and mitigation.


On 10/11/2016 1:22 PM, sky5w...@gmail.com wrote:

Can confirm with gmail. Every post now has multiple spam replies.
Fossil has been discovered!


I suspect religiously reporting the offending email as spam to GMail 
will help in the long run.


--
Ross Berteig   r...@cheshireeng.com
Cheshire Engineering Corp.   http://www.CheshireEng.com/
+1 626 303 1602

___
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] fast-export to git produces unimportable dump

[sky5walk]

Can confirm with gmail. Every post now has multiple spam replies.
Fossil has been discovered!
___
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] fast-export to git produces unimportable dump

[Andy Bradford]

Thus said Osamu Aoki on Mon, 10 Oct 2016 14:32:51 +0900:

> PS: Immediately after posing here, I got many replies from SPAM :-(

I post  quite often and  never see any  SPAM. Maybe Gmail's  filters are
breaking down?

Andy
-- 
TAI64 timestamp: 400057fb3706


___
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] fast-export to git produces unimportable dump

[Osamu Aoki]

On Mon, Oct 10, 2016 at 10:38:45AM +0900, Osamu Aoki wrote:
...
> commit refs/heads/test_ticket_d17d6e5b17
> mark :37455
> committer jan.nijtmans  1353531216 +
> data 82
> Just commit some weird filenames, even one with a newline in it, to
^^^
> test the code.
  ^

Now I realize.

> from :37577
> M 100644 :1050 :abc
> M 100644 :37588 abc
> def.txt

I see this should have been "abc\ndef.txt" instead of "abc", real NL
and "def.txt".

I tested "git fast-export" with filename with NL in it.

| commit refs/heads/master
| mark :4
| author Osamu Aoki  1476073435 +0900
| committer Osamu Aoki  1476073435 +0900
| data 7
| update
| from :2
| M 100644 :3 "foo\nbar.txt"

It generate file like this.  So when ever you see NL, this escaping
needs to happen and they are always double quoted (normally there are no
double quote).  Quick check indicates:

NL QUOTED "\n"
TABQUOTED "\t"
\  QUOTED "\\"
SPACE  QUOTED " "

For example
| M 100644 :8 "space space.txt"

"fossil export" and "fossil import" need to support these features.

As I read git-ls-files manpage, its OUTPUT has following content:

 When -z option is not used, TAB, LF, and backslash characters in
 pathnames are represented as \t, \n, and \\, respectively.

So at least addressing above 4 cases should do good.

  if filename_has_specials(filenamestring)
filenamestring = quote_and_escape(filenamestring);

Osamu

PS: Immediately after posing here, I got many replies from SPAM :-(
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users