View Issue Details

IDProjectCategoryView StatusLast Update
0009627Talerexchangepublic2025-03-20 10:16
Reporterfefe Assigned ToResolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityfeatureReproducibilityalways
Status implementingResolutionreopened 
Product Versiongit (master) 
Target Versionpost-1.0Fixed in Version1.0 
Summary0009627: 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
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2025-03-18 10:25

manager   ~0024215

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.

fefe

2025-03-18 10:37

reporter   ~0024217

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.

Christian Grothoff

2025-03-18 10:42

manager   ~0024220

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.

Christian Grothoff

2025-03-20 10:16

manager   ~0024252

When the submodule update fails, bootstrap should output a hint that either
- network is down, or
- submodules were renamed and checkout is outdated

Issue History

Date ModifiedUsernameFieldChange
2025-03-18 10:16fefeNew Issue
2025-03-18 10:16fefeStatusnew => assigned
2025-03-18 10:16fefeAssigned To => Christian Grothoff
2025-03-18 10:25Christian GrothoffNote Added: 0024215
2025-03-18 10:25Christian GrothoffStatusassigned => informing
2025-03-18 10:25Christian GrothoffResolutionopen => no change required
2025-03-18 10:25Christian GrothoffFixed in Version => 1.0
2025-03-18 10:37fefeStatusinforming => feedback
2025-03-18 10:37fefeResolutionno change required => reopened
2025-03-18 10:37fefeNote Added: 0024217
2025-03-18 10:42Christian GrothoffNote Added: 0024220
2025-03-20 10:15Christian GrothoffAssigned ToChristian Grothoff =>
2025-03-20 10:15Christian GrothoffSeverityminor => feature
2025-03-20 10:15Christian GrothoffStatusfeedback => implementing
2025-03-20 10:15Christian GrothoffTarget Version => post-1.0
2025-03-20 10:15Christian GrothoffSummarybootstrap fails => bootstrap fails when submodules were renamed, should improve error message
2025-03-20 10:16Christian GrothoffNote Added: 0024252