gnutls-2.12.14-r3.1 - strange rpm names yocto
Hello guys,
I've been plying along with yocto lately and managed to understand at a decent level it's work-flow and components.
Today wanted to complete an image-core-minimal for arm using packages that are not GPLv3 using (found in manual):
#EXTRA_IMAGE_FEATURES = "debug-tweaks"INCOMPATIBLE_LICENSE = "GPLv3"
Further more i wanted to compile gnutls and i think that i came across a bug. In the bb file (poky/meta/recipes-support/gnutls/gnutls_2.12.14.bb) the rules for pakages are:
PACKAGES =+ "${PN}-openssl ${PN}-extra ${PN}-bin ${PN}-xx"
FILES_${PN} = "${libdir}/libgnutls.so.*"
FILES_${PN}-bin = "${bindir}/gnutls-serv \
${bindir}/gnutls-cli \
${bindir}/srptool \
${bindir}/psktool \
${bindir}/p11tool \
${bindir}/certtool \
${bindir}/gnutls-srpcrypt"FILES_${PN}-dev += "${bindir}/*-config ${bindir}/gnutls-cli-debug" FILES_${PN}-extra = "${libdir}/libgnutls-extra.so.*" FILES_${PN}-openssl = "${libdir}/libgnutls-openssl.so.*" FILES_${PN}-xx = "${libdir}/libgnutlsxx.so.*"
So the rpms should be named gnutls-dev, gnutls-bin etc etc.
Well... this is not true cause in the tmp/work/armv5te-poky-linux-gnueabi/gnutls-2.12.14-r3.1/deploy-rpms directory i found:
drwxr-xr-x 2 agherzan agherzan 4096 2011-12-09 23:47 .
drwxrwxr-x 3 agherzan agherzan 4096 2011-12-09 23:46 ..
-rw-r--r-- 1 agherzan agherzan 306281 2011-12-09 23:47 libgnutls26-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 107347 2011-12-09 23:47 libgnutls-bin-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 1667211 2011-12-09 23:47 libgnutls-dbg-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 63017 2011-12-09 23:47 libgnutls-dev-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 799229 2011-12-09 23:47 libgnutls-doc-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 17962 2011-12-09 23:47 libgnutls-extra26-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 12240 2011-12-09 23:47 libgnutls-locale-cs-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 7992 2011-12-09 23:47 libgnutls-locale-de-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 10241 2011-12-09 23:47 libgnutls-locale-en+boldquot-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 10192 2011-12-09 23:47 libgnutls-locale-en+quot-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 12095 2011-12-09 23:47 libgnutls-locale-fr-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 11857 2011-12-09 23:47 libgnutls-locale-it-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 10325 2011-12-09 23:47 libgnutls-locale-ms-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 11858 2011-12-09 23:47 libgnutls-locale-nl-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 11973 2011-12-09 23:47 libgnutls-locale-pl-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 11773 2011-12-09 23:47 libgnutls-locale-sv-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 12338 2011-12-09 23:47 libgnutls-locale-vi-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 10521 2011-12-09 23:47 libgnutls-locale-zh-cn-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 18005 2011-12-09 23:47 libgnutls-openssl27-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 1795460 2011-12-09 23:47 libgnutls-staticdev-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 18524 2011-12-09 23:47 libgnutlsxx27-2.12.14-r3.1.armv5te.rpm
More infos: I'm using multithreading building and my last commit in poky is "commit af7fbd6083f4b5f1770e58fe0a2262951037c176."
I just cannot understand how these names are built. More, what are libgnutls-openssl27 and libgnutlsxx27?
Quoted 79 lines · Andrei Gherzan
Hello guys,
I've been plying along with yocto lately and managed to understand at a decent level it's work-flow and components.
Today wanted to complete an image-core-minimal for arm using packages that are not GPLv3 using (found in manual):
#EXTRA_IMAGE_FEATURES = "debug-tweaks"INCOMPATIBLE_LICENSE= "GPLv3"Further more i wanted to compile gnutls and i think that i came across a bug. In the bb file (poky/meta/recipes-support/gnutls/gnutls_2.12.14.bb) the rules for pakages are:
PACKAGES =+ "${PN}-openssl ${PN}-extra ${PN}-bin ${PN}-xx"FILES_${PN} = "${libdir}/libgnutls.so.*"
FILES_${PN}-bin = "${bindir}/gnutls-serv \ ${bindir}/gnutls-cli \ ${bindir}/srptool \ ${bindir}/psktool \ ${bindir}/p11tool \ ${bindir}/certtool \ ${bindir}/gnutls-srpcrypt"FILES_${PN}-dev += "${bindir}/*-config ${bindir}/gnutls-cli-debug" FILES_${PN}-extra = "${libdir}/libgnutls-extra.so.*" FILES_${PN}-openssl = "${libdir}/libgnutls-openssl.so.*" FILES_${PN}-xx = "${libdir}/libgnutlsxx.so.*"
So the rpms should be named gnutls-dev, gnutls-bin etc etc. Well... this is not true cause in the tmp/work/armv5te-poky-linux-gnueabi/gnutls-2.12.14-r3.1/deploy-rpms directory i found:
drwxr-xr-x 2 agherzan agherzan 4096 2011-12-09 23:47 .
drwxrwxr-x 3 agherzan agherzan 4096 2011-12-09 23:46 ..
-rw-r--r-- 1 agherzan agherzan 306281 2011-12-09 23:47 libgnutls26-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 107347 2011-12-09 23:47 libgnutls-bin-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 1667211 2011-12-09 23:47 libgnutls-dbg-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 63017 2011-12-09 23:47
libgnutls-dev-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 799229 2011-12-09 23:47 libgnutls-doc-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 17962 2011-12-09 23:47
libgnutls-extra26-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 12240 2011-12-09 23:47
libgnutls-locale-cs-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 7992 2011-12-09 23:47
libgnutls-locale-de-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 10241 2011-12-09 23:47
libgnutls-locale-en+boldquot-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 10192 2011-12-09 23:47
libgnutls-locale-en+quot-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 12095 2011-12-09 23:47
libgnutls-locale-fr-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 11857 2011-12-09 23:47
libgnutls-locale-it-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 10325 2011-12-09 23:47
libgnutls-locale-ms-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 11858 2011-12-09 23:47
libgnutls-locale-nl-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 11973 2011-12-09 23:47
libgnutls-locale-pl-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 11773 2011-12-09 23:47
libgnutls-locale-sv-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 12338 2011-12-09 23:47
libgnutls-locale-vi-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 10521 2011-12-09 23:47
libgnutls-locale-zh-cn-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 18005 2011-12-09 23:47
libgnutls-openssl27-2.12.14-r3.1.armv5te.rpm -rw-r--r-- 1 agherzan agherzan 1795460 2011-12-09 23:47 libgnutls-staticdev-2.12.14-r3.1.armv5te.rpm
-rw-r--r-- 1 agherzan agherzan 18524 2011-12-09 23:47
libgnutlsxx27-2.12.14-r3.1.armv5te.rpm
Quoted 5 lines
More infos: I'm using multithreading building and my last commit in poky is "commit
af7fbd6083f4b5f1770e58fe0a2262951037c176."I just cannot understand how these names are built. More, what are libgnutls-openssl27 and libgnutlsxx27?
This looks like our debian-style package renaming, which renames libraries to include the lib prefix.
We have a brief blurb about it here:
http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-classes-debian
Regards,
Joshua
Signature · 3 lines
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology CentreQuoted 9 lines
This looks like our debian-style package renaming, which renames libraries to include the lib prefix.
We have a brief blurb about it here:
http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-classes-debianRegards,
Joshua
Yes it looks like. But here is the problem: i included this pkg in IMAGE-INSTALL and i found library from -extra with even if LICENSE_${PN}-extra = "GPLv3+"
And i think that this could be because of this name style change.
Signature · 8 lines
*Andrei Gherzan*, Engineer mobile +40.744.478.414 fax +40.031.816.28.12 Email: [email protected] Email: [email protected] Romania Acest e-mail reprezinta corespondenta pentru care dumneavoastra v-ati exprimat acordul si se supune politicii noastre de anti-spamming. Daca totusi considerati ca acest email reprezinta spamming va rugam sa ne contactati folosind e-mail-ul [email protected]. Multumim.
Quoted 7 lines · Andrei Gherzan
Quoted 7 lines
This looks like our debian-style package renaming, which renames libraries to include the lib prefix.
We have a brief blurb about it here:
http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-classes-debian
Quoted 8 lines
Quoted 2 lines
Regards,
JoshuaYes it looks like. But here is the problem: i included this pkg in IMAGE-INSTALL and i found library from -extra with even if
LICENSE_${PN}-extra = "GPLv3+"And i think that this could be because of this name style change.
There are two issues here. The first is that IMAGE_INSTALL is the binary package name. This name can be munged with the renaming as Joshua mentioned. Most people assume that this name matches the source recipe name. So there is confusion to deal with.
The other issue is that any place a user is asked to list a -binary- package name, it should go through the same munging process as it does when things are generated. The IMAGE_INSTALL does not do this at this time. (It -really- should!) This has been on my list of things to work on for a while now, but I have not had the time to get to it.
Patches are welcome! ;)
--Mark
Quoted 17 lines
--
*Andrei Gherzan*, Engineer
mobile +40.744.478.414 fax +40.031.816.28.12
Email: [email protected]
Email: [email protected]
RomaniaAcest e-mail reprezinta corespondenta pentru care dumneavoastra v-ati exprimat acordul si se supune politicii noastre de anti-spamming.
Daca totusi considerati ca acest email reprezinta spamming va rugam sa ne contactati folosind e-mail-ul [email protected]. Multumim._______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Quoted 22 lines · Mark Hatle
Quoted 7 lines · Andrei Gherzan
Quoted 7 lines
This looks like our debian-style package renaming, which renames libraries to include the lib prefix.
We have a brief blurb about it here:
http://www.yoctoproject.org/docs/current/poky-ref-manual/poky-ref-manual.html#ref-classes-debianQuoted 8 lines
Quoted 2 lines
Regards,
JoshuaYes it looks like. But here is the problem: i included this pkg in IMAGE-INSTALL and i found library from -extra with even if
LICENSE_${PN}-extra = "GPLv3+"And i think that this could be because of this name style change.
There are two issues here. The first is that
IMAGE_INSTALLis the binary package name. This name can be munged with the renaming as Joshua mentioned. Most people assume that this name matches the source recipe name. So there is confusion to deal with.
Quoted 7 lines
The other issue is that any place a user is asked to list a -binary- package name, it should go through the same munging process as it does when things are generated. The
IMAGE_INSTALLdoes not do this at this time. (It -really- should!) This has been on my list of things to work on for a while now, but I have not had the time to get to it.Patches are welcome! ;)
To quote image.bbclass:
export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${FEATURE_INSTALL}"
python () {
# If we don't do this we try and run the mapping hooks while parsing which is slow # bitbake should really provide something to let us know this...
if d.getVar('BB_WORKERCONTEXT', True) is not None:
runtime_mapping_rename("PACKAGE_INSTALL", d) runtime_mapping_rename("PACKAGE_INSTALL_ATTEMPTONLY", d)
}
so as far as I know, the remapping does work.
Cheers,
Richard
Bug added to bugzilla:
*Bug 1845* <http://bugzilla.yoctoproject.org/show_bug.cgi?id=1845>-gnutls-2.12.14-r3.1 - GPLv3 license rpm present in a non-GPLv3 build(edit <http://bugzilla.yoctoproject.org/post_bug.cgi#>)
Quoted 6 lines · Andrei Gherzan
Bug added to bugzilla:
*Bug 1845*
<http://bugzilla.yoctoproject.org/show_bug.cgi?id=1845>-gnutls-2.12.14-r3.1
- GPLv3 license rpm present in a non-GPLv3 build(edit
<http://bugzilla.yoctoproject.org/post_bug.cgi#>)
Any chance of getting you to provide the patch for this also? If so, I can assign this bug to you.
Thanks
Sau!
Quoted 5 lines
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky
I can look over this as well but there would be a problem: i don't know what solution to choose. I can take this package out from WHITELIST, ican make wpa_supplicant to compile with openssl and not with gnutls... i can compile wpa-supplicant without gnutls-extra and so on... What do you say?
Quoted 5 lines · Andrei Gherzan
I can look over this as well but there would be a problem: i don't know what solution to choose. I can take this package out from WHITELIST, ican make
wpa_supplicantto compile with openssl and not with gnutls... i can compile wpa-supplicant without gnutls-extra and so on... What do you say?
I think it needs to stay in the WHITELIST for know, until we have some kind of future change that can determine package based LICENSE info and build accordingly (that's a different issue then this right now).
What does wpa-supplicant use from gnutls-extra? What functionality could be lost? This might be the best approach, and could be a conditional patch based on GPLv3 or not (see code in util-linux_2.19.1)
For WPA-supplicant and openssl, are there know issues?
Sau!
Quoted 5 lines
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Quoted 6 lines · Saul Wold
Quoted 5 lines · Andrei Gherzan
I can look over this as well but there would be a problem: i don't know what solution to choose. I can take this package out from WHITELIST, ican make
wpa_supplicantto compile with openssl and not with gnutls... i can compile wpa-supplicant without gnutls-extra and so on... What do you say?
Quoted 13 lines
I think it needs to stay in the WHITELIST for know, until we have some kind of future change that can determine package based LICENSE info and build accordingly (that's a different issue then this right now).
What does wpa-supplicant use from gnutls-extra? What functionality could be lost? This might be the best approach, and could be a conditional patch based on GPLv3 or not (see code in util-linux_2.19.1)
For WPA-supplicant and openssl, are there know issues?
Sau!
Quoted 5 lines
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky
Well things seem to be like this. wpa-supplicant has 3 ways of implementing TLS:
1. internal
2. openssl
3. gnutls + optional gnutls extra.
For internal there are only these features:
1. can be used in place of an external TLS/crypto library
2. TLSv1
3. X.509 certificate processing
4. PKCS #1
5. ASN.1
6. RSA
7. bignum
8. minimal size (ca. 50 kB binary, parts of which are already needed for WPA; TLSv1/X.509/ASN.1/RSA/bignum parts are about 25 kB on x86)
OpenSSL has a license problem (as i recall). It is not GPL compatible.
gnutls comes optionally with gnutls-extra. This rpm implements TLS/IA.
"The TLS/IA protocol was designed to be used in the EAP-TTLSv1 protocol, to perform user authentication of Wireless LAN network nodes using IEEE 802.1x. The TLS/IA and TTLSv1 protocols were published through the IETF and descriptions"
My choice would be to eliminate this feature and build wpa-suplicant without gnutls-extra. In this way we have a solid TLS implementations, GPL compatible with a little compromise. Obviously, this would be only in a non-GPLv3 build.
Quoted 51 lines · Andrei Gherzan
Quoted 10 lines · Saul Wold
Quoted 5 lines · Andrei Gherzan
I can look over this as well but there would be a problem: i don't know what solution to choose. I can take this package out from WHITELIST, ican make
wpa_supplicantto compile with openssl and not with gnutls... i can compile wpa-supplicant without gnutls-extra and so on... What do you say?I think it needs to stay in the WHITELIST for know, until we have some kind of future change that can determine package based LICENSE info and build accordingly (that's a different issue then this right now).
Quoted 13 lines
What does wpa-supplicant use from gnutls-extra? What functionality could be lost? This might be the best approach, and could be a conditional patch based on GPLv3 or not (see code in util-linux_2.19.1)
For WPA-supplicant and openssl, are there know issues?
Sau!
Quoted 5 lines
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/pokyWell things seem to be like this. wpa-supplicant has 3 ways of implementing TLS:
1. internal
2. openssl
3. gnutls + optional gnutls extra.For internal there are only these features:
1. can be used in place of an external TLS/crypto library
2. TLSv1
3. X.509 certificate processing
4. PKCS #1
5. ASN.1
6. RSA
7. bignum
8. minimal size (ca. 50 kB binary, parts of which are already needed for WPA; TLSv1/X.509/ASN.1/RSA/bignum parts are about 25 kB on x86)OpenSSL has a license problem (as i recall). It is not GPL compatible.
gnutls comes optionally with gnutls-extra. This rpm implements TLS/IA.
"The TLS/IA protocol was designed to be used in the EAP-TTLSv1 protocol, to perform user authentication of Wireless LAN network nodes using IEEE 802.1x. The TLS/IA and TTLSv1 protocols were published through the IETF and descriptions"
Quoted 4 lines
My choice would be to eliminate this feature and build wpa-suplicant without gnutls-extra. In this way we have a solid TLS implementations, GPL compatible with a little compromise. Obviously, this would be only in a non-GPLv3 build.
That was also the direction I was leaning as you might have been able to tell, I just to be sure of the functionality lose. Do you think it's possible to implement it as a conditional on the INCOMPATIBLE_LICENSE having GPLv3?
Thanks again
Sau!
Yes. Absolutely. I will attach a patch to that bug today.
Quoted 69 lines · Saul Wold
Quoted 54 lines · Andrei Gherzan
Quoted 16 lines · Saul Wold
Quoted 6 lines · Andrei Gherzan
I can look over this as well but there would be a problem: i don't know what solution to choose. I can take this package out from WHITELIST, ican make
wpa_supplicantto compile with openssl and not with gnutls... i can compile wpa-supplicant without gnutls-extra and so on... What do you say?I think it needs to stay in the WHITELIST for know, until we have some kind of future change that can determine package based LICENSE info and build accordingly (that's a different issue then this right now).
What does wpa-supplicant use from gnutls-extra? What functionality could be lost? This might be the best approach, and could be a conditional patch based on GPLv3 or not (see code in util-linux_2.19.1)
Quoted 10 lines
For WPA-supplicant and openssl, are there know issues?
Sau!
______________________________**_________________
Quoted 5 lines
poky mailing list
[email protected]
https://lists.yoctoproject.**org/listinfo/poky<https://lists.yoctoproject.org/listinfo/poky>Well things seem to be like this. wpa-supplicant has 3 ways of implementing TLS:
1. internal
2. openssl
3. gnutls + optional gnutls extra.For internal there are only these features:
1. can be used in place of an external TLS/crypto library
2. TLSv1
3. X.509 certificate processing
4. PKCS #1
5. ASN.1
6. RSA
7. bignum
8. minimal size (ca. 50 kB binary, parts of which are already needed for WPA; TLSv1/X.509/ASN.1/RSA/bignum parts are about 25 kB on x86)OpenSSL has a license problem (as i recall). It is not GPL compatible.
gnutls comes optionally with gnutls-extra. This rpm implements TLS/IA.
"The TLS/IA protocol was designed to be used in the EAP-TTLSv1 protocol, to perform user authentication of Wireless LAN network nodes using IEEE 802.1x. The TLS/IA and TTLSv1 protocols were published through the IETF and descriptions"
Quoted 5 lines
My choice would be to eliminate this feature and build wpa-suplicant without gnutls-extra. In this way we have a solid TLS implementations, GPL compatible with a little compromise. Obviously, this would be only in a non-GPLv3 build.
That was also the direction I was leaning as you might have been able to tell, I just to be sure of the functionality lose. Do you think it's possible to implement it as a conditional on the
INCOMPATIBLE_LICENSEhaving GPLv3?Thanks again
Sau!
Bug attached to:
Sorry for the typo. I ment: "patch attached to".
Quoted 4 lines · Andrei Gherzan
Bug attached to: