1da107bd15
Resolves: rhbz#1993156
1.3 KiB
1.3 KiB
grafana-pcp
The grafana-pcp package
Upgrade instructions
- update
Version
,Release
,%changelog
and tarball NVRs in the specfile - create bundles and manifest:
make clean all
- update specfile with contents of the
.manifest
file - run local build:
rpkg local
- run rpm linter:
rpkg lint -r *.rpmlintrc
- run a scratch build:
fedpkg scratch-build --srpm
- upload new source tarballs:
fedpkg new-sources *.tar.gz *.tar.xz
- commit new
sources
file
Patches
- create the patch
- declare and apply (
%prep
) the patch in the specfile - if the patch affects Go or Node.js dependencies, or the webpack
- add the patch to
PATCHES_PRE_VENDOR
orPATCHES_PRE_WEBPACK
in the Makefile - create new tarballs
- update the specfile with new tarball name and contents of the
.manifest
file
- add the patch to
General guidelines
- aim to apply all patches in the specfile
- avoid rebuilding the tarballs
Patches fall in several categories:
- modify dependency versions
- modify both sources and vendored dependencies (e.g. CVEs)
- modify the Node.js source (i.e. affect the webpack)
- some patches are conditional (e.g. FIPS)
Patches cannot be applied twice. It is not possible to unconditionally apply all patches in the Makefile, and great care must be taken to include the required patches at the correct stage of the build.