View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009627 | Taler | exchange | public | 2025-03-18 11:16 | 2025-03-20 11:16 |
| Reporter | fefe | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | confirmed | Resolution | reopened | ||
| Product Version | git (master) | ||||
| Target Version | post-1.0 | Fixed in Version | 1.0 | ||
| Summary | 0009627: bootstrap fails when submodules were renamed, should improve error message | ||||
| Description | ./bootstrap: Updating submodules Cloning into '/home/leitner/cvs/exchange/contrib/wallet-core'... fatal: repository 'https://git.taler.net/wallet-core.git/' not found fatal: clone of 'https://git.taler.net/wallet-core.git' into submodule path '/home/leitner/cvs/exchange/contrib/wallet-core' failed Failed to clone 'contrib/wallet-core'. Retry scheduled Cloning into '/home/leitner/cvs/exchange/contrib/wallet-core'... fatal: repository 'https://git.taler.net/wallet-core.git/' not found fatal: clone of 'https://git.taler.net/wallet-core.git' into submodule path '/home/leitner/cvs/exchange/contrib/wallet-core' failed Failed to clone 'contrib/wallet-core' a second time, aborting | ||||
| Steps To Reproduce | % ./bootstrap | ||||
| Tags | No tags attached. | ||||
|
|
Well, the repositories were renamed (weeks ago!). You should grab the latest exchange.git, you have some old submodules checked out. Easiest might be a fresh clone, alternatively you need to pull *without* the submodules, and then sync the submodules. |
|
|
Or, you know, hear me out here, if you make breaking changes to your git (I have the latest version checked out), and you have a bootstrap script to set up submodules, you could make it so the script follows the breaking changes. |
|
|
Not so easy, as most likely you do NOT actually have the latest version checked out: git refused that because it couldn't (automatically) update the submodules. And we don't want bootstrap to check out a different version because that'd also be wrong. So when Git origins of submodules change (hopefully very rare), you do have to manually force git to checkout the latest version without auto-updating the submodule and then submodule sync. I don't think this can be fixed. |
|
|
When the submodule update fails, bootstrap should output a hint that either - network is down, or - submodules were renamed and checkout is outdated |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-03-18 11:16 | fefe | New Issue | |
| 2025-03-18 11:16 | fefe | Status | new => assigned |
| 2025-03-18 11:16 | fefe | Assigned To | => Christian Grothoff |
| 2025-03-18 11:25 | Christian Grothoff | Note Added: 0024215 | |
| 2025-03-18 11:25 | Christian Grothoff | Status | assigned => resolved |
| 2025-03-18 11:25 | Christian Grothoff | Resolution | open => no change required |
| 2025-03-18 11:25 | Christian Grothoff | Fixed in Version | => 1.0 |
| 2025-03-18 11:37 | fefe | Status | resolved => feedback |
| 2025-03-18 11:37 | fefe | Resolution | no change required => reopened |
| 2025-03-18 11:37 | fefe | Note Added: 0024217 | |
| 2025-03-18 11:42 | Christian Grothoff | Note Added: 0024220 | |
| 2025-03-20 11:15 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2025-03-20 11:15 | Christian Grothoff | Severity | minor => feature |
| 2025-03-20 11:15 | Christian Grothoff | Status | feedback => confirmed |
| 2025-03-20 11:15 | Christian Grothoff | Target Version | => post-1.0 |
| 2025-03-20 11:15 | Christian Grothoff | Summary | bootstrap fails => bootstrap fails when submodules were renamed, should improve error message |
| 2025-03-20 11:16 | Christian Grothoff | Note Added: 0024252 |
