Re: Broken w3 subrepo?

I just did a fresh clone from
https://bitbucket.org/xemacs/xemacs-packages and didn't have any
problems.

Jerry James wrote:

> I did an hg pull on the packages to get yesterday's gnus prerelease,
> and got nothing, and hg log showed a last top-level update from a
> couple of weeks ago:
> 
> changeset:   1137:3720091d7106
> tag:         tip
> user:        Norbert Koch <[email protected]>
> date:        Sat Sep 19 00:35:08 2015 +0200
> summary:     pre-release gnus

Yes, that's the same tip changeset that I got.

> I thought that maybe the recent trouble with the top-level had
> something to do with it, so I did a fresh hg clone of the package
> repository.  Mercurial reported success, but several subrepositories
> are missing:
[...]
> 
> In short, all subrepos that lie alphabetically after w3 did not get
> checked out.  I thought maybe running hg update would fetch the rest:
[...]
> images/open-cap-up.xbm: untracked file differs
> abort: untracked files in working directory differ from files in
> requested revision (in subrepo xemacs-packages/w3)

I don't know what happened there.  What do "hg verify", "hg id", and "hg
tip" report in the w3 subrepo?

> This is from a fresh hg clone; I have not touched anything inside the
> w3 subrepo, or any other subrepo for that matter.  Also, after running
> hg update, I get this:
> 
> $ hg status
> M .hgsubstate

I usually see that when I've committed something in a subrepo but there
hasn't been a top-level commit to incorporate the subrepo change.  I
don't know if that's the only way you get those results, though.  I
suspect it's related to the problems you saw in the w3 subrepo.

mike