4091 2013-03-25 02:16:58 +0000 Add support to bitbake fetcher to fetch files from bare repos for PREMIRRORS 2025-10-02 15:05:03 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified All Multiple RESOLVED OBSOLETE Medium enhancement Future 1 jeff.polk liezhi.yang corneliux.stoicescu mark.hatle mark.hatle poky.bs.watcher poky.watcher randy.macleod --- --- No (bug/feature does not impact docs) oldest_to_newest 31068 0 jeff.polk 2013-03-25 02:16:58 +0000 WR ships our releases and updates via bare git repositories. We also ship complete PREMIRRORS so that no network access or downloads are required but those directories and updates for them, while maintained internally as repositories, must currently be updated as regular directories. We'd like to be able to harmonize the mechanisms used for our distributions and updates by directly supporting bare git repositories as PREMIRRORS. 31118 1 richard.purdie 2013-03-25 14:33:21 +0000 Doesn't this work already in master? 34024 2 richard.purdie 2013-06-20 21:12:25 +0000 I'm struggling to believe this doesn't work with current master since everything in DL_DIR exists as bare git repos and the mirror tarballs are even bare git repos. I'm closing this as WORKSFORME since I can't see the problem here. If there is a problem, please repoen with more details. 37836 3 corneliux.stoicescu 2013-10-11 10:59:02 +0000 Inside bitbake/lib/bb/tests/fetch.py I see: self.d.setVar("PREMIRRORS", "git://someserver.org/bitbake git://git.openembedded.org/bitbake \n") Marking this as VERIFIED. 44144 4 mark.hatle 2014-06-23 19:02:37 +0000 I'm reopening this. I found the missing piece of information. The request is not to mirror bare repositories. The request is to mirror -files- -from- bare repositories. In otherwords, if I have a git repository of all of the downloads. I shouldn't have to git clone meta-downloads, and then point the PREMIRRORS to 'file://...meta-downloads'. Instead I should be able to point the PREMIRRORS to 'git://...meta-downloads.git;branch=daisy' It will then get a PREMIRROR call and attempt to extract just the requested file(s) from the bare git repository. 45801 5 richard.purdie 2014-09-24 14:33:27 +0000 Hi Mark, I hadn't seen this until now. The fetcher is "dumb" in some senses, in particular it doesn't know anything about the content of the git repo. This sounds like you want the fetcher to optionally fetch the repo, then unpack it and see if it contains something else which looks like an artefact (either another repo or tarball) which can then be passed back to the original "fetch". I'm not sure this recursive fetching is something we want to support or encourage to be quite honest. If you did want to do it, I'd suggest a different fetcher module for it using a different url type to distinguish it from the "normal" git fetcher. That backend would get calls in from the premirrors code and it would be up to it how it dealt with them. As such, this isn't something I'm planning to work on though and I am not sure how feasible this is, just thinking out loud for anyone who may want to try implementing it. 56656 6 sjolley.yp.pm 2015-11-19 16:06:54 +0000 This was REOPENED 75627 7 mark.hatle 2017-08-03 19:15:04 +0000 Just so it's clear, I'm still tracking this. Even though it is in a future state. 84507 8 randy.macleod 2019-07-25 15:32:29 +0000 Mark, it's been 2 years, are you still tracking this? 84536 9 mark.hatle 2019-07-26 18:34:11 +0000 Yes I am. 91535 10 randy.macleod 2021-09-23 15:25:03 +0000 Robert, do we still want this bug opened or has it been fixed? 96592 11 randy.macleod 2023-09-28 15:08:23 +0000 Robert, do we still care about this ER ? 102870 12 randy.macleod 2025-10-02 15:05:03 +0000 No activity so declaring obsolete.