[Dev] Build problems with GBS

김현우 hwlove.kim at samsung.com
Sat Oct 5 08:31:48 GMT 2013


Dear Krzysztof Opasiak and Anas Nashif,

I just modified __os_install_post in hash-signer following rpm-tizen_macros file in rpm package temporarily.
So you can build packages which use hash-signer.
And I will modify signing code as Anas Nashif's guide in next week.

Regards,
Hyunwoo Kim.

------- Original Message -------
Sender : Nashif, Anas<anas.nashif at intel.com> 
Date   : 2013-10-04 23:02 (GMT+09:00)
Title  : Re: [Dev] Build problems with GBS

The solution is to put that signing code in

/usr/lib/rpm/brp-tizen.d/brp-sign

then /usr/lib/rpm/brp-tizen will run all scripts in

/usr/lib/rpm/brp-tizen.d/



This is how the post_install can be extended from packages, not by
replacing the macro.

Anas


On 04/10/2013 09:56, "Krzysztof Opasiak" <k.opasiak at samsung.com> wrote:

>Dear Jaewon Lee,
>
>Could you provide us solution for below problem, it comes from package
>which you maintain?
>
>BRs,
>Krzysztof Opasiak
>
>> -----Original Message-----
>> From: Kanevskiy, Alexander [mailto:alexander.kanevskiy at intel.com]
>> Sent: Friday, October 04, 2013 3:35 PM
>> To: Nashif, Anas; so.yu at samsung.com; Krzysztof Opasiak;
>> dev at lists.tizen.org
>> Subject: Re: [Dev] Build problems with GBS
>> 
>> On 10/4/13 16:12 , "Nashif, Anas" <anas.nashif at intel.com> wrote:
>> 
>> 
>> IMO, redefining this kind of global macros in some packages doesn't
>> make
>> any sense.
>> 
>> If we have some Tizen specifics that should be applied on many
>> packages,
>> then probably it would be best place to have such macros in one
>> place
>> (e.g. rpm) ?
>> That would allow to properly sync contents of those and will make
>> sure
>> that relevant people with good knowledge on macros would be
>> reviewing them.
>> 
>> 
>> >The package hash-signer replaces the default os_install_post from
>> rpm and
>> >replaces that with:
>> >
>> >
>> >%__os_install_post    \r
>> >    /usr/lib/rpm//brp-compress \r
>> >    %{!?__debug_package:/usr/lib/rpm/brp-strip %{__strip}} \r
>> >    /usr/lib/rpm/brp-strip-static-archive %{__strip} \r
>> >    /usr/lib/rpm/brp-strip-comment-note %{__strip} %{__objdump} \r
>> >    /usr/lib/rpm/brp-python-bytecompile \r
>> >    /usr/lib/rpm/brp-python-hardlink \r
>> >    %{!?disable_docs_package:/usr/lib/rpm/tizen/find-docs.sh
>> %{buildroot}}
>> >\r
>> >    %{?tizen_author_sign: %define tizen_author_flag -a} \r
>> >    %{?tizen_dist_sign: %define tizen_dist_flag -d} \r
>> >    %{?tizen_sign:/usr/bin/hash-signer.sh %tizen_author_flag
>> >%tizen_dist_flag -p %tizen_sign_level  -b $RPM_BUILD_ROOT
>> >"%tizen_sign_base"} \r
>> >%{nil}
>> >
>> >
>> >
>> >So, anything that depends on hash-signer will fail, not sure what
>> that is
>> >and why it is needed.
>> >
>> >So the problem is not RPM, the problem is hash-signer.
>> >
>> >
>> >Anas
>> >
>> >
>> >On 04/10/2013 08:34, "Seungmin Yu" <so.yu at samsung.com> wrote:
>> >
>> >>Dear all,
>> >>
>> >>I faced same problem against osp-security-service.
>> >>To avoid the build error, I added following into %install
>> section.
>> >>
>> >>%global __os_install_post  \r
>> >>    /usr/lib/rpm/brp-compress \r
>> >>    /usr/lib/rpm/brp-tizen  \r
>> >>    %{!?disable_docs_package:/usr/lib/rpm/tizen/find-docs.sh
>> >>%{buildroot}} \r
>> >>%{nil}
>> >>
>> >>Maybe, there is a problem in rpm macros of 'rpm' package.
>> >>'brp-strip-static-archive' is removed by the spec file of 'rpm'
>> package,
>> >>thus it have to removed on postscript.
>> >>
>> >>[   90s] /var/tmp/rpm-tmp.XpS4yV: line 55:
>> >>/usr/lib/rpm/brp-strip-static-archive: No such file or directory
>> >>
>> >>
>> >>Thanks and regards,
>> >>Seungmin Yu
>> >>
>> >>
>> >>------- Original Message -------
>> >>Sender : Krzysztof Opasiak<k.opasiak at samsung.com> Junior Software
>> >>Engineer/SRPOL-Kernel & System Framework (SSD)/삼성전자
>> >>Date : 2013-10-04 01:41 (GMT+09:00)
>> >>Title : [Dev] Build problems with GBS
>> >>
>> >>Dear all,
>> >>I'm working with some packages to help build Tizen image.
>> Recently I
>> >>took up osp-channel-service and osp-connectivity-service. I
>> figured out
>> >>that the problem was in not using pkgconfig by those two and in
>> missing
>> >>dependency to appinfo in appfw package. Please review my patches
>> and
>> >>merge them as soon as possible:
>> >>
>> >>[1] https://review.tizen.org/gerrit/10524
>> >>[2] https://review.tizen.org/gerrit/10532
>> >>[3] https://review.tizen.org/gerrit/10533
>> >>
>> >>When I was trying to build osp-channel-service [2] with my patch
>> I
>> >>experienced some new problem with gbs: Build (install part
>> exactly) was
>> >>failed due to missing brp-strip-static-archive and
>> >>brp-strip-comment-note scripts form rpm. I had to cp them
>> manually from
>> >>rpm repository to suitable directory in my build root and then
>> >>everything works fine. I know that this is only some walk around
>> but I
>> >>have no idea where those errors come from? Can anyone help with
>> it?
>> >>
>> >>BR's
>> >>
>> >>---
>> >>Krzysztof Opasiak
>> >>Samsung R&D Institute Poland
>> >>Samsung Electronics
>> >>k.opasiak at samsung.com
>> >>
>> >>
>> >>
>> >>_______________________________________________
>> >>Dev mailing list
>> >>Dev at lists.tizen.org
>> >>https://lists.tizen.org/listinfo/dev
>> >>
>> >>
>> >>
>> >>
>> >
>> >_______________________________________________
>> >Dev mailing list
>> >Dev at lists.tizen.org
>> >https://lists.tizen.org/listinfo/dev
>> >
>> 
>> 
>> --
>> Best regards, Alexander Kanevskiy.
>> 
>> 
>> 
>> -------------------------------------------------------------------
>> --
>> Intel Finland Oy
>> Registered Address: PL 281, 00181 Helsinki
>> Business Identity Code: 0357606 - 4
>> Domiciled in Helsinki
>> 
>> This e-mail and any attachments may contain confidential material
>> for
>> the sole use of the intended recipient(s). Any review or
>> distribution
>> by others is strictly prohibited. If you are not the intended
>> recipient, please contact the sender and delete all copies.
>
>

_______________________________________________
Dev mailing list
Dev at lists.tizen.org
https://lists.tizen.org/listinfo/dev
<p> </p><p> </p>


More information about the Dev mailing list