Successful push but changes in pushed file are missing

[Juliana Arnolds]

Peter Hosey wrote:
> On Oct 02, 2008, at 12:12:01, Juliana Arnolds wrote:
> 
>> When viewing the local Hg wksp, the changes were successfully  
>> committed and pushed.  When viewing
>> the remote Hg wksp and looking at the changeset log, Mercurial  thinks 
>> it has the latest changes and believes the update to the  store has 
>> occurred, but this is not the case.  Despite "hg status"
>> returning nothing, the store thinking it is updated and the  changeset 
>> appearing in the log, the
>> changes made to the file in the local Hg wksp have not been  
>> propagated to the corresponding file in the remote Hg wksp.
> 
> 
> What do you mean by “workspace”? Are you talking about the  
> repositories, or their working copies?

Sorry for not being clear -- My understanding is that a Mercurial repository consists of a working 
directory coupled with a store.

I setup a Mercurial repository on what I'm calling the "remote server".  I cloned the remote server 
repository in order to create a Mercurial repository on my local system.  On the local system, I 
made changes to a file in the working directory and committed it to the store.  The "hg status" and 
"hg head" commands verified that commit was successful.  I have the following hook in the hgrc file 
of the remote repository so the update is performed automatically when the local repository performs 
a push.

[hooks]
changegroup = hg update >&2
# The above changegroup hook specifies the command to be run AFTER a
# group of changesets has been brought into the repository from
# somewhere else -- By adding the above hook, a remote
# repository can simply do a "hg push" and the update here will
# be done automagically.

> 
> What does “hg parents” say in each repository?

Uh oh....the "hg parents" output is different for the local and the remote repositories....when I 
perform an "hg log" on both repositories, the logs are the same.  I'm relatively new to Mercurial so 
  I'll have to read about this --


> 
> Have you run hg update on the remote repository?

Yes -- states that the repository is up-to-date and the head for the remote repository matches the 
head for the local one.