New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dist-git - avoid the downstream-only hacks we are using for autospec #2317
Comments
note that this may also solve our problem https://pagure.io/rpkg/issue/641 |
Summary from our meeting: That issue discusses possibilities of how to get the original SRPM from the generated one. That's not what we want, we'd loose the generated Release and %changelog fields that we want to keep (i.e. if Fedora DistGit has a generated |
Related: #2600 |
Would that work for you? copr/dist-git/copr_dist_git/package_import.py Line 220 in fceb794
|
Absolutely, thank you for the patch @onosek! We'll just need to add "BuildRequires: python3-rpkg >= X.Y" (the new option will fail with older rpkg versions). It would be nice to get the new version of rpkg into F37+. |
There's the second part of this issue, ie the "--allow-empty" option we need to drop from commit(). |
We have "dnf versionlock python3-rpkg" on dist-git machines. |
sync:
next steps needed to close this issue:
|
#2608 is blocking the last two steps here |
Related: fedora-copr#2317 pyrpkg don't allow using pre-generated SRPM by default. They created for this `allow_pre_generated_srpm` for us.
Related: fedora-copr#2317 pyrpkg don't allow using pre-generated SRPM by default. They created for this `allow_pre_generated_srpm` for us.
Related: fedora-copr#2317 pyrpkg don't allow using pre-generated SRPM by default. They created for this `allow_pre_generated_srpm` for us.
Related: fedora-copr#2317 pyrpkg don't allow using pre-generated SRPM by default. They created for this `allow_pre_generated_srpm` for us.
Related: fedora-copr#2317 pyrpkg don't allow using pre-generated SRPM by default. They created for this `allow_pre_generated_srpm` for us.
Related: fedora-copr#2317 pyrpkg don't allow using pre-generated SRPM by default. They created for this `allow_pre_generated_srpm` for us.
Related: fedora-copr#2317 pyrpkg don't allow using pre-generated SRPM by default. They created for this `allow_pre_generated_srpm` for us.
Related: fedora-copr#2317 pyrpkg don't allow using pre-generated SRPM by default. They created for this `allow_pre_generated_srpm` for us in 1.66-6 version of rpkg.
Related: #2317 pyrpkg don't allow using pre-generated SRPM by default. They created for this `allow_pre_generated_srpm` for us in 1.66-6 version of rpkg.
There are now two problems to fix:
spec_file_processed_by_rpmautospec
check needs to be disabled for copr dist git deployments--allow-empty
option shouldn't be used while importing SRPMs and unskip test_no_op_1 (see dist-git: FTBFS with python-rpkg > 1.65 #2600)Original issue: https://pagure.io/copr/copr/issue/2317
Opened: 2022-09-22 13:23:01
Opened by: praiskup
We need a way around this (a new opt-out in rpkg, I guess, and proper configuration in copr-dist-git or dist-git):
https://pagure.io/rpkg/c/3087dd72e933568896b2f167bab75194482a6cd1
The reason is that in Copr we want to import the pre-generated SRPMs into our "proxy" DistGit instance. This way we keep the changelog and Release info baked into the Fedora DistGit "git log".
praiskup commented at 2022-09-22 23:03:11:
For now, we can apply this patch (ansible patching), and things should be fine...
The text was updated successfully, but these errors were encountered: