[Unison-hackers] the unison [0-9]*.* bug

[Benjamin Pierce]

Yes.  I believe it's fixed in the new beta release.

    - B


On May 4, 2009, at 10:42 AM, Claudio wrote:

> Thanks, that's right. When unsetting my backup options and running
> unison again, it didn't leave out any files.
>
> My prior backup settings are as follows.
> ,---
> | backuplocation = central
> | backupdir = /home/claudio/.unison/backup
> | backup = Name *
> | backupprefix = $VERSION.
> | backupsuffix =
> `---
>
> There is no logical reason for assuming that any file outside the
> 'backupdir' is a backup file (and to ignore it though not told to do  
> so
> by ignore directives). Nor is this behaviour documented.
>
> IMO that is a bug.
>
> Claudio
>
> On Tue, Apr 28, 2009 at 05:40:29PM -0400, Benjamin Pierce wrote:
>> Probably you have a "backup" preference set to something beginning
>> with the backup prefix (which is a number).  Unison tries to ignore
>> backup files...
>>
>>    - B
>>
>> On Apr 28, 2009, at 5:32 PM, Claudio wrote:
>>> I've encountered the behaviour that unison ignores some files even  
>>> if
>>> there isn't a single "ignore" directive(!). For example those files
>>> are
>>> affected:
>>>
>>> 1237678487.000102.mbox:2,S
>>> 20._Geburtstag
>>> 05.HTM
>>> 400.html
>>> 04.03.tar.gz
>>> 2.
>>> 3.3
>>> 4.foo
>>> 55.bar
>>>
>>> unison version 2.27.57 (shipped with ubuntu)
>>>
>>> So it doesnt sync my mails in ~/Maildir and a huge amount other
>>> documents. I found a creepy workaround:
>>>
>>> ignorenot = Name [0-9]*.*
> _______________________________________________
> Unison-hackers mailing list
> Unison-hackers at lists.seas.upenn.edu
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers