Changes

Jump to: navigation, search

LEAP SOP

308 bytes added, 22:19, 27 March 2016
no edit summary
; extra: Extra packages such as docker, cockpit, golang, etc.
Source While there is no Rsync repository for CentOS source rpms , they can only be downloaded manually through yum or curl/wgetor yum. Therefore, since there creating a bash script to automate download processes is no Rsync repository for Centos source rpmshighly recommended.
== Determine problem ==
; Build test/check failed
: <u>Reason</u>: Can be random reasons or the program software is naturally just unable to run perfectly on AArch64
: <u>Solution</u>: Try to look for solutions, otherwise comment out the <tt>%check</tt> section in spec file
; BuildError<span>:</span> No matching arches were found
: <u>Reason</u>: Package only supports the specific architectures on the <tt>ExclusiveArch</tt> list in the spec file: <u>Solution</u>: Checkout similar version of the package on [http://arm.koji.fedoraproject.org Fedora ARM Koji ] and [http://buildlogs.centos.org/centos/7 CentOS AArch64 repo ] and determine whether the package is possible to support AArch64 or not
; Fail to patch
</source>
=== Rebranding Re-branding ===
The packages that contain the extension <tt>.centos</tt> in their release version are branded packages. In order to properly re-branding those packages for LEAP, here is the checklist:
* Replace the word "CentOS" or "CentOS Linux" with "LEAP", and "centos" with "leap" in spec package descriptions and patches (make sure they are branding-related)* Replace CentOS branding patches with LEAP branding patchesone
** If certain patch file contains author name, regenerate the patch with your own name instead of modifying the patch directly
* Replace CentOS links with links for LEAP links accordingly
* Sometimes Red Hat trademarks and links have to be replaced as well
* Remove CentOS/RHEL certificate certificates, binaries, or any enterprise support files and binaries
==== Particular cases ====
A few packages in the package set contain patches or sources having identical file names. When installing source rpms to rpmbuild tree (<tt>$HOME/rpmbuild/*</tt>), try to avoid installing too many of them at the same time (50+). Wipe the rpmbuild tree after finishing modification and build of those packages on Koji. There are a few problematic packages have been discovered:
* OpenJDK 6 / 7 / 8 packages
* '''xorg-x11-drv-dummy ''' and '''xorg-x11-drv-fbdev'''
= Fixing dependencies = Other packages ==After all of the packages have been done, it's time to fix minor broken dependencies. <tt>repoclosure</tt> and <tt>leap-closure-report.sh</tt> (by * '''Chris Markietalibreoffice''') are the tools to check dependency stats of a repository. You should always check the build-tag repository instead Require at least 50GB of dest-tag because space to build-tag usually inherits all the existing packages.
= Fixing broken dependencies =After all of the packages have been done, it's time to fix minor broken dependencies. <tt>repoclosure</tt> and <tt>leap-closure-report.sh</tt> (by Chris Markieta) are the tools to check dependency stats of a repository. You should always check the build-tag repository since new packages may require some of the old packages. When a package requires a missing shared library file like <tt>xxxxx-3.so</tt>, the package usually it only need to be rebuilt again (if the library exists) in order to pick up the latest .so file from the latest version of required library.
= Package signing =

Navigation menu