After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 764735 - parent repos should probably work more like git clone --reference, not git clone --shared
parent repos should probably work more like git clone --reference, not git cl...
Status: RESOLVED WONTFIX
Product: ostree
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: OSTree maintainer(s)
OSTree maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-04-07 15:04 UTC by Colin Walters
Modified: 2018-08-17 18:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Colin Walters 2016-04-07 15:04:29 UTC 
It's common for ostree repositories (like the system one) to not retain the full history (i.e. to perform GC).

If one uses the current ostree `core/parent` config option to point to such repos, it's very possible that child repos that happened to be reusing parent objects will become corrupt.

I suspect pretty much every current user of `parent` repos would really want `core/alternates` which functions like `git clone --reference` on demand.

I'd say we don't change current `core/parent` but instead add `core/alternates` as a list of local file path repos to fetch from first when looking for an object?
Comment 1 André Klapper 2018-08-17 18:58:29 UTC 
OSTree has moved to Github a while ago.
Furthermore, GNOME Bugzilla will be shut down and replaced by gitlab.gnome.org.

If the problem reported in this Bugzilla ticket is still valid, please report it to https://github.com/ostreedev/ostree/issues instead. Thank you!

Closing this report as WONTFIX as part of Bugzilla Housekeeping.