[opensuse-buildservice] feature request: a service to test spec file for distro specific policies
some distro's like opensuse seem to have policies on how a package is to be build and these policy are checked in the spec file in addition to rpm spec file requirements. The build service seem to check the policies after the code is compiled and the package is being build and then bail out if the limit on error points in reached. Trying to modify the spec file to go under the limit if not eliminating them means spinning up the entire thing from the beginning, build the sources and then check to see if a policy is not violated, only to see a new. Doing guess work on my part means wasting unnecessary resources on your part.I dont have suse locally so you guys' resources are my only hope :-) Having a way to process a spec file before building a package would save a few resources on your guys part. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Donnerstag, 14. Juni 2012, 14:47:49 schrieb .. ink ..:
some distro's like opensuse seem to have policies on how a package is to be build and these policy are checked in the spec file in addition to rpm spec file requirements.
The build service seem to check the policies after the code is compiled and the package is being build and then bail out if the limit on error points in reached.
Trying to modify the spec file to go under the limit if not eliminating them means spinning up the entire thing from the beginning, build the sources and then check to see if a policy is not violated, only to see a new. Doing guess work on my part means wasting unnecessary resources on your part.I dont have suse locally so you guys' resources are my only hope :-)
Having a way to process a spec file before building a package would save a few resources on your guys part.
done. You can get find it in obs-service-source_validator package and for build checks of the build result in rpmlint. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 06/14/2012 08:54 PM, Adrian Schröter wrote:
Am Donnerstag, 14. Juni 2012, 14:47:49 schrieb .. ink ..:
some distro's like opensuse seem to have policies on how a package is to be build and these policy are checked in the spec file in addition to rpm spec file requirements.
The build service seem to check the policies after the code is compiled and the package is being build and then bail out if the limit on error points in reached.
Trying to modify the spec file to go under the limit if not eliminating them means spinning up the entire thing from the beginning, build the sources and then check to see if a policy is not violated, only to see a new. Doing guess work on my part means wasting unnecessary resources on your part.I dont have suse locally so you guys' resources are my only hope :-)
Having a way to process a spec file before building a package would save a few resources on your guys part.
done.
You can get find it in obs-service-source_validator package and for build checks of the build result in rpmlint.
which is unfortunately broken on my system toganm@desktop:~/devel/My_Packages/branched/clamav> osc service localrun source_validator grep: Unmatched [ or [^ grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end clamav-0.97.5.tar.gz clamav-rcclamd clamav-rcfreshclam clamav-updateclamconf clamav-rpmlintrc clamav-rcmilter clamav-conf.patch clamav-sles9.patch clamav-gcc47.patch error: line 49: Unknown tag: Source0: clamav-0.97.5.tar.gz I have obs-service-source_validator-0.2-22.1.noarch osc-0.134.1-75.1.noarch Any ideas what to look for further info Thanks Togan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Donnerstag, 14. Juni 2012, 21:25:09 schrieb Togan Muftuoglu:
On 06/14/2012 08:54 PM, Adrian Schröter wrote:
Am Donnerstag, 14. Juni 2012, 14:47:49 schrieb .. ink ..:
some distro's like opensuse seem to have policies on how a package is to be build and these policy are checked in the spec file in addition to rpm spec file requirements.
The build service seem to check the policies after the code is compiled and the package is being build and then bail out if the limit on error points in reached.
Trying to modify the spec file to go under the limit if not eliminating them means spinning up the entire thing from the beginning, build the sources and then check to see if a policy is not violated, only to see a new. Doing guess work on my part means wasting unnecessary resources on your part.I dont have suse locally so you guys' resources are my only hope :-)
Having a way to process a spec file before building a package would save a few resources on your guys part.
done.
You can get find it in obs-service-source_validator package and for build checks of the build result in rpmlint.
which is unfortunately broken on my system
toganm@desktop:~/devel/My_Packages/branched/clamav> osc service localrun source_validator grep: Unmatched [ or [^ grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end clamav-0.97.5.tar.gz clamav-rcclamd clamav-rcfreshclam clamav-updateclamconf clamav-rpmlintrc clamav-rcmilter clamav-conf.patch clamav-sles9.patch clamav-gcc47.patch error: line 49: Unknown tag: Source0: clamav-0.97.5.tar.gz
I have obs-service-source_validator-0.2-22.1.noarch osc-0.134.1-75.1.noarch
Any ideas what to look for further info
You can call it manually to debug it. Just run /usr/lib/obs/service/source_validator in your source directory. A patch very welcome :) -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 06/14/2012 09:53 PM, Adrian Schröter wrote:
Am Donnerstag, 14. Juni 2012, 21:25:09 schrieb Togan Muftuoglu:
On 06/14/2012 08:54 PM, Adrian Schröter wrote:
Am Donnerstag, 14. Juni 2012, 14:47:49 schrieb .. ink ..:
some distro's like opensuse seem to have policies on how a package is to be build and these policy are checked in the spec file in addition to rpm spec file requirements.
The build service seem to check the policies after the code is compiled and the package is being build and then bail out if the limit on error points in reached.
Trying to modify the spec file to go under the limit if not eliminating them means spinning up the entire thing from the beginning, build the sources and then check to see if a policy is not violated, only to see a new. Doing guess work on my part means wasting unnecessary resources on your part.I dont have suse locally so you guys' resources are my only hope :-)
Having a way to process a spec file before building a package would save a few resources on your guys part.
done.
You can get find it in obs-service-source_validator package and for build checks of the build result in rpmlint.
which is unfortunately broken on my system
toganm@desktop:~/devel/My_Packages/branched/clamav> osc service localrun source_validator grep: Unmatched [ or [^ grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end clamav-0.97.5.tar.gz clamav-rcclamd clamav-rcfreshclam clamav-updateclamconf clamav-rpmlintrc clamav-rcmilter clamav-conf.patch clamav-sles9.patch clamav-gcc47.patch error: line 49: Unknown tag: Source0: clamav-0.97.5.tar.gz
I have obs-service-source_validator-0.2-22.1.noarch osc-0.134.1-75.1.noarch
Any ideas what to look for further info
You can call it manually to debug it. Just run
/usr/lib/obs/service/source_validator
in your source directory. A patch very welcome :)
20-files-present-and-referenced is the faulty one, but regexp is not my strong thing ;=) + grep -a '^Icon:' /home/toganm/devel/My_Packages/branched/clamav/clamav.spec + sed -n 's/^Icon:[ ]*/%{echo:/ /^%{echo:/s/$/ }/p' + grep -a -q '^Release' /home/toganm/devel/My_Packages/branched/clamav/clamav.spec ++ grep -a '^%if' /tmp/check_if_valid_source_dir-Gyv5ZM/tmp.spec ++ wc -l ++ grep -a '^%endif' /tmp/check_if_valid_source_dir-Gyv5ZM/tmp.spec ++ wc -l + test 4 -gt 4 + read line ++ grep -E '^Source:|^Source[0-9]*:|^Patch:|^Patch[0-9]*:' /home/toganm/devel/My_Packages/branched/clamav/clamav.spec + grep -qx '##seen Source0: %{name}-%{version}.tar.gz' /tmp/check_if_valid_source_dir-Gyv5ZM/tmp.spec grep: Unmatched [ or [^ + echo 'Source0: %{name}-%{version}.tar.gz' + sed -e 's/^\(\([Ss]ource\|[Pp]atch\)[0-9]*:[ ]*\)\(.*\)/##seen \1\3\n%{echo:\3 }/' + read line + grep -qx '##seen Source1: clamav-rcclamd' /tmp/check_if_valid_source_dir-Gyv5ZM/tmp.spec grep: Invalid range end + echo 'Source1: clamav-rcclamd' + sed -e 's/^\(\([Ss]ource\|[Pp]atch\)[0-9]*:[ ]*\)\(.*\)/##seen \1\3\n%{echo:\3 }/' + read line + grep -qx '##seen Source2: clamav-rcfreshclam' /tmp/check_if_valid_source_dir-Gyv5ZM/tmp.spec grep: Invalid range end + echo 'Source2: clamav-rcfreshclam' + sed -e 's/^\(\([Ss]ource\|[Pp]atch\)[0-9]*:[ ]*\)\(.*\)/##seen \1\3\n%{echo:\3 }/' + read line + grep -qx '##seen Source3: clamav-updateclamconf' /tmp/check_if_valid_source_dir-Gyv5ZM/tmp.spec grep: Invalid range end + echo 'Source3: clamav-updateclamconf' + sed -e 's/^\(\([Ss]ource\|[Pp]atch\)[0-9]*:[ ]*\)\(.*\)/##seen \1\3\n%{echo:\3 }/' + read line + grep -qx '##seen Source4: clamav-rpmlintrc' /tmp/check_if_valid_source_dir-Gyv5ZM/tmp.spec grep: Invalid range end + echo 'Source4: clamav-rpmlintrc' + sed -e 's/^\(\([Ss]ource\|[Pp]atch\)[0-9]*:[ ]*\)\(.*\)/##seen \1\3\n%{echo:\3 }/' -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
.. ink ..
-
Adrian Schröter
-
Togan Muftuoglu