Upon a little further reflection, I am fairly sure that the solution will rely on FDREPO.
That will impart no burden to attempt to maintain a private git server, nor any additional financial responsibilities on anyone. While a top level server running FDREPO, like on my server or the process used to maintain the download repository for IBIBLIO uses a configuration to pull packages from “upstream”, that is neither a requirement nor suggested method for most other servers running a FDREPO. Other servers, like Victoria’s repository should really be configured to pull from other servers running FDREPO for a number of reasons. One such reason, is it is orders of magnitude faster than polling a git server about updates to packages. The question then becomes how soon will this be fixed. The answer is, I do not know. I am very deep into another project and can neither afford or desire to divert my attention aways from that to solve this new issue. Nor do I wish to spend countless hours making fundamental changes to the “end-of-life” RBEv3. While I may find the time to gut portions of RBEv3 and glue-in some sort of patch, that largely feels like a waste of time. It is more likely that the monthly interim test builds will be suspended, until I have the time and motivation to create and test RBEv4. A special thanks goes to GitLab for all of the extra work they have given me. :-( Jerome _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
