If a folder is deleted from clearcase and then when I "update from repository" should the folder be deleted locally also ? Currently it is not deleted locally, I have updated my view and can see the folder has been removed from the view.
No, by default, a cleartool update preserve private content.
And your directory is now considered private, once removed from ClearCase from another view.
(which is your case here: you didn't delete it directly in your view from the ClearCase interface).
You could see your directory renamed as 'yourDirectory.unloaded', but sometimes it will remain unchanged, especially if some process has an handle on it.
See technote "About .unloaded snapshot view files" for more.
The help page "How files and directories in snapshot views are unloaded" mentions:
Unloading directories
Directories are unloaded recursively.
To unload a directory element, the files in the directory are unloaded.
If any view-private objects, hijacked files, or checked-out files are in the directory, or if the directory is currently in use (for example, if your current working directory is in or below the directory) .unloaded is appended to the name of the directory.
For example, if the directory src contains view-private files, the directory is renamed to src.unloaded.
In your case, you need to make sure that no process has any handle on the directory itself or the directory content, make your update (-overwrite has no bearing here, being only there to restore hijacked file), and then search and remove any *.unloaded elements (files or directories).
As far as I know, delete a folder from clearcase interface , local file will also be deleted.
Related
Background
In ClearCase, you can make unreserved checkouts if a certain file is already checked out by another view with the following command:
ct co -unreserved <element>
You can also add a new element to clearcase with the following command
ct mkelem <new_element>
However, using the mkelem command on a file requires that the directory of the file be a checked-out clearcase element.
Issue
I am trying to create a new clearcase element in a directory. This directory is current checked out by another view, thus I need to make an unreserved checkout. The unreserved checkout works perfectly. However, when I try to run ct mkelem newFile after making an unreserved checkout of the directory, I get this error:
% ct mkelem newFile
Creation comments for "newFile": . Created
element "newFile" (type "text_file").
ERROR: User [user_name]
cannot make reserved checkouts for this file type or branch in this area. File
is [/vobs/directory/to/newFile##/main/0] You can still
make an unreserved checkout if needed.
Which lead me to wonder...
Question
Is there a way to make a new clearcase element inside an unreserved checkout of a directory?
This seems to be a custom error message: "You can still make an unreserved checkout".
Meaning it is not natively displayed by ClearCase.
So check if there are any VOB trigger in place which would enforce such a policy (no unreserved checkout of a directory): use cleartool lstype -invob \aVob -kind trtype, as in this answer.
Because you can checkout a folder concurrently in a reserved and unreserved way... which can lead to evil twins, as this thread illustrates:
evil twins were introduced from users in parallel directory versions, either from another branch or different versions in the same branch (a user had an old unreserved checkout, added a file that another user already added in a reserved checkout later in the version tree, thus you now have evil twins.)
I have an issue with NetBeans. I created a folder on my webserver with some files (pictures). Now I want to sync it with my project in NetBeans. While other folders had no problem, this folder is not been downloaded with the below mententioned summary.
For me it looks like the folder xxx (name changed) is seen as a symbolic link and thus it is not downloading. i checked the attributes (chmod) of the directory and it has the same settings as other folders.
1) How to check if this is realy a symbolic link? If I run ls -la I don't see differences to other folders.
2) How to change a symbolic link to a real folder?
3) How to sync the folder (if I cannot solve point 2)? <-- I know that this is done generally by a right click ;-)
Thanks
Tim.
This is the result presented by NetBeans 8.2:
Summary
====================
Ignored:
dir xxx File xxx is a symbolic link.
file xxx/TNBild0.JPG Some parent of file xxx/TNBild0.JPG is a symbolic link.
file xxx/TNBild1.jpg Some parent of file xxx/TNBild1.jpg is a symbolic link.
file xxx/TNBild2.jpg Some parent of file xxx/TNBild2.jpg is a symbolic link.
file xxx/TNBild3.jpg Some parent of file xxx/TNBild3.jpg is a symbolic link.
Runtime: 1 ms, processed: 0 file(s), 0 KB
As I was not able to solve the above discribed issue, I deleted all local files and the project and created a brand new project which then finally downloaded all the files.
No good solution, but a workaround.
How does one add a file or registry by editing a sequenced AppV 5.0 application?
Whenever we have tried to add a file directly under Root in the AppV 5.0 editor, the file was added to different location. Is there a reason for that?
The top directory of the package represents a location where some metadata files key to describing the package reside. The directory literally named "Root" represents the primary virtual application directory. You should be successful adding files to this directory, or any of the VFS directories, but not to the top directory of the package itself.
In our clearcase we are having few folders require same contents.
We use to have symlink to achieve that. But Now our folders are having view private files, so symlink doesn't do any good.
Is copying it again the only mechanism ?
Any other policy or settings which can help to symlink view private file?
Symlinks (OS symlinks, not cleartool symlinks) should be supported, even for private files (they would certainly work in snapshot view anyway: those are based on the native OS).
Otherwise, copy is still a solution to fallback on.
But I am not aware of any dedicated policy on ClearCase for symlinks on private view files.
The is only one policy for versionned symlinks (created by cleartool ln -s, but this isn't your current scenario):
On Linux and UNIX systems, symbolic links are listed as absolute pathnames by default.
To list symbolic links as relative pathnames, set the environment variable CCASE_LS_RELATIVE_SYMLINK_PATH.
The OP Samselvaprabu mentions using Dynamic view drive and i am in windows environment, and reports the following error on symlink creation:
Object Msilist.bat is not a valid symlink target; no symlinks will be created.
Please select only valid symlink targets and retry the operation.
The man page "To create a Vob symlink" mentions the following restrictions:
You can use the cleartool ln -s command to create a VOB symbolic link (symlink) to the following items:
A file or directory (checked in or checked out)
A symbolic link
An eclipsed element (dynamic views only)
A hijacked element (snapshot views only)
The target of the symbolic link must be in the same view as the directory in which the symbolic link is to be created.
If you are in a snapshot view, unloaded elements are not valid symlink targets. Also, the directory in which the symlink is to be created must also be loaded.
My point was:
If cleartool ln -s doesn't work, especially for private file (which are not in ClearCase anyway), use OS symlink (in your case, NTFS symlinks if you are on Windows Vista or more, otherwise simple junction points)
So OS symlinks (native symlinks, not created by cleartool) should work.
I have CM Server for ClearCase Remote Clients in windows 2003 server.
Installed package in server.
I'm getting below error in CCRC client:
"CRVAP0087E CCRC command "checkin" failed: Unable to create pathname for
file "C:\ccweb\v973012\v973012_Latest_FMC": Permission denied"
Can you please help me to fix this issue?
The most efficient way to troubleshoot right issue is to go directly to the CCRC server, under the CCRC web (snapshot) view and type:
cd c:\ccweb\v973012
cleartool lsview -l -full -pro -cview
That way, you see with which group the user has created the CCRC view in the first place.
That group must be one of the groups associated with the Vob of the element being checked-in.
Check also this technote:
During the installation of Rational ClearCase, you are asked for a temporary directory to use during the installation to unzip large artifacts.
This temporary directory is used to preserve user configuration settings during an update or uninstall process.
If you specify a directory that is mounted on a file system that is separate from the installation directory, the file permissions and owners are not preserved when the files are moved across the file systems.
Finally, check for any trigger set on the Vob: they can have an unwanted side-effect with that CCRC 'checkin' operation.
In the specific case of the OP mth123, he suggests:
Go to the Windows Explorer and try these steps:
Go the the following directory: C:\ccweb
Rename the folder v123412 to V123412 (Only change the first letter and put "V" capitalized.)
Check if the problem is solved.
So depending on the actual tag of the view, this could be an issue about case-sensitive path.
The latest patch caused this issue. While applying patch CC preserving some file inclusing ccweb folder. while restoring those folder during post install these directory might have changed with lowercase/upper case. This is currently with IBM queue.
If you are going to upgrade CCRC please make a copy of ccweb directory with proper ACL or use ccopy.exe (clearcase utility)