Here are some notes from my meeting with Dirk from Suse. Dirk Mueller was kind enough to meet with me Saturday morning, he works on the openstack-rpm-packaging [0] repo, which contains Jinja2 templates. This repo uses Zuul jobs convert the Jinja2 to Fedora/RHEL specfile and SUSE-style specfiles and then runs a "spec-cleaner" [1] job via tox. There are also some "3rd" Party CI jobs that connect to SUSE and RDO's CI to actually build packages. The spec-cleaner process provides a modified specfile if there are changes, it's not a linter per-se. It also depends on the specfile being ordered in an "opinionated" fashion, meaning the sections need to be in a certain order, see the openSUSE Specfile Guidelines [2]. I had started to create an OBS project [3], which currently contains 1 "package", stx-fault, a package can contain multiple specfiles. This package can be branched to test. There is a CLI called "osc" which can be installed to Fedora [4] or Ubuntu [5]. There is also a git_scm service that will generate packages from a git repo [6][7]. I propose that we try to convert a couple of packages to the ordering that spec-cleaner wants and do a before and after packaging test to validate the changes, then try running spec-cleaner I am sure there is more information missing information or details, it might be useful to have a meeting with Dirk and other OBS folks when we are further along. Sau! [0] https://opendev.org/openstack/rpm-packaging [1] https://github.com/openSUSE/spec-cleaner [2] https://en.opensuse.org/openSUSE:Specfile_guidelines [3] https://build.opensuse.org/project/show/home:saulwold [4] https://download.opensuse.org/repositories/openSUSE:/Tools/Fedora_28/ [5] https://download.opensuse.org/repositories/openSUSE:/Tools/xUbuntu_18.04/ [7] https://en.opensuse.org/openSUSE:Build_Service_Concept_SourceService [8] https://github.com/openSUSE/obs-service-tar_scm