shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-22 13:33:56 +03:00
Code
3a9fe8e768
systemd-stable/.packit.yml

47 lines
1.7 KiB
YAML
Raw Normal View History

ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 13:37:41 +03:00
---
# vi:ts=2 sw=2 et:
#
# Docs: https://packit.dev/docs/
specfile_path: .packit_rpm/systemd.spec
synced_files:
- .packit.yaml
- src: .packit_rpm/systemd.spec
dest: systemd.spec
upstream_package_name: systemd
downstream_package_name: systemd
# `git describe` returns in systemd's case 'v245-xxx' which breaks RPM version
ci: build the Fedora RPMs with -Werror
2021-01-29 00:27:18 +03:00
# detection (that expects 245-xxxx'). Let's tweak the version string accordingly
ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 13:37:41 +03:00
upstream_tag_template: "v{version}"
Packit: build SRPMs in Copr Add srpm_build_deps key to the Packit config to specify needed dependencies for SRPM build and indicate to build SRPM in Copr. (cherry picked from commit d15e1a29e3aab04ee79d5e3ec8e1e65fca78e165)
2022-03-09 09:50:29 +03:00
srpm_build_deps: []
ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 13:37:41 +03:00
actions:
post-upstream-clone:
packit: build on and use Fedora 36 spec file It's targeted to the v250 branch, while the rawhide one follows the newest upstream release, and the command line options are not compatible
2022-04-01 03:03:25 +03:00
# Use the Fedora 36 specfile
- "git clone --branch f36 https://src.fedoraproject.org/rpms/systemd .packit_rpm --depth=1"
packit: drop the 'sources' file after cloning the Fedora repo Otherwise rebase-helper thinks we're are a dist-git repository, replacing the generated git archive with PR changes with the tarball found in the 'sources' file.
2021-04-12 18:56:33 +03:00
# Drop the "sources" file so rebase-helper doesn't think we're a dist-git
- "rm -fv .packit_rpm/sources"
ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 13:37:41 +03:00
# Drop backported patches from the specfile, but keep the downstream-only ones
packit: drop unnumbered patches as well (cherry picked from commit 729c6b6af8e3cef259b80746f7f7f10cc63d309f)
2022-02-17 16:02:04 +03:00
# - Patch(0000-0499): backported patches from upstream
ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 13:37:41 +03:00
# - Patch0500-9999: downstream-only patches
packit: drop unnumbered patches as well (cherry picked from commit 729c6b6af8e3cef259b80746f7f7f10cc63d309f)
2022-02-17 16:02:04 +03:00
- "sed -ri '/^Patch(0[0-4]?[0-9]{0,2})?\\:.+\\.patch/d' .packit_rpm/systemd.spec"
packit: drop bfq patch Does not apply on v250-stable
2022-04-01 17:26:38 +03:00
# Also drop the bfq scheduler patch, does not apply on v250-stable
- "sed -ri '/^Patch0500\\:.+\\.patch/d' .packit_rpm/systemd.spec"
ci: revert back to --werror instead of -Dc_args=-Werror -Dc_args=/-Dcpp_args= don't play well with the RPM hardening macros using $CFLAGS/$CPPFLAGS, since they're mutually exclusive.
2021-03-07 01:17:01 +03:00
# Build the RPM with --werror. Even though --werror doesn't work in all
# cases (see [0]), we can't use -Dc_args=/-Dcpp_args= here because of the
# RPM hardening macros, that use $CFLAGS/$CPPFLAGS (see [1]).
ci: build with -Werror on Fedora Prompted by: https://github.com/systemd/systemd/pull/18400#issuecomment-771602705
2021-02-02 19:02:12 +03:00
#
# [0] https://github.com/mesonbuild/meson/issues/7360
ci: revert back to --werror instead of -Dc_args=-Werror -Dc_args=/-Dcpp_args= don't play well with the RPM hardening macros using $CFLAGS/$CPPFLAGS, since they're mutually exclusive.
2021-03-07 01:17:01 +03:00
# [1] https://github.com/systemd/systemd/pull/18908#issuecomment-792250110
- 'sed -i "/^CONFIGURE_OPTS=(/a--werror" .packit_rpm/systemd.spec'
ci: enable Packit integration Let's enable the Packit integration and see if it's a viable option for us. This configuration builds systemd on Fedora (on x86_64, i386, and aarch64) and runs the unit test suite. To do that, it uses the specfile from Fedora Rawhide[0] with some minor modifications, thus dropping the need to have a specfile in the upstream repository. So far the builds took around 25 minutes each, so speed-wise it's pretty good. The two remaining supported architectures (s390x and armhfp) are excluded, for now, since they're emulated and build there takes a really long time (~4 hours). [0] https://src.fedoraproject.org/rpms/systemd/
2020-03-19 13:37:41 +03:00
jobs:
- job: copr_build
trigger: pull_request
metadata:
targets:
packit: build on and use Fedora 36 spec file It's targeted to the v250 branch, while the rawhide one follows the newest upstream release, and the command line options are not compatible
2022-04-01 03:03:25 +03:00
- fedora-36-aarch64
- fedora-36-i386
- fedora-36-ppc64le
- fedora-36-x86_64
Copy Permalink