SourceGear Support

"pkgadd -d" expects a device, and the file (after gunzip) will work fine. The whole command would be something like "pkgadd -d SGsos-4.1.0-professional-SunOS-5.9.pkg".

This bug was introduced for 3.0, and will be fixed very shortly in 3.0.1.

You may want to try the Solaris 9 package on Solaris 8 (2.8). If you have the GTK packages installed (Sun Freeware has gtk-2.2.4 packages for Solaris 8), it may work, even though it was complied for a newer version.

You can do either. If you work while Renegade, you'll simply need to Check Out the file some time before you want to perform a Check In / Commit.

Yes, we will release SOS 4.1 Unix packages in the very near future, built on Fedora Core 2 machines. This new release depends on GTK 2.4, which Red Hat 9 does not provide (third-party GTK 2.4 packages are available for it), so the builds are made and tested on Fedora 2. Fedora 3 was just released, a...

This error points to a dynamic linker (ld.so) or C library problem. You may want to run "ldconfig" as root; that may help. Also, you may want to try reinstalling the packages containing libc and ld.so. As a last resort, you could download the RPM of SOS 4.0 for Unix (which is compatible wi...

This is a (pretty) harmless error having to do with the garbage collection and finalization of mutex objects. Vault 3.0 uses a different locking mechanism (.NET framework Mutex objects instead of Win32 Mutex objects), so this error should go away.

I wrote a small command-line application that does what you've requested. It's written in C#, but the API would be the same for VB or C++. You'll need to put a copy of your Vault Client DLLs in the Client DLLs directory after you unzip the archive.

Let me know if you have any questions.

Vault does not allow you to check in a file with a status of Unknown, because it doesn't know which version of the file it was based on (its baseline version). Not knowing the baseline prevents it from being able to construct a delta to send to the server during the check in. A Get Latest Version (w...

Not yet.

Yes. I just tested this on my 3.0 pre-release build, and it worked. I moved $/Doc/install.txt to $/Doc/Internal/install.txt, committed the change, then performed a Get Latest Version on $/Doc. The file moved to the correct working folder (it's actually deleted, then downloaded again, but the effect ...

I'm currently working with a co-worker to solve your first problem (the error message). This can happen when a baseline file has been deleted from that folder but is needed for a Vault operation. But the name of the file is suspicious (it should not end with .0), and may mean the client is receiving...

This is exactly what the Get Latest Version feature in Vault does. It will update any files in the developer's working folder that have newer versions in the server's repository (if the file has been modified by the developer, it can automatically merge the changes, do nothing, or overwrite, dependi...

I've added this feature request to our list to be addressed in a future version.

I've moved this over to the new Dragnet support forum.