Re: [yocto] [opkg-devel] [PATCH][opkg] bug 13528 add SPDX id to opkg

2019-10-25 Thread Yann CARDAILLAC 
Hi Alejandro,

Here's patch v2

Thanks for your sharpened eyes !

Regards,

On Thu, Oct 24, 2019 at 9:39 PM Alejandro Del Castillo <
alejandro.delcasti...@ni.com> wrote:

> Hi Yann,
>
> Thanks again for adding the headers. Your patch looks good, except for
> one line that has a duplicated header:
>
> /core/26_prefer_arch_to_version.py
> index 0a0d66b..82934c1 100755
> --- a/tests/core/26_prefer_arch_to_version.py
> +++ b/tests/core/26_prefer_arch_to_version.py
> @@ -1,4 +1,5 @@
> -#! /usr/bin/env python3
> +#! /usr/bin/env python3# SPDX-License-Identifier: GPL-2.0-only
> +# SPDX-License-Identifier: GPL-2.0-only
>   #
>
> could you send a v2? regarding m4 files, I looked around a bit and
> didn't find project adding SPDX identifiers to them
>
> Cheers,
>
> Alejandro
>
> On 10/22/19 9:55 AM, Yann CARDAILLAC wrote:
> > Hi,
> >
> > I'm working on bug :
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13528
> > <
> https://urldefense.com/v3/__https://bugzilla.yoctoproject.org/show_bug.cgi?id=13528__;!fqWJcnlTkjM!4DVD9lP2UdCF5UedI8J-XjhQQuyDhmAiLaOXk8OW5KMCFRzG2ASP_BdrxnvBnCnb0TyYNQ$
> >
> >
> >  I've a first patch proposal. Note that I didn't knew what to do with
> >  m4/gpgme.m4 the license header seems pretty weird to me...
> >
> > Regards,
> >
> > -- SMILE
> > <
> https://urldefense.com/v3/__http://www.smile.eu/__;!fqWJcnlTkjM!4DVD9lP2UdCF5UedI8J-XjhQQuyDhmAiLaOXk8OW5KMCFRzG2ASP_BdrxnvBnCnfbDCHYw$
> >
> >
> >  20 rue des Jardins 92600 Asnières-sur-Seine
> >
> >  *Yann CARDAILLAC* Ingénieur Systèmes Embarqués
> >
> > email yann.cardail...@smile.fr  url
> > http://www.smile.eu
> > <
> https://urldefense.com/v3/__http://www.smile.eu__;!fqWJcnlTkjM!4DVD9lP2UdCF5UedI8J-XjhQQuyDhmAiLaOXk8OW5KMCFRzG2ASP_BdrxnvBnCmV9R4jPA$
> >
> >
> >
> >
> > Twitter
> > <
> https://urldefense.com/v3/__https://twitter.com/GroupeSmile__;!fqWJcnlTkjM!4DVD9lP2UdCF5UedI8J-XjhQQuyDhmAiLaOXk8OW5KMCFRzG2ASP_BdrxnvBnCkq-mFzcw$
> >
> >  Facebook
> > <
> https://urldefense.com/v3/__https://www.facebook.com/smileopensource__;!fqWJcnlTkjM!4DVD9lP2UdCF5UedI8J-XjhQQuyDhmAiLaOXk8OW5KMCFRzG2ASP_BdrxnvBnCk8LxW08A$
> >
> >  LinkedIn
> > <
> https://urldefense.com/v3/__https://www.linkedin.com/company/smile__;!fqWJcnlTkjM!4DVD9lP2UdCF5UedI8J-XjhQQuyDhmAiLaOXk8OW5KMCFRzG2ASP_BdrxnvBnCk5-3y08w$
> >
> >  Github
> > <
> https://urldefense.com/v3/__https://github.com/Smile-SA__;!fqWJcnlTkjM!4DVD9lP2UdCF5UedI8J-XjhQQuyDhmAiLaOXk8OW5KMCFRzG2ASP_BdrxnvBnClEOxUzoA$
> >
> >
> >
> >
> >
> >
> > eco Pour la planète, n'imprimez ce mail que si c'est nécessaire
> >
> > -- You received this message because you are subscribed to the Google
> >  Groups "opkg-devel" group. To unsubscribe from this group and stop
> > receiving emails from it, send an email to
> > opkg-devel+unsubscr...@googlegroups.com
> > . To view this
> > discussion on the web visit
> >
> https://groups.google.com/d/msgid/opkg-devel/CAA984JWqcX5oDhumXYBom%2BZyxD%2Bbo7oGmTzLx_tXejvPaR1UKQ%40mail.gmail.com
> >
> > <
> https://urldefense.com/v3/__https://groups.google.com/d/msgid/opkg-devel/CAA984JWqcX5oDhumXYBom*2BZyxD*2Bbo7oGmTzLx_tXejvPaR1UKQ*40mail.gmail.com?utm_medium=email&utm_source=footer__;JSUl!fqWJcnlTkjM!4DVD9lP2UdCF5UedI8J-XjhQQuyDhmAiLaOXk8OW5KMCFRzG2ASP_BdrxnvBnCn7bez8Tg$
> >.
>
> --
> >
> Cheers,
>
> Alejandro
>


-- 
[image: SMILE] 

20 rue des Jardins
92600 Asnières-sur-Seine
*Yann CARDAILLAC*
Ingénieur Systèmes Embarqués

[image: email] yann.cardail...@smile.fr
[image: url] http://www.smile.eu

[image: Twitter]  [image: Facebook]
 [image: LinkedIn]
 [image: Github]



[image: eco] Pour la planète, n'imprimez ce mail que si c'est nécessaire
From ba9298741fe993e663c88e642a9636dd9fa17a88 Mon Sep 17 00:00:00 2001
From: Yann CARDAILLAC 
Date: Tue, 22 Oct 2019 16:49:42 +0200
Subject: [PATCH] add SPDX License identifier

Signed-off-by: Yann CARDAILLAC 
---
 intercept/depmod | 1 +
 intercept/ldconfig   | 1 +
 intercept/update-modules | 1 +
 libopkg/cksum_list.c | 2 ++
 libopkg/cksum_list.h | 2 ++
 libopkg/conffile.c   | 2 ++
 libopkg/conffile.h   | 2 ++
 libopkg/conffile_list.c  | 2 ++
 libopkg/conffile_list.h  | 2 ++
 libopkg/file_list.c  | 2 ++
 libopkg/file_list.h  | 2 ++
 libopkg/file_util.c  | 2 ++
 libopkg/file_util.h  | 2 ++
 libopkg/hash_table.c | 2 ++
 libopkg/hash_table.h | 2 ++
 libopkg/list.h   |

Re: [yocto] [EXTERNAL] Re: Issues adding bare meta toolchain to yocto build

2019-10-25 Thread Westermann, Oliver 
Thanks for all the help so far, I have a working recipe which installs the whole
toolchain to /usr/bin and uses that from another recipe :)

> On Thu, 2019-10-24 at 08:55 +, Richard Purdie wrote:
> You can probably do that by extending SYSROOT_DIRS in the recipe.

I'm still having issues here: I've tried to extend SYSROOOT_DIRS and even used a
path relative to the existing entrys (so I don't get caught by some hidden
extension mechanism), but my files still don't end up in the sysroot.
I've also tried both, SYSROOOT_DIRS and SYSROOT_DIRS_NATIVE, with the same 
result.

A (hopefully) last tip would be appreciated to make a nice recipe from a 
working one.

GCC_ARM_NONE_EXTRA_PATH="/${PN}"
SYSROOOT_DIRS += "${bindir}/../opt"

do_install() {
# old and working to install to /usr/bin/
# install -d ${D}${bindir}${GCC_ARM_NONE_EXTRA_PATH}
# cp -r ${S}/* ${D}${bindir}${GCC_ARM_NONE_EXTRA_PATH}

# new, but no files in the sysroots of recipes using the toolchain
install -d ${D}${bindir}/../opt${GCC_ARM_NONE_EXTRA_PATH}
cp -r ${S}/* ${D}${bindir}/../opt${GCC_ARM_NONE_EXTRA_PATH}
}

Best regards, Olli
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [opkg-devel] [PATCH][opkg] bug 13528 add SPDX id to opkg

2019-10-25 Thread Alejandro Del Castillo 
merged

thanks again for doing this, its been on the wish-list for a while!

--
Cheers,

Alejandro

On 10/25/19 2:50 AM, Yann CARDAILLAC wrote:
> Hi Alejandro,
> 
> Here's patch v2
> 
> Thanks for your sharpened eyes !
> 
> Regards,
> 
> On Thu, Oct 24, 2019 at 9:39 PM Alejandro Del Castillo 
> mailto:alejandro.delcasti...@ni.com>> wrote:
> 
> Hi Yann,
> 
> Thanks again for adding the headers. Your patch looks good, except for
> one line that has a duplicated header:
> 
> /core/26_prefer_arch_to_version.py
> index 0a0d66b..82934c1 100755
> --- a/tests/core/26_prefer_arch_to_version.py
> +++ b/tests/core/26_prefer_arch_to_version.py
> @@ -1,4 +1,5 @@
> -#! /usr/bin/env python3
> +#! /usr/bin/env python3# SPDX-License-Identifier: GPL-2.0-only
> +# SPDX-License-Identifier: GPL-2.0-only
>    #
> 
> could you send a v2? regarding m4 files, I looked around a bit and
> didn't find project adding SPDX identifiers to them
> 
> Cheers,
> 
> Alejandro
> 
> On 10/22/19 9:55 AM, Yann CARDAILLAC wrote:
>  > Hi,
>  >
>  > I'm working on bug :
>  > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13528
> 
> 
> 
>  >
> 
> 
>  >
>  >  I've a first patch proposal. Note that I didn't knew what to do with
>  >  m4/gpgme.m4 the license header seems pretty weird to me...
>  >
>  > Regards,
>  >
>  > -- SMILE
>  >
> 
> 
>  >
>  >  20 rue des Jardins 92600 Asnières-sur-Seine
>  >
>  >  *Yann CARDAILLAC* Ingénieur Systèmes Embarqués
>  >
>  > email yann.cardail...@smile.fr 
> > url
>  > http://www.smile.eu
> 
> 
> 
>  >
> 
> 
>  >
>  >
>  >
>  > Twitter
>  >
> 
> 
>  >  Facebook
>  >
> 
> 
>  >  LinkedIn
>  >
> 
> 
>  >  Github
>  >
> 
> 
>  >
>  >
>  >
>  >
>  >
>  > eco Pour la planète, n'imprimez ce mail que si c'est nécessaire
>  >
>  > -- You received this message because you are subscribed to the Google
>  >  Groups "opkg-devel" group. To unsubscribe from this group and stop
>  > receiving emails from it, send an email to
>  > opkg-devel+unsubscr...@googlegroups.com
> 
>  >  >. To view this
>  > discussion on the web visit
>  >
> 
> https://groups.google.com/d/msgid/opkg-devel/CAA984JWqcX5oDhumXYBom%2BZyxD%2Bbo7oGmTzLx_tXejvPaR1UKQ%40mail.gmail.com
> 
> 
>  >
>  >
> 
> .
> 
> --
>  >
> Cheers,
> 
> Alejandro
> 
> 
> 
> -- 
> SMILE 
> 
> 
> 20 rue des Jardins
> 92600 Asnières-sur-Seine
> 
>   
> *Yann CARDAILLAC*
> Ingénieur Systèmes Embarqués
> 
> email yann.cardail...@smile.fr

Re: [yocto] TFS Urls with Git in Recipes

2019-10-25 Thread Randy MacLeod 

Hello Christian,

Thanks for reporting the problem. Comments and questions below.

On 10/23/19 3:36 AM, Lohr, Christian [ext] wrote:

Hello,

I‘m using the following:

Yocto Release 2.4 (Rocko), and Bitbake 1.9.x


Can you check if the problem is still present on the master branch?



My problem is the following url (actually the “%20” is the problem in 
bitbake):


ssh://tfs-my-company.org:22/tfs/OWN_Projects/FooBar%20500/_git/DummyApplicationForYocto

I can do a “git clone ” without any problems. Now I wanted to 
create a Yocto recipe similar to this:


--

SUMMARY = "A demo application"

DESCRIPTION = "This application is just for demo purpose and should be 
seen as Hello World"


LICENSE = "CLOSED"

#LIC_FILES_CHKSUM = ""

PROJECT_URL = "tfs-my-company.org:22/tfs/OWN_Projects"

PROJECT_NAME = "FooBar%20500"


It's possible that:
PROJECT_NAME = "FooBar 500"
or
PROJECT_NAME = "FooBar\ 500"
would work. Have you tried that already? I haven't worked on the
bitbake fetcher code so I may be making naive suggestions.

Also, I expect that you are working around the issue by just
removing the space in the path, right?



SRC_URI = 
"git://${PROJECT_URL}/${PROJECT_NAME}/_git/DummyApplicationForYocto;protocol=ssh"


SRCREV = "${AUTOREV}"

PV = "1.0+git${SRCPV}"

DEPENDS = "qtbase"



The „%20“ sign will be replaced with a space “ “ in some cases:

When I try to run “bitbake dummyapp”, the following happens:

“FooBar%20500” will be transformed to “FooBar 500”



git -c core.fsyncobjectfiles=0 ls-remote 
ssh://tfs-my-company.org:22/tfs/OWN_Projects/FooBar 
500/_git/DummyApplicationForYocto  failed with exit code 128, output:


remote: Command git-upload-pack '/tfs/OWN_Projects/FooBar' is not in 
expected format.


fatal: Could not read from remote repository.

Is it possible to prevent this because if it would leave the “%20” the 
command would work.



The YP does have problems dealing with spaces in path names as you
have seen. I think this prevents the MacOS port for example.

Could you open a defect in the Yocto bugzilla?
  https://bugzilla.yoctoproject.org/
  https://wiki.yoctoproject.org/wiki/Bug_reporting_and_Information_levels

Ideally, it would be great if you could submit a patch but I understand
that you may not have the time, interest or the expertise to do so.
If you are not able to do that then the defect will be triaged during
the weekly review (next week's meeting is actually cancelled do to the
Embedded Linux Conference - Europe) and someone will work on the defect
based on it's importance and their interest and workload.

If you want a fix sooner than that, there are companies and consultants
listed on the yocto project homepage:
   https://www.yoctoproject.org/ecosystem/members/
   https://www.yoctoproject.org/community/consultants/

Thanks again for the report and
I'm sorry that I'm not able to be of more help immediately.

../Randy





Kind regards,

Christian Lohr





--
# Randy MacLeod
# Wind River Linux
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto