[meta-swupdate][Question] Missing dependencys do_package_qa

500 views
Skip to first unread message

Sebastian

unread,
Mar 22, 2017, 11:01:39 AM3/22/17
to swupdate
Hi Together

If I'm building sw-update with the following command (yocto/poky morty branch):

# bitbake swupdate

I`m getting always the following warings:

```
WARNING: swupdate-2017.01-r0 do_package_qa: QA Issue: swupdate rdepends on libcurl, but it isn't a build dependency, missing curl in DEPENDS or PACKAGECONFIG? [build-deps]
WARNING: swupdate-2017.01-r0 do_package_qa: QA Issue: swupdate rdepends on zeromq, but it isn't a build dependency, missing zeromq in DEPENDS or PACKAGECONFIG? [build-deps]
WARNING: swupdate-2017.01-r0 do_package_qa: QA Issue: swupdate rdepends on json-c, but it isn't a build dependency, missing json-c in DEPENDS or PACKAGECONFIG? [build-deps]
```
can someone give me a hint how can avoid this warnings?
Googleing and counsulting the yocto docs about do_package_qa does not helped yet :(

Thanks
Sebastian

--- here is my current swupdate build config (make menuconfig) without comments for better reading ---

CONFIG_HAVE_DOT_CONFIG=y


CONFIG_SCRIPTS=y

# CONFIG_HW_COMPATIBILITY is not set

CONFIG_SW_VERSIONS_FILE="/etc/sw-versions"

CONFIG_MTD=y

CONFIG_LUA=y

CONFIG_LUAPKG="lua"


CONFIG_CROSS_COMPILE=""

CONFIG_SYSROOT=""

CONFIG_EXTRA_CFLAGS=""

CONFIG_EXTRA_LDFLAGS=""

CONFIG_EXTRA_LDLIBS=""


CONFIG_DOWNLOAD=y

CONFIG_HASH_VERIFY=y

CONFIG_SIGNED_IMAGES=y

CONFIG_SURICATTA=y

CONFIG_SURICATTA_SSL=y

CONFIG_SURICATTA_STATE_CHOICE_UBOOT=y

CONFIG_SURICATTA_STATE_UBOOT="ustate"

CONFIG_SURICATTA_HAWKBIT=y

CONFIG_WEBSERVER=y


CONFIG_MONGOOSE=y


CONFIG_MONGOOSELUA=y

CONFIG_MONGOOSESSL=y


CONFIG_GUNZIP=y


CONFIG_LIBCONFIG=y

CONFIG_LIBCONFIGROOT=""

CONFIG_JSON=y


CONFIG_CFI=y

CONFIG_RAW=y

CONFIG_LUASCRIPTHANDLER=y

CONFIG_SHELLSCRIPTHANDLER=y

CONFIG_HANDLER_IN_LUA=y

CONFIG_REMOTE_HANDLER=y

CONFIG_UBOOT=y

CONFIG_UBOOT_FWENV="/etc/fw_env.config"

---


Stefano Babic

unread,
Mar 26, 2017, 9:25:45 AM3/26/17
to Sebastian, swupdate
Hi Sebastian,

On 22/03/2017 16:01, Sebastian wrote:
> Hi Together
>
> If I'm building sw-update with the following command (yocto/poky morty
> branch):
>
> # bitbake swupdate
>
> I`m getting always the following warings:
>
> ```
> WARNING: swupdate-2017.01-r0 do_package_qa: QA Issue: swupdate rdepends
> on libcurl, but it isn't a build dependency, missing curl in DEPENDS or
> PACKAGECONFIG? [build-deps]
> WARNING: swupdate-2017.01-r0 do_package_qa: QA Issue: swupdate rdepends
> on zeromq, but it isn't a build dependency, missing zeromq in DEPENDS or
> PACKAGECONFIG? [build-deps]
> WARNING: swupdate-2017.01-r0 do_package_qa: QA Issue: swupdate rdepends
> on json-c, but it isn't a build dependency, missing json-c in DEPENDS or
> PACKAGECONFIG? [build-deps]
> ```

Tested on -master for all layers, I cannot see the issue (of course,
CONFIG_DOWNLOAD is set). It disappeared or I cannot reproduce myself.

> can someone give me a hint how can avoid this warnings?
> Googleing and counsulting the yocto docs about do_package_qa does not
> helped yet :(

The depend's list is generated at runtime for SWUpdate. This is surely
an exception in oe-world, where dependencies are set via the DEPENDS
variable. Anyway, it looks like to work and I cannot currently see the
issue you are seeing.

Best regards,
Stefano Babic


--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sba...@denx.de
=====================================================================

Sebastian

unread,
Mar 28, 2017, 4:43:14 AM3/28/17
to swupdate, office....@gmail.com, sba...@denx.de
Hi Stefano,

thanks for your reply.

today I've found out that the error comes form my local system "bitbake -c cleanall swupdate" works not every time correctly, the qa warings are an result of that.

To avoid this problem it was necessary to remove the whole tmp directory manually. Now it works fine.

thanks again for your reply and have a nice day!
Sebastian
Reply all
Reply to author
Forward
0 new messages