Databases
StackOverflow2013
Postsdbo
POMercurial share extension doesn't work with nested subrepos
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMercurial share extension doesn't work with nested subrepos
    primarykey
    data
    text
    <p>I can't get mercurial <strong>share</strong> extension to work with nested repos.</p> <p>Test repository structure:</p> <ul> <li>SubrepoTest/ <ul> <li>nested/</li> </ul></li> </ul> <p>The SubrepoTest/.hgsub content:</p> <p><code> nested = nested </code></p> <p>Trying to share repo gives this error:</p> <pre><code> hg share --debug --traceback SubrepoTest Copy updating working directory resolving manifests overwrite: False, partial: False ancestor: 000000000000, local: 000000000000+, remote: 9d3080714601 .hgsub: remote created -> g .hgsubstate: remote created -> g New Text Document.txt: remote created -> g calling hook preupdate.auto_update_hooks: calling hook preupdate.auto_rhapsody: Rhapsody not running. updating: .hgsub 1/3 files (33.33%) getting .hgsub updating: .hgsubstate 2/3 files (66.67%) getting .hgsubstate subrepo merge 000000000000+ 9d3080714601 000000000000+ subrepo nested: remote added, get nested:6a97f6c97cf7b1fd1bd82cb528a7494980e17d62:hg Traceback (most recent call last): File "mercurial\dispatch.pyo", line 87, in _runcatch File "mercurial\dispatch.pyo", line 696, in _dispatch File "mercurial\dispatch.pyo", line 472, in runcommand File "mercurial\extensions.pyo", line 184, in wrap File "hgext\color.pyo", line 362, in colorcmd File "mercurial\dispatch.pyo", line 786, in _runcommand File "mercurial\dispatch.pyo", line 757, in checkargs File "mercurial\dispatch.pyo", line 693, in File "mercurial\util.pyo", line 463, in check File "hgext\share.pyo", line 29, in share File "mercurial\hg.pyo", line 175, in share File "mercurial\hg.pyo", line 416, in update File "mercurial\merge.pyo", line 596, in update File "mercurial\merge.pyo", line 391, in applyupdates File "mercurial\subrepo.pyo", line 183, in submerge File "mercurial\subrepo.pyo", line 512, in get File "mercurial\subrepo.pyo", line 494, in _get File "mercurial\subrepo.pyo", line 247, in _abssource Abort: default path for subrepository nested not found abort: default path for subrepository nested not found </code></pre> <p>I'm using Mercurial Distributed SCM (version 2.2.2) from TortoiseHG for Windows.</p> <p>How do I solve this problem?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMagnus
    1. USMagnus
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POMercurial share extension doesn't work with nested subrepos
      1. This table or related slice is empty.
      1. VTClose
    2. VO
      singulars
      1. POMercurial share extension doesn't work with nested subrepos
      1. This table or related slice is empty.
      1. VTClose
    1. COYou should ask this on superuser.com as it does not contain a programming question.
      singulars
      1. POMercurial share extension doesn't work with nested subrepos
      1. UStrojanfoe
    2. COFile a bug report at http://bz.selenic.com/...? A stack trace indicates abnormal behaviour.
      singulars
      1. POMercurial share extension doesn't work with nested subrepos
      1. USLaurens Holst
    3. CO@trojanfoe: good point. I've seen alot of similar questions here, so I thought is was accepted.
      singulars
      1. POMercurial share extension doesn't work with nested subrepos
      1. USMagnus
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload