[Starlingx-discuss] Problems build-iso in centos8 environment

Saul Wold sgw at linux.intel.com
Thu Dec 12 22:27:39 UTC 2019



On 12/11/19 11:17 PM, fuyong wrote:
> *Hi StarlingX team*
> 
> I’m upgrading starlingx to centos8 and have a question to ask for help.
> 
> *problem:*
> 
> *When I run the build-iso command in the centos8 build container 
> environment, I find that the build-tools / build_iso / cgts_deps.sh 
> script runs with some issues.*
> 
> 1.I cannot add multiple parameters after the “repoquery –whatprovides” 
> command.
> 
> 2.Unable to query some dependencies through “repoquery –whatprovides” 
> command.
> 
Hi Fuyong:

First off, as I have mentioned before DNF replaced YUM and associated 
commands, which repoquery is one of. It's likely that the DNF variation 
is not exactly the same, so your seeing this change in behavior. 
Depending on the usage in the build tools scripts, we might have to 
account for that change and modify the scripts.

Sau!
> *Eg1:*
> 
> *In the centos7 build container environment, the following commands can 
> be executed normally. You can see that multiple parameters can be added 
> after repoquery –whatprovides*
> 
> *Centos7:*
> 
> [lymtics at ba0d929a1011 /]$ repoquery -c 
> /localdisk/loadbuild/lymtics/starlingx/export/yum.conf 
> --repoid=TisCentos7Distro --arch=x86_64,noarch --whatprovides 
> 'libattr.so.1()(64bit)' 'libc.so.6()(64bit)' 
> 'libc.so.6(GLIBC_2.14)(64bit)' 'libc.so.6(GLIBC_2.2.5)(64bit)' 
> 'libc.so.6(GLIBC_2.3.4)(64bit)' 'libc.so.6(GLIBC_2.3)(64bit)' 
> 'libc.so.6(GLIBC_2.4)(64bit)' 'rtld(GNU_HASH)' '--qf=%{name}'
> 
> libattr
> 
> glibc
> 
> glibc
> 
> glibc
> 
> glibc
> 
> glibc
> 
> glibc
> 
> glibc
> 
> *But it is invalid in the centos8 build container environment.*
> 
> *centos8:*
> 
> [lymtics at aa4a04b2f1f7 export]$ repoquery -c 
> /localdisk/loadbuild/lymtics/starlingx/export/yum.conf 
> --repoid=TisCentos8Distro --arch=x86_64,noarch --whatprovides 
> 'libattr.so.1()(64bit)' 'libc.so.6()(64bit)' 
> 'libc.so.6(GLIBC_2.14)(64bit)' 'libc.so.6(GLIBC_2.2.5)(64bit)' 
> 'libc.so.6(GLIBC_2.3.4)(64bit)' 'libc.so.6(GLIBC_2.3)(64bit)' 
> 'libc.so.6(GLIBC_2.4)(64bit)' 'rtld(GNU_HASH)' '--qf=%{name}'
> 
> Last metadata expiration check: 0:09:25 ago on Wed 11 Dec 2019 03:09:45 
> AM UTC.
> 
> *If I query one parameter at a time, I can query the results correctly 
> in centos8.*
> 
> **
> 
> *Eg2:*
> 
> *In the centos7 build container environment, the following commands can 
> be executed normally.*
> 
> [lymtics at ba0d929a1011 export]$ repoquery -c 
> /localdisk/loadbuild/lymtics/starlingx/export/yum.conf 
> --repoid=TisCentos7Distro --arch=x86_64,noarch --whatprovides *libacl = 
> 2.2.51-14.el7* '--qf=%{name}'
> libacl**
> 
> **
> 
> *But it is invalid in the centos8 build container environment.*
> 
> *centos8:*
> 
> [lymtics at 07e4fd4ae0c8 export]$ repoquery -c 
> /localdisk/loadbuild/lymtics/starlingx/export/yum.conf 
> --repoid=TisCentos8Distro --arch=x86_64,noarch --whatprovides *libacl = 
> 2.2.53-1.el8* '--qf=%{name}'
> Last metadata expiration check: 0:03:40 ago on Wed 11 Dec 2019 03:41:17 
> AM UTC.
> 
> **
> 
> **
> 
> please contact me, If you have any good suggestions.
> 
> Thank you
> 
> **
> 
> Best Regards
> 
> Wish you happy everyday!
> 
> --------------------------------
> 
> Yong.Fu- Neusoft
> 
> 
> ---------------------------------------------------------------------------------------------------
> Confidentiality Notice: The information contained in this e-mail and any 
> accompanying attachment(s)
> is intended only for the use of the intended recipient and may be 
> confidential and/or privileged of
> Neusoft Corporation, its subsidiaries and/or its affiliates. If any 
> reader of this communication is
> not the intended recipient, unauthorized use, forwarding, printing,  
> storing, disclosure or copying
> is strictly prohibited, and may be unlawful.If you have received this 
> communication in error,please
> immediately notify the sender by return e-mail, and delete the original 
> message and all copies from
> your system. Thank you.
> ---------------------------------------------------------------------------------------------------
> 
> 
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> 



More information about the Starlingx-discuss mailing list