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':
A gpio/branches
A gpio/branches/oe
A gpio/branches/oe/pre-20070305
A gpio/branches/oe/pre-20070305/README
A gpio/branches/oe/pre-20070305/classes
A gpio/branches/oe/pre-20070305/classes/autotools.bbclass
A gpio/branches/oe/pre-20070305/classes/base.bbclass
A gpio/branches/oe/pre-20070305/classes/openmoko-base.bbclass
A gpio/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
