Forgot to attach the log. But below is the rpmlint output. The groups are
easily fixable. I am not sure what to do about the license. Why is BSD not
allowed in Tizen?




[   38s] RPMLINT report:
[   38s] ===============
[   39s] (none): E: badness 3000 exceeds threshold 2000, aborting.
[   39s] gpsd-clients-httpd.i686: W: tizen-filelist-forbidden-fhs23
/var/www is not allowed in FHS 2.3
[   39s] see http://www.pathname.com/fhs/ to find a better location
[   39s]
[   39s] gpsd-clients-httpd.i686: W: tizen-filelist-forbidden
/etc/httpd/conf.d/gpsd.conf is not allowed in Tizen
[   39s]  Your package installs files or directories in a location that
have previously
[   39s] been blacklisted. Please have a look at the particular file and
see if the
[   39s] SUSE Packaging Guidelines propose a better place on where to
install the file
[   39s] or not install it at all.
[   39s]
[   39s] gpsd.i686: W: subsys-unsupported /etc/init.d/gpsd
[   39s] The init script uses /var/lock/subsys which is not supported by
this
[   39s] distribution.
[   39s]
[   39s] gpsd.src: W: strange-permission gpsd-3.11~dev.tar.gz 0664L
[   39s] gpsd.src: W: strange-permission gpsd.spec 0664L
[   39s] A file that you listed to include in your package has strange
permissions.
[   39s] Usually, a file should have 0644 permissions.
[   39s]
[   39s] gpsd.i686: E: non-standard-group (Badness: 200) System
Environment/Daemons
[   39s] gpsd-clients-cli.i686: E: non-standard-group (Badness: 200)
Applications/System
[   39s] gpsd-clients-httpd.i686: E: non-standard-group (Badness: 200)
Applications/System
[   39s] gpsd-clients-x11.i686: E: non-standard-group (Badness: 200)
Applications/System
[   39s] gpsd-clients.i686: E: non-standard-group (Badness: 200)
Applications/System
[   39s] gpsd.src: E: non-standard-group (Badness: 200) System
Environment/Daemons
[   39s] The value of the Group tag in the package is not valid.  Valid
groups are
[   39s] listed here:
https://wiki.tizen.org/wiki/Packaging/Guidelines#Group_Tag
[   39s]
[   39s] gpsd.src:164: W: macro-in-comment %{__install}
[   39s] gpsd.src:165: W: macro-in-comment %{__install}
[   39s] gpsd.src:168: W: macro-in-comment %{_libdir}
[   39s] gpsd.src:171: W: macro-in-comment %{__chmod}
[   39s] gpsd.src:171: W: macro-in-comment %{python_sitearch}
[   39s] gpsd.src:238: W: macro-in-comment %{_includedir}
[   39s] gpsd.src:246: W: macro-in-comment %defattr
[   39s] gpsd.src:247: W: macro-in-comment %{_qt4_libdir}
[   39s] gpsd.src:248: W: macro-in-comment %{_qt4_libdir}
[   39s] There is a unescaped macro after a shell style comment in the
specfile. Macros
[   39s] are expanded everywhere, so check if it can cause a problem in
this case and
[   39s] escape the macro with another leading % if appropriate.
[   39s]
[   39s] gpsd.i686: E: license-file-in-docs (Badness: 200)
/usr/share/doc/packages/gpsd/COPYING
[   39s] A file whose name suggests that it contains a license is included
in the
[   39s] package as a document. Such files need to be marked with %license
and not with
[   39s] %doc, which will install them in a special directory seperated
from the
[   39s] documentation.
[   39s]
[   39s] gpsd.i686: E: invalid-license (Badness: 200) BSD
[   39s] gpsd-clients-cli.i686: E: invalid-license (Badness: 200) BSD
[   39s] gpsd-clients-httpd.i686: E: invalid-license (Badness: 200) BSD
[   39s] gpsd-clients-x11.i686: E: invalid-license (Badness: 200) BSD
[   39s] gpsd-devel.i686: E: invalid-license (Badness: 200) BSD
[   39s] libQgpsmm.i686: E: invalid-license (Badness: 200) BSD
[   39s] gpsd-clients.i686: E: invalid-license (Badness: 200) BSD
[   39s] gpsd.src: E: invalid-license (Badness: 200) BSD
[   39s] The specified license string is not recognized. Please refer to
[   39s] http://spdx.org/licenses/ for the list of known licences and their
exact
[   39s] spelling.
[   39s]
[   39s] gpsd.i686: W: install-file-in-docs
/usr/share/doc/packages/gpsd/INSTALL
[   39s] A file whose name suggests that it contains installation
instructions is
[   39s] included in the package.  Such instructions are often not relevant
for already
[   39s] installed packages; if this is the case for this file and it does
not contain
[   39s] any information that is of interest after the package has been
built and
[   39s] installed, do not include the file in the binary package.
[   39s]
[   39s] gpsd.i686: W: init-script-without-%stop_on_removal-preun
/etc/init.d/gpsd
[   39s] The init script should have a %preun script that calls
%stop_on_removal.
[   39s]
[   39s] gpsd.i686: W: init-script-without-%restart_on_update-postun
/etc/init.d/gpsd
[   39s]  The package has an init script but is missing the
%restart_on_update call in
[   39s] %postun to automatically restart the daemon. This is optional, but
in most
[   39s] cases it is wanted. Please check.
[   39s]
[   39s] gpsd.i686: W: files-duplicate /usr/share/man/man1/gpsprof.1.gz
/usr/share/man/man1/gegps.1.gz
[   39s] gpsd-clients-cli.i686: W: files-duplicate
/usr/share/man/man1/lcdgps.1.gz /usr/share/man/man1/cgps.1.gz
[   39s] gpsd-clients-cli.i686: W: files-duplicate
/usr/share/man/man1/gpxlogger.1.gz /usr/share/man/man1/gpscat.1.gz
[   39s] gpsd-clients-x11.i686: W: files-duplicate
/usr/share/man/man1/xgps.1.gz /usr/share/man/man1/xgpsspeed.1.gz
[   39s] 8 packages and 0 specfiles checked; 15 errors, 21 warnings.




On Thu, Dec 4, 2014 at 1:14 PM, Rudolf Streif <[email protected]>
wrote:

> Jingjing and Mikko,
>
> Thank you for your help.
>
> Indeed removing the %{?dist} tag and replacing it with 0 got me over that
> hurdle. Now there are some other issues with packaging.
>
> Everything builds fine now. Gpsd uses scons for building. The sources
> build correctly and the installation into the build root works fine too. I
> traced everything through %install as working.
>
> It then fails on packaging:
>
> %files -n libQgpsmm
> %defattr(-,root,root,-)
> %{_qt4_libdir}/libQgpsmm.so*
> %{_qt4_libdir}/libQgpsmm.prl
> %{_mandir}/man3/libQgpsmm.3*
>
> The issue is that it cannot expand {_qt4_libdir}. If I comment them out
> that package is created with that manual only of course.
>
> It's writing all the packages into the build root. So far so good. But
> then rpmlint barfs (log attached). Most of the "badness" comes from the BSD
> license which apparently is not allowed for Tizen?
>
>
> Thanks,
> Rudi
>
> On Thu, Dec 4, 2014 at 12:44 AM, Li, JinjingX <[email protected]>
> wrote:
>
>>  Hi Rudolf Streif
>>
>>
>>
>> The root cause is rpm failed to parse the macro %{?dist} in Release
>> period during gbs build.
>>
>> Is the function of macro to get the kernel name of your current Linux or
>> else?
>>
>> I reproduced the issue on fedora20 as your vm, but gbs build ok on
>> opensuse13.1(whether is it the platform you mean?)
>>
>>
>>
>> On Fedora20_x86-64:
>>
>> *$ uname –a *
>>
>>    Linux bkd01sdp.bj.intel.com 3.11.10-301.*fc20*.x86_64 #1 SMP Thu Dec
>> 5 14:01:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>>
>> *$ rpm –q rpm*
>>
>> rpm-4.11.3-1.fc20.x86_64
>>
>> *$ gbs build fails as you did*
>>
>>
>>
>> On opensuse13.1_x86-64
>>
>> *$ uname –a*
>>
>>   Linux lbworker-163 3.11.10-21-default #1 SMP Mon Jul 21 15:28:46 UTC
>> 2014 (9a9565d) x86_64 x86_64 x86_64 GNU/Linux
>>
>> *$ rpm –q rpm*
>>
>>   rpm-4.11.1-6.5.1.x86_64
>>
>> *$ gbs build –A i586 –R*
>> http://download.tizen.org/snapshots/tizen/ivi/latest/repos/atom/packages/
>>  *-B ~/gpsd_br*
>>
>> info: generate repositories ...
>>
>> info: build conf has been downloaded at:
>>
>>       /var/tmp/jenkins-gbs/tizen.conf
>>
>> info: start building packages from: /srv/var-lib/jenkins/gpsd (git)
>>
>> 2014-12-04 06:59 +0200
>>
>> gbs 0.23
>>
>> info: prepare sources...
>>
>> info: start export source from: /srv/var-lib/jenkins/gpsd ...
>>
>> warning: Deprecated option '--git-export-only', please use '--no-build'
>> instead!
>>
>> info: Creating (native) source archive gpsd-3.11~dev.tar.gz from 'HEAD'
>>
>> info: package files have been exported to:
>>
>>      /var/lib/jenkins/gpsd_br/local/sources/tizen/*gpsd-3.11~dev-1*
>>
>> info: retrieving repo metadata...
>>
>> info: parsing package data...
>>
>> info: building repo metadata ...
>>
>> info: resolving skipped packages ...
>>
>> info: package dependency resolving ...
>>
>> info: *** Build Status Summary ***
>>
>> === the following packages failed to build due to missing build
>> dependencies
>> (1)
>> ===
>>
>> gpsd:
>>
>>   nothing provides bluez-libs-devel
>>
>>   nothing provides libXaw-devel
>>
>>   nothing provides qt-devel
>>
>>
>>
>> === Total succeeded built packages: (0) ===
>>
>> info: generated html format report:
>>
>>      /var/lib/jenkins/gpsd_br/local/repos/tizen/i586/index.html
>>
>> info: generated RPM packages can be found from local repo:
>>
>>      /var/lib/jenkins/gpsd_br/local/repos/tizen/i586/RPMS
>>
>> info: generated source RPM packages can be found from local repo:
>>
>>      /var/lib/jenkins/gpsd_br/local/repos/tizen/i586/SRPMS
>>
>> info: build logs can be found in:
>>
>>      /var/lib/jenkins/gpsd_br/local/repos/tizen/i586/logs
>>
>> info: build roots located in:
>>
>>      /var/lib/jenkins/gpsd_br/local/BUILD-ROOTS/scratch.i586.*
>>
>> error: <gbs>some packages failed to be built
>>
>>
>>
>> You could try to remove the macro %{?dist} in Release in specfile, if it
>> doesn’t very important,  gbs build will ok.
>>
>>
>>
>> Thanks
>>
>> Li Jinjing
>>
>> *From:* Dev [mailto:[email protected]] *On Behalf Of *Rudolf
>> Streif
>> *Sent:* Thursday, December 04, 2014 9:36 AM
>> *To:* [email protected]
>> *Subject:* [Dev] Fwd: Building GPSD for Tizen with GBS
>>
>>
>>
>> I am trying to build gpsd for Tizen IVI. It builds fine on the platform
>> itself. Now I am trying to build it with GBS. The gpsd package provides a
>> spec file for RPM packaging.
>>
>>
>>
>> When I am trying to build with GBS I am getting the following warning
>> about exporting the spec file and no packages are built [1]. Unfortunately
>> GBS is not very specific about the issue. The spec file looks reasonable to
>> me though. Spec file is attached.
>>
>>
>>
>> Thanks,
>>
>> Rudi
>>
>>
>>
>>
>>
>>
>>
>> [1]
>>
>>
>>
>> gbs -c ../gbs.tizen-3.0.conf build -A i586
>>
>> info: generate repositories ...
>>
>> info: build conf has been downloaded at:
>>
>>       /var/tmp/rudi-gbs/tizen3.0_m3_oct2014.conf
>>
>> info: start building packages from:
>> /home/rudi/Dropbox/Develop/Tizen/Source/gpsd-3.11 (git)
>>
>> 2014-12-03 17:32 -0800
>>
>> gbs 0.22.3
>>
>> info: prepare sources...
>>
>> info: start export source from:
>> /home/rudi/Dropbox/Develop/Tizen/Source/gpsd-3.11 ...
>>
>> info: Creating (native) source archive gpsd-3.11~dev.tar.gz from 'HEAD'
>>
>> info: package files have been exported to:
>>
>>
>>  /home/rudi/GBS-ROOT/local/sources/tizen3.0_m3_oct2014/gpsd-3.11~dev-1.fc20
>>
>> warning: spec file gpsd.spec has not been exported to
>> /home/rudi/GBS-ROOT/local/sources/tizen3.0_m3_oct2014/gpsd-3.11~dev-1/
>> correctly, please check if there're special macros in Name/Version/Release
>> fields
>>
>> info: retrieving repo metadata...
>>
>> info: parsing package data...
>>
>> info: building repo metadata ...
>>
>> info: resolving skipped packages ...
>>
>> info: package dependency resolving ...
>>
>> warning: no available packages to build.
>>
>> info: *** Build Status Summary ***
>>
>> === Total succeeded built packages: (0) ===
>>
>> info: generated html format report:
>>
>>      /home/rudi/GBS-ROOT/local/repos/tizen3.0_m3_oct2014/i586/index.html
>>
>> info: generated RPM packages can be found from local repo:
>>
>>      /home/rudi/GBS-ROOT/local/repos/tizen3.0_m3_oct2014/i586/RPMS
>>
>> info: generated source RPM packages can be found from local repo:
>>
>>      /home/rudi/GBS-ROOT/local/repos/tizen3.0_m3_oct2014/i586/SRPMS
>>
>> info: build logs can be found in:
>>
>>      /home/rudi/GBS-ROOT/local/repos/tizen3.0_m3_oct2014/i586/logs
>>
>> info: build roots located in:
>>
>>      /home/rudi/GBS-ROOT/local/BUILD-ROOTS/scratch.i586.*
>>
>> error: <gbs>some packages failed to be built
>>
>>
>>
>>
>>
>> --
>>
>> *Rudolf J. Streif*
>>
>>
>>
>>
>>
>>
>>
>> --
>>
>> *Rudolf J. Streif*
>>
>>
>>
>
>
>
> --
> *Rudolf J. Streif*
>
>


-- 
*Rudolf J. Streif*
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to