Bug 1462182

Summary: RFE: look-aside cache
Product: [Community] Copr Reporter: Michael Mráka <mmraka>
Component: backendAssignee: Copr Team <copr-team>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: praiskup
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-15 07:58:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael Mráka 2017-06-16 11:47:07 UTC
Description of problem:
In Spacewalkproject we need to build thirdparty packages with a custom options or custom patches.

In such cases we store only package spec and patches in git repo because storing source tgzs in git is not efficient.   

To build the package we need to have a place (look-aside cache) where we can upload tgz and copr will find it during build. It could be the same place where copr puts sources when building from srpm or url.

Comment 1 Pavel Raiskup 2017-06-16 12:13:30 UTC
It is planned to open copr's dist-git for writing, similar to what we have
in Fedora's dist git (upload tarball, and commit only sources/patches to
git), this is bug 1397508.

You could build from Fedora's dist-git too, something to be fixed there
(bug 1391889) but could work for you.

There's tito feature that supports git annex too:
http://m0dlx.com/blog/Reproducible_builds_on_Copr_with_tito_and_git_annex.html

And perhaps you are interested in this too
https://pagure.io/copr/copr/issue/60

Comment 2 clime 2017-07-18 09:17:46 UTC
Could this possibly be also addressed by adding GIT LFS support to COPR? Meaning that the tarballls you need to place in your repo would be links into a storage and COPR would auto-download them?

This seems to be a good way to solve this problem as well.

Comment 4 Pavel Raiskup 2020-12-14 13:55:01 UTC
Hi Michael, after some time - I tend to say that opening Copr Dist Git 
repository for custom writing isn't that much worth it.  IMO we should
concentrate on better support for Fedora default DistGit - which might
now be in a pretty decent state now.

Would you be OK to use "private-*" copr repository in Fedora DistGit,
and upload the tarballs into Fedora DistGit?  Then command like this works:
$ copr build-distgit --name postgresql --commit private-praiskup-rebase-2017-MAY-f27 ping --chroot fedora-rawhide-x86_64

Comment 5 Michael Mráka 2020-12-14 16:14:34 UTC
Actually, we don't need it anymore. The project we need this for has been discontinued in the meantime.

Feel free to close this RFE if it does not fit your future plans.

Comment 6 Pavel Raiskup 2020-12-15 07:58:17 UTC
Ok, I tested the command from comment #4 and it worked.  So I think
people can use Fedora DistGit.  Thank you for the feedback!