ci: Packit configuration update #799
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #799 +/- ##
=======================================
Coverage 83.90% 83.90%
=======================================
Files 74 74
Lines 4387 4387
=======================================
Hits 3681 3681
Misses 706 706 ☔ View full report in Codecov by Sentry. |
LecrisUT
force-pushed
the
fedora/centos-10
branch
from
08f6e6b
to
e8a3286
Compare
LecrisUT
force-pushed
the
fedora/centos-10
branch
from
e8a3286
to
b975eb8
Compare
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
LecrisUT
force-pushed
the
fedora/centos-10
branch
from
7e02584
to
2a88144
Compare
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
Does not seem to be ready yet Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
LecrisUT
force-pushed
the
fedora/centos-10
branch
3 times, most recently
from
f4a75ed
to
ca08afd
Compare
Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
LecrisUT
force-pushed
the
fedora/centos-10
branch
from
ca08afd
to
7e3d62b
Compare
This reverts commit 7e3d62b. Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
LecrisUT
force-pushed
the
fedora/centos-10
branch
from
55d2379
to
ae99525
Compare
henryiii
approved these changes
Aug 30, 2024
LecrisUT
added a commit
that referenced
this pull request
Oct 5, 2024
- hotfix for #799 (doesn't need new release, I've already pushed the changes downstream) - reformat the fmf files to look more like yaml - install doc examples in their own `venv` --------- Signed-off-by: Cristian Le <cristian.le@mpsd.mpg.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Primarily some cleanups:
scikit-build-coreproject, instead use the auto-generated project by packitnightlyproject is well ordered (previously they had the same NVR (name-version-release) so it would pick randomly any build from there)rpminspect. I will look into unifying with downstream's implementationpackit.yamlto make it simplerpython3-scikit-build-core+pyprojectsub-package since it really has no effect nowIncluded. Postponed because F40, F39 does not satisfy requirementhatchlingtests to the test environmentIdeally we would want both epel-9 and epel-10 as build targets with tests enabled, but there are some issues encountered:
epel-10:
epel-9:
setuptools-scmcan't determine version from git-archive (can be workaround)exceptiongroup: not packagedFurther blocked by
flit-scm->setuptools-scm->setuptools, the last being a major blocker for a lot of stuff getting on EPEL9packaging >=21.3vs20.9