Re: [oe] S variable for svn fetcher Was: State of OE world - 2020-02-18
On 2/20/20 9:34 AM, Martin Jansa wrote: On Thu, Feb 20, 2020 at 05:23:12PM +0100, Martin Jansa wrote: On Thu, Feb 20, 2020 at 06:11:59PM +0200, Adrian Bunk wrote: On Thu, Feb 20, 2020 at 04:37:58PM +0100, Martin Jansa wrote: On Thu, Feb 20, 2020 at 05:16:20PM +0200, Adrian Bunk wrote: On Thu, Feb 20, 2020 at 03:48:48PM +0100, Martin Jansa wrote: ... Any idea why these aren't shown in our build? ... What is your mirror configuration? Default configuration downloads the tarball from [1]. Maybe I'm missing your point, but these aren't fetch issues. ... MIRRORS = "" (and deleting the downloaded tar) is what I needed for getting a build failure. OK, I see now, sorry. That explains why it's not shown in khem's builds and might be broken well before thud already, the tarball created here today: $ tar xvf ../downloads/gpio_svn.openmoko.org_.trunk.src.target_4949_.tar.gz gpio/ gpio/trunk/ gpio/trunk/doc/ gpio/trunk/doc/hardware/ gpio/trunk/doc/hardware/GTA01Bv3/ gpio/trunk/doc/hardware/GTA01Bv3/gpio.txt gpio/trunk/doc/hardware/GTA01Bv3/pmu-voltage.txt ... while the corresponding tarball on mirror: http://sources.openembedded.org/gpio_svn.openmoko.org_.trunk.src.target_4949_.tar.gz $ tar xvf gpio_svn.openmoko.org_.trunk.src.target_4949_.tar.gz gpio/ gpio/gpio-s3c6410.c gpio/Makefile gpio/gpio.c gpio/gpio-glamo.c gpio/README Will check when it got broken before thud. It's still reproducible in pyro, so probably not caused by changes in OE. There is one more recipe using svn in meta-multimedia which works fine: meta-multimedia/recipes-dvb/oscam/oscam_svn.bb:SRC_URI = "svn://www.streamboard.tv/svn/oscam;module=trunk;protocol=http \ The rest are all from svn.openmoko.org: meta-oe/recipes-support/samsung-soc-utils/s3c24xx-gpio_svn.bb:SRC_URI = "svn://svn.openmoko.org/trunk/src/target;module=gpio;protocol=http" meta-oe/recipes-support/samsung-soc-utils/s3c64xx-gpio_svn.bb:SRC_URI = "svn://svn.openmoko.org/trunk/src/target;module=gpio;protocol=http" meta-oe/recipes-support/samsung-soc-utils/sjf2410-linux-native_svn.bb:SRC_URI = "svn://svn.openmoko.org/trunk/src/host/;module=sjf2410-linux;protocol=http \ meta-oe/recipes-support/usbpath/usbpath_svn.bb:SRC_URI = "svn://svn.openmoko.org/trunk/src/host;module=usbpath;protocol=http \ meta-oe/recipes-support/wmiconfig/wmiconfig_svn.bb:SRC_URI = "svn://svn.openmoko.org/trunk/src/target;module=AR6kSDK.build_sw.18;protocol=http \ And now this leads to do_fetch running: svn --non-interactive --trust-server-cert co --no-auth-cache --ignore-externals -r 4949 http://svn.openmoko.org/trunk/src/target/gpio@4949 gpio as before, but now it redirects to github: Redirecting to URL 'https://github.com/openmoko/openmoko-svn': Agpio/branches Agpio/branches/oe Agpio/branches/oe/pre-20070305 Agpio/branches/oe/pre-20070305/README Agpio/branches/oe/pre-20070305/classes Agpio/branches/oe/pre-20070305/classes/autotools.bbclass Agpio/branches/oe/pre-20070305/classes/base.bbclass Agpio/branches/oe/pre-20070305/classes/openmoko-base.bbclass Agpio/branches/oe/pre-20070305/classes/openmoko-panel-plugin.bbclass .. and the svn bridge to github probably doesn't work exactly the same as the native svn repo used to work, but I don't see it explicitly mentioned in: https://help.github.com/en/github/importing-your-projects-to-github/support-for-subversion-clients So to resolve this quickly I'm going to send SRC_URI updates for these recipes to just use git fetcher from: https://github.com/openmoko/openmoko-svn directly. I don't think anyone is using these nowadays, so it's also fine with me to just delete them all, which I'll do in separate follow-up commit in case someone tries to resurrect them later in own layer. I think plan looks good. Lets fix the SRC_URI and then delete them -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] S variable for svn fetcher Was: State of OE world - 2020-02-18
On Thu, Feb 20, 2020 at 05:23:12PM +0100, Martin Jansa wrote: > On Thu, Feb 20, 2020 at 06:11:59PM +0200, Adrian Bunk wrote: > > On Thu, Feb 20, 2020 at 04:37:58PM +0100, Martin Jansa wrote: > > > On Thu, Feb 20, 2020 at 05:16:20PM +0200, Adrian Bunk wrote: > > > > On Thu, Feb 20, 2020 at 03:48:48PM +0100, Martin Jansa wrote: > > > > >... > > > > > Any idea why these aren't shown in our build? > > > > >... > > > > > > > > What is your mirror configuration? > > > > > > > > Default configuration downloads the tarball from [1]. > > > > > > Maybe I'm missing your point, but these aren't fetch issues. > > >... > > > > MIRRORS = "" (and deleting the downloaded tar) is what I needed for > > getting a build failure. > > OK, I see now, sorry. > > That explains why it's not shown in khem's builds and might be broken > well before thud already, the tarball created here today: > > $ tar xvf ../downloads/gpio_svn.openmoko.org_.trunk.src.target_4949_.tar.gz > gpio/ > gpio/trunk/ > gpio/trunk/doc/ > gpio/trunk/doc/hardware/ > gpio/trunk/doc/hardware/GTA01Bv3/ > gpio/trunk/doc/hardware/GTA01Bv3/gpio.txt > gpio/trunk/doc/hardware/GTA01Bv3/pmu-voltage.txt > ... > > while the corresponding tarball on mirror: > http://sources.openembedded.org/gpio_svn.openmoko.org_.trunk.src.target_4949_.tar.gz > $ tar xvf gpio_svn.openmoko.org_.trunk.src.target_4949_.tar.gz > gpio/ > gpio/gpio-s3c6410.c > gpio/Makefile > gpio/gpio.c > gpio/gpio-glamo.c > gpio/README > > Will check when it got broken before thud. It's still reproducible in pyro, so probably not caused by changes in OE. There is one more recipe using svn in meta-multimedia which works fine: meta-multimedia/recipes-dvb/oscam/oscam_svn.bb:SRC_URI = "svn://www.streamboard.tv/svn/oscam;module=trunk;protocol=http \ The rest are all from svn.openmoko.org: meta-oe/recipes-support/samsung-soc-utils/s3c24xx-gpio_svn.bb:SRC_URI = "svn://svn.openmoko.org/trunk/src/target;module=gpio;protocol=http" meta-oe/recipes-support/samsung-soc-utils/s3c64xx-gpio_svn.bb:SRC_URI = "svn://svn.openmoko.org/trunk/src/target;module=gpio;protocol=http" meta-oe/recipes-support/samsung-soc-utils/sjf2410-linux-native_svn.bb:SRC_URI = "svn://svn.openmoko.org/trunk/src/host/;module=sjf2410-linux;protocol=http \ meta-oe/recipes-support/usbpath/usbpath_svn.bb:SRC_URI = "svn://svn.openmoko.org/trunk/src/host;module=usbpath;protocol=http \ meta-oe/recipes-support/wmiconfig/wmiconfig_svn.bb:SRC_URI = "svn://svn.openmoko.org/trunk/src/target;module=AR6kSDK.build_sw.18;protocol=http \ And now this leads to do_fetch running: svn --non-interactive --trust-server-cert co --no-auth-cache --ignore-externals -r 4949 http://svn.openmoko.org/trunk/src/target/gpio@4949 gpio as before, but now it redirects to github: Redirecting to URL 'https://github.com/openmoko/openmoko-svn': Agpio/branches Agpio/branches/oe Agpio/branches/oe/pre-20070305 Agpio/branches/oe/pre-20070305/README Agpio/branches/oe/pre-20070305/classes Agpio/branches/oe/pre-20070305/classes/autotools.bbclass Agpio/branches/oe/pre-20070305/classes/base.bbclass Agpio/branches/oe/pre-20070305/classes/openmoko-base.bbclass Agpio/branches/oe/pre-20070305/classes/openmoko-panel-plugin.bbclass .. and the svn bridge to github probably doesn't work exactly the same as the native svn repo used to work, but I don't see it explicitly mentioned in: https://help.github.com/en/github/importing-your-projects-to-github/support-for-subversion-clients So to resolve this quickly I'm going to send SRC_URI updates for these recipes to just use git fetcher from: https://github.com/openmoko/openmoko-svn directly. I don't think anyone is using these nowadays, so it's also fine with me to just delete them all, which I'll do in separate follow-up commit in case someone tries to resurrect them later in own layer. signature.asc Description: PGP signature -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] S variable for svn fetcher Was: State of OE world - 2020-02-18
On Thu, Feb 20, 2020 at 7:38 AM Martin Jansa wrote: > > On Thu, Feb 20, 2020 at 05:16:20PM +0200, Adrian Bunk wrote: > > On Thu, Feb 20, 2020 at 03:48:48PM +0100, Martin Jansa wrote: > > >... > > > Any idea why these aren't shown in our build? > > >... > > > > What is your mirror configuration? > > > > Default configuration downloads the tarball from [1]. > > Maybe I'm missing your point, but these aren't fetch issues. > > Even when bitbake fetches the tarball (with the svn repo), svn fetcher > will still do the actual checkout to WORKDIR, so it will fail the same > when fetching from upstream repo with svn or when using tarball. > they could have been fetched long time ago, perhaps it changed in this area after that when fetching fresh repos, just guessing > Cheers, -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] S variable for svn fetcher Was: State of OE world - 2020-02-18
On Thu, Feb 20, 2020 at 06:11:59PM +0200, Adrian Bunk wrote: > On Thu, Feb 20, 2020 at 04:37:58PM +0100, Martin Jansa wrote: > > On Thu, Feb 20, 2020 at 05:16:20PM +0200, Adrian Bunk wrote: > > > On Thu, Feb 20, 2020 at 03:48:48PM +0100, Martin Jansa wrote: > > > >... > > > > Any idea why these aren't shown in our build? > > > >... > > > > > > What is your mirror configuration? > > > > > > Default configuration downloads the tarball from [1]. > > > > Maybe I'm missing your point, but these aren't fetch issues. > >... > > MIRRORS = "" (and deleting the downloaded tar) is what I needed for > getting a build failure. OK, I see now, sorry. That explains why it's not shown in khem's builds and might be broken well before thud already, the tarball created here today: $ tar xvf ../downloads/gpio_svn.openmoko.org_.trunk.src.target_4949_.tar.gz gpio/ gpio/trunk/ gpio/trunk/doc/ gpio/trunk/doc/hardware/ gpio/trunk/doc/hardware/GTA01Bv3/ gpio/trunk/doc/hardware/GTA01Bv3/gpio.txt gpio/trunk/doc/hardware/GTA01Bv3/pmu-voltage.txt ... while the corresponding tarball on mirror: http://sources.openembedded.org/gpio_svn.openmoko.org_.trunk.src.target_4949_.tar.gz $ tar xvf gpio_svn.openmoko.org_.trunk.src.target_4949_.tar.gz gpio/ gpio/gpio-s3c6410.c gpio/Makefile gpio/gpio.c gpio/gpio-glamo.c gpio/README Will check when it got broken before thud. signature.asc Description: PGP signature -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] S variable for svn fetcher Was: State of OE world - 2020-02-18
On Thu, Feb 20, 2020 at 04:37:58PM +0100, Martin Jansa wrote: > On Thu, Feb 20, 2020 at 05:16:20PM +0200, Adrian Bunk wrote: > > On Thu, Feb 20, 2020 at 03:48:48PM +0100, Martin Jansa wrote: > > >... > > > Any idea why these aren't shown in our build? > > >... > > > > What is your mirror configuration? > > > > Default configuration downloads the tarball from [1]. > > Maybe I'm missing your point, but these aren't fetch issues. >... MIRRORS = "" (and deleting the downloaded tar) is what I needed for getting a build failure. > Cheers, cu Adrian -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] S variable for svn fetcher Was: State of OE world - 2020-02-18
On Thu, Feb 20, 2020 at 6:48 AM Martin Jansa wrote:
>
> On Wed, Feb 19, 2020 at 09:29:58AM -0800, Khem Raj wrote:
> > http://www.openembedded.org/wiki/Bitbake_World_Status
> >
> > == Failed tasks /media/ra_build_share/buildlogs/oe/world/dunfell/2020-02-18
> > ==
> >
> > INFO: jenkins-job.sh-1.8.46 Complete log available at
> > /media/ra_build_share/buildlogs/oe/world/dunfell//media/ra_build_share/buildlogs/oe/world/dunfell/log.report.20200219_150007.log
> >
> > === common (0) ===
> >
> > === common-x86 (0) ===
> >
> > === qemuarm (0) ===
> >
> > === qemuarm64 (0) ===
> >
> > === qemux86 (0) ===
> >
> > === qemux86_64 (0) ===
>
> Looks great! Thanks
>
> I was running some world builds recently as well and was surprised that
> there are a few failing recipes in meta-oe:
> s3c24xx-gpio
> s3c64xx-gpio
> wmiconfig
> usbpath
> which are all using svn fetcher.
>
> Any idea why these aren't shown in our build? I was able to reproduce
> this on thud as well as latest master build:
>
perhaps it might be due to the fact that yoe distro uses yocto and oe
source mirrors for tarballs
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/usbpath/usbpath_svn.bb:do_patch
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c64xx-gpio_svn.bb:do_compile
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c24xx-gpio_svn.bb:do_compile
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c64xx-gpio_svn.bb:do_populate_lic
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c24xx-gpio_svn.bb:do_populate_lic
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/wmiconfig/wmiconfig_svn.bb:do_patch
>
> they have all the same root cause and that is that the
> S variable points to directory where the sources used to be, but now
> they are checked out somewhere else, e.g. s3c24xx-gpio:
>
> LIC_FILES_CHKSUM =
> "file://gpio.c;endline=12;md5=cfb91c686857b2e60852b4925d90a3e1"
>
> SRC_URI = "svn://svn.openmoko.org/trunk/src/target;module=gpio;protocol=http"
>
> S = "${WORKDIR}/gpio"
>
> And now S looks like this:
> $ ls
> /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/s3c24xx-gpio/1.0+svnr4949-r2/gpio/
> branches trunk
>
> While before I believe it was checking out just this directory (as
> ${WORKDIR}/gpio):
> $ ls
> /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/s3c24xx-gpio/1.0+svnr4949-r2/gpio/trunk/src/target/gpio/
> gpio.c gpio-glamo.c gpio-s3c6410.c Makefile README
>
> Anyone still actively using svn fetcher for something?
>
> I'll check with even older bitbake to see when it changed, but it's
> still surprising that you wouldn't be seeing it with latest bitbake
> in world builds.
>
> Cheers,
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] S variable for svn fetcher Was: State of OE world - 2020-02-18
On Thu, Feb 20, 2020 at 05:16:20PM +0200, Adrian Bunk wrote: > On Thu, Feb 20, 2020 at 03:48:48PM +0100, Martin Jansa wrote: > >... > > Any idea why these aren't shown in our build? > >... > > What is your mirror configuration? > > Default configuration downloads the tarball from [1]. Maybe I'm missing your point, but these aren't fetch issues. Even when bitbake fetches the tarball (with the svn repo), svn fetcher will still do the actual checkout to WORKDIR, so it will fail the same when fetching from upstream repo with svn or when using tarball. Cheers, signature.asc Description: PGP signature -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] S variable for svn fetcher Was: State of OE world - 2020-02-18
On Thu, Feb 20, 2020 at 03:48:48PM +0100, Martin Jansa wrote: >... > Any idea why these aren't shown in our build? >... What is your mirror configuration? Default configuration downloads the tarball from [1]. > Cheers, cu Adrian [1] http://downloads.yoctoproject.org/mirror/sources/ -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] S variable for svn fetcher Was: State of OE world - 2020-02-18
On Thu, Feb 20, 2020 at 03:48:48PM +0100, Martin Jansa wrote:
> On Wed, Feb 19, 2020 at 09:29:58AM -0800, Khem Raj wrote:
> > http://www.openembedded.org/wiki/Bitbake_World_Status
> >
> > == Failed tasks /media/ra_build_share/buildlogs/oe/world/dunfell/2020-02-18
> > ==
> >
> > INFO: jenkins-job.sh-1.8.46 Complete log available at
> > /media/ra_build_share/buildlogs/oe/world/dunfell//media/ra_build_share/buildlogs/oe/world/dunfell/log.report.20200219_150007.log
> >
> > === common (0) ===
> >
> > === common-x86 (0) ===
> >
> > === qemuarm (0) ===
> >
> > === qemuarm64 (0) ===
> >
> > === qemux86 (0) ===
> >
> > === qemux86_64 (0) ===
>
> Looks great! Thanks
>
> I was running some world builds recently as well and was surprised that
> there are a few failing recipes in meta-oe:
> s3c24xx-gpio
> s3c64xx-gpio
> wmiconfig
> usbpath
> which are all using svn fetcher.
>
> Any idea why these aren't shown in our build? I was able to reproduce
> this on thud as well as latest master build:
>
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/usbpath/usbpath_svn.bb:do_patch
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c64xx-gpio_svn.bb:do_compile
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c24xx-gpio_svn.bb:do_compile
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c64xx-gpio_svn.bb:do_populate_lic
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c24xx-gpio_svn.bb:do_populate_lic
>
> /OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/wmiconfig/wmiconfig_svn.bb:do_patch
>
> they have all the same root cause and that is that the
> S variable points to directory where the sources used to be, but now
> they are checked out somewhere else, e.g. s3c24xx-gpio:
>
> LIC_FILES_CHKSUM =
> "file://gpio.c;endline=12;md5=cfb91c686857b2e60852b4925d90a3e1"
>
> SRC_URI = "svn://svn.openmoko.org/trunk/src/target;module=gpio;protocol=http"
>
> S = "${WORKDIR}/gpio"
>
> And now S looks like this:
> $ ls
> /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/s3c24xx-gpio/1.0+svnr4949-r2/gpio/
> branches trunk
>
> While before I believe it was checking out just this directory (as
> ${WORKDIR}/gpio):
> $ ls
> /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/s3c24xx-gpio/1.0+svnr4949-r2/gpio/trunk/src/target/gpio/
> gpio.c gpio-glamo.c gpio-s3c6410.c Makefile README
>
> Anyone still actively using svn fetcher for something?
>
> I'll check with even older bitbake to see when it changed, but it's
> still surprising that you wouldn't be seeing it with latest bitbake
> in world builds.
Chiming in as this caught my eye. I've run in to this perhaps with
'warrior' as well recently for a customer. I assumed it was just that
it had been so long since I had used SVN I had just mis-remembered how
S needed to be set. I also as a tangent noticed that AUTOREV for svn
seems broken as it doesn't ensure we have subversion-native in the
sysroot ('svn command not found' is the relevant part of the failure).
--
Tom
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] S variable for svn fetcher Was: State of OE world - 2020-02-18
On Wed, Feb 19, 2020 at 09:29:58AM -0800, Khem Raj wrote:
> http://www.openembedded.org/wiki/Bitbake_World_Status
>
> == Failed tasks /media/ra_build_share/buildlogs/oe/world/dunfell/2020-02-18 ==
>
> INFO: jenkins-job.sh-1.8.46 Complete log available at
> /media/ra_build_share/buildlogs/oe/world/dunfell//media/ra_build_share/buildlogs/oe/world/dunfell/log.report.20200219_150007.log
>
> === common (0) ===
>
> === common-x86 (0) ===
>
> === qemuarm (0) ===
>
> === qemuarm64 (0) ===
>
> === qemux86 (0) ===
>
> === qemux86_64 (0) ===
Looks great! Thanks
I was running some world builds recently as well and was surprised that
there are a few failing recipes in meta-oe:
s3c24xx-gpio
s3c64xx-gpio
wmiconfig
usbpath
which are all using svn fetcher.
Any idea why these aren't shown in our build? I was able to reproduce
this on thud as well as latest master build:
/OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/usbpath/usbpath_svn.bb:do_patch
/OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c64xx-gpio_svn.bb:do_compile
/OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c24xx-gpio_svn.bb:do_compile
/OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c64xx-gpio_svn.bb:do_populate_lic
/OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/samsung-soc-utils/s3c24xx-gpio_svn.bb:do_populate_lic
/OE/build/oe-core/meta-openembedded/meta-oe/recipes-support/wmiconfig/wmiconfig_svn.bb:do_patch
they have all the same root cause and that is that the
S variable points to directory where the sources used to be, but now
they are checked out somewhere else, e.g. s3c24xx-gpio:
LIC_FILES_CHKSUM =
"file://gpio.c;endline=12;md5=cfb91c686857b2e60852b4925d90a3e1"
SRC_URI = "svn://svn.openmoko.org/trunk/src/target;module=gpio;protocol=http"
S = "${WORKDIR}/gpio"
And now S looks like this:
$ ls
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/s3c24xx-gpio/1.0+svnr4949-r2/gpio/
branches trunk
While before I believe it was checking out just this directory (as
${WORKDIR}/gpio):
$ ls
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/s3c24xx-gpio/1.0+svnr4949-r2/gpio/trunk/src/target/gpio/
gpio.c gpio-glamo.c gpio-s3c6410.c Makefile README
Anyone still actively using svn fetcher for something?
I'll check with even older bitbake to see when it changed, but it's
still surprising that you wouldn't be seeing it with latest bitbake
in world builds.
Cheers,
signature.asc
Description: PGP signature
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
