morty build fails firmware_imx fetcher

* morty build fails firmware_imx fetcher
@ 2017-03-24 21:22 Eckhardt, Andrew           UTAS
  2017-03-24 23:09 ` Max Krummenacher
  0 siblings, 1 reply; 4+ messages in thread
From: Eckhardt, Andrew           UTAS @ 2017-03-24 21:22 UTC (permalink / raw)
  To: meta-freescale

[-- Attachment #1: Type: text/plain, Size: 2849 bytes --]

Hi all,

Because our proxy server requires http format. I have changed SRC_URI in meta-freescale/recipes-bsp/firmware-imx/firmware-imx.inc

From:
           git://git.freescale.com/imx/imx-firmware.git;branch=${SRCBRANCH};destsuffix=${S}/git "

To:
          http://git.freescale.com/git/cgit.cgi/imx/imx-firmware.git;branch=${SRCBRANCH};destsuffix=${S}/git "

Now bitbake actually gets an html file which start like this...

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns='http://www.w3.org/1999/xhtml' xml:lang='en' lang='en'>
<head>
<title>imx-firmware.git - i.MX Firmware
</title>
<meta name='generator' content='cgit v0.9.0.2-39-g756e'/>
<meta name='robots' content='index, nofollow'/>
<link rel='stylesheet' type='text/css' href='/cgit.css'/>
<link rel='alternate' title='Atom feed' href='http://git.freescale.com/git/cgit.cgi/imx/imx-firmware.git/atom/?h=master' type='application/atom+xml'/>
</head>
<body>
Ubuntu1A

...and so has checksum failure.

WARNING: firmware-imx-1_5.4-r0 do_fetch: Checksum mismatch for local file downloads/imx-firmware.git
Cleaning and trying again.
WARNING: firmware-imx-1_5.4-r0 do_fetch: Renaming /downloads/imx-firmware.git to /downloads/imx-firmware.git_bad-checksum_6aa357175f29cf32710c9677bc7cdaa8
...
imx-firmware.git' has md5 checksum 6aa357175f29cf32710c9677bc7cdaa8 when dae846ca2fc4504067f725f501491adf was expected
imx-firmware.git' has sha256 checksum 44c0250e54e11a4b72741226da43d184872f5f97d08edb6645f26c8c0422a5dd when c5bd4bff48cce9715a5d6d2c190ff3cd2262c7196f7facb9b0eda231c92cc223 was expected

... and fetcher suggests that...

If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe:
SRC_URI[md5sum] = "6aa357175f29cf32710c9677bc7cdaa8"
SRC_URI[sha256sum] = "44c0250e54e11a4b72741226da43d184872f5f97d08edb6645f26c8c0422a5dd"

...if I make the change to SRC_URI[md5sum] then...

File: ' /downloads/firmware-imx-5.4.bin' has md5 checksum dae846ca2fc4504067f725f501491adf when 6aa357175f29cf32710c9677bc7cdaa8 was expected
File: ' /downloads/firmware-imx-5.4.bin' has sha256 checksum c5bd4bff48cce9715a5d6d2c190ff3cd2262c7196f7facb9b0eda231c92cc223 when 44c0250e54e11a4b72741226da43d184872f5f97d08edb6645f26c8c0422a5dd was expected

If this change is expected (e.g. you have upgraded to a new version without updating the checksums) then you can use these lines within the recipe:
SRC_URI[md5sum] = "dae846ca2fc4504067f725f501491adf"
SRC_URI[sha256sum] = "c5bd4bff48cce9715a5d6d2c190ff3cd2262c7196f7facb9b0eda231c92cc223"

...  so now the incoming file matched the original SRC_URI[md5sum] but not the new one !!!

Very strange behavior.

Andrew Eckhardt

[-- Attachment #2: Type: text/html, Size: 7151 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread