nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cross Platform deployment and case sensitivity

System

OpenDeploy and DataDeploy 5.6 SP1
TS 5.5.2
Are there any known problems while deploying files from Windows(Case insensitive) TS server to Unix web server (case sensitive)?

There are OD clients on the unix box.
Metadata is deployed to database using ddsync.ipl as a DNR script.

If I deploy a file e.g. Index.html to the webserver and later re-name the file as index.html and resubmit, the metadata is not getting updated.

Has anyone encountered this problem?

TIA

Find more posts tagged with

Comments

Migrateduser

There are some mixed case issues when deploying from Unix to Windows. (Relevant bugs are 36970 and 37051.) Not sure if similar problems exist going the other way.

You might want to open a tech support case so that they can reproduce the problem and get a bug on file, if needed.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

DavidMusser

Is this still true in 6.02? Is there no way to get OD to just put one or the other there. Doesn't matter which as it's bad form to have 2 files with the same name on Unix with different cases.

I had a deployment that simply hung on this for over an hour.. Is there a setting to say ignore multiple files with the same name now or anything?

Failure when Deploying from Unix to Windows
Knowledge Base Article: 1825
Type: Tech Note

Synopsis
OpenDeploy may give the error "Ambiguous cross-platform name comparison" when deploying to NT from Unix. This occurs when there are files on the Unix machine with the same filename, but differing in case. The offending Unix files must be deleted.
Details

This problem is causedÂ lack of case sensitivity by Windows. To compensate for this, OpenDeployÂ strips the case sensitivity from the Unix files as well. When there are files with otherwise dissimilar names on the Unix filesystem (ex. Foo.txt and foo.txt) they will end up having the same filename from OpenDeploy's point of view. Because of this, it will not know which file it should be comparing to the version on the server, and it will fail the deploy.

There is no workaround available for this issue. The only viable solution is to remove or rename the conflicting files on the Unix machine so that OpenDeploy will once again be able to differentiate between them.

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

Migrateduser

The ability to configure this behavior is feature request #10849. I've added your comments to it.

The bugs mentioned in my earlier post appear to still be open. Please file a case with tech support and ask them to attach it to the relevant bugs.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

Todd,

I'm wondering almost 7 months later if this has been resolved yet. I'm using OD 6.0.2 on Unix and Windows and am having the "ambiguous filename" issue.

Thanks,

Dave

Environments:
(1,2) TS6.5, TS6.5SP1 on W2K3
(3) Vignette V7 Portal on Solaris 9

Migrateduser

Dave - The bugs and feature request mentioned in my earlier posts appear to still be open. Please file a case with tech support and ask them to attach it to the relevant bugs and/or feature request.

Thanks.

Todd Scallan
Sr. Dir. Product Mgt.
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com