help with cvs import

[Kevin Rodgers]

I'm tracking a 3rd party package, within our own CVS project.  I
followed the manual for the initial import: untar the distribution, cd
to its root directory, and import with the appropriate directory,
vendortag, and releasetag arguments.

Then I checked out our project, and commited some changes to the 3rd
party package.

Then I got a new release of the 3rd party package, and I followed the
manual again: untar the distribution, cd to its root directory, and
import with the same arguments except for an updated releasetag.

Now when I check out our project, any file I committed a change to
between imports is wrong: its my changed version of the old release, not
the newly imported version.  cvs log confirms that the file was
imported, but that's not what the server is returning.  When I imported
the new release, I meant it: that is the current version of that package
-- every single file.

Furthermore, files that were in the previous release of the 3rd party
package but not the new release are still checked out into my working
directory.  When I imported the new release, I meant it: that is the
current version of that package -- and not anything else.

I tried using cvs admin command as described in the "Reverting to the
latest vendor release" section of the manual, but to no avail.

What is going here?  Why does anything between import commands have any
effect?  Doesn't import update the main trunk?  If I want to work on a
previous release, I'll specify that release tag.

Frustrated,
--
Kevin Rodgers