From the paths, it looks like those files are in the spec tests for one of the 
Saxon gems, so I don’t think this is a required file in production: those tests 
aren’t going to be run. I don’t know if there is a simple way to filter these 
sorts of files out of the production build.

archivesspace-v1.5.1$ find . -name '*_*_*_*.yml' -print

On Sep 19, 2016, at 10:23 AM, Reese, Terry P. 
<<>> wrote:

Certain versions of windows have file length limits that are enforced with 
Explorer.  If you are unzipping – you might try creating a folder at the C-root 
and see if that gives you enough characters.

There is a post on the listserv (can’t find it right now) about some advice for 
dealing with this issue after unzipping.


 []On Behalf Of 
Bowman, George
Sent: Monday, September 19, 2016 10:15 AM
To: '' 
Subject: [Archivesspace_Users_Group] paths too long to unzip?

I’m trying to unzip the ArchivesSpace 1.51, and I get errors on two .yml files 
in the zip-file.

The only option I have is to skip them and move on.  I’d like to go back to the 
zip and find them and copy them out individually, but I can’t seem to search 
the zip – there is some windows trick that is eluding me.

The two files having really long path names (path + filename) are


Has anybody else gotten around this problem?  Or does anybody know where in the 
filestructure they live, so I can get them out of the zip-file?  Do the names 
really have to be this long?


n  George Bowman
n  Library and Archives Systems Support Branch
n  Collections Systems Division, OCIO
n  Smithsonian Institution

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group mailing list

Reply via email to