Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v3 6/6] package/mender: bump version to 3.5.1
Date: Mon, 22 Jul 2024 14:55:49 +0200	[thread overview]
Message-ID: <20240722145549.20a7efcd@windsurf> (raw)
In-Reply-To: <20231219172446.498409-6-adam.duskett@amarulasolutions.com>

Hello Adam,

On Tue, 19 Dec 2023 10:24:46 -0700
Adam Duskett <adam.duskett@amarulasolutions.com> wrote:

> The artifact_info file is no longer supported. Instead, mender now expects a
> bootstrap.mender artifact created by mender-artifact in either /data/ or
> /var/lib/mender. See the following for more information:
> https://northerntech.atlassian.net/browse/MEN-2585
> https://northerntech.atlassian.net/browse/MEN-2583

[...]

I don't think it's related to this version bump, but our Mender test
case in our CI is failing:

  https://gitlab.com/buildroot.org/buildroot/-/jobs/7391793034

I am not 100% sure what the error exactly is. The end of the log looks
like this:

mdb.c: In function 'mdb_cursor_put':
mdb.c:6535:44: warning: this statement may fall through [-Wimplicit-fallthrough=]
 6535 |                                         if (SIZELEFT(fp) < offset) {
      |                                            ^
mdb.c:6540:33: note: here
 6540 |                                 case MDB_CURRENT:
      |                                 ^~~~
# github.com/mendersoftware/openssl
vendor/github.com/mendersoftware/openssl/engine.go:29:5: could not determine kind of name for C.ENGINE
vendor/github.com/mendersoftware/openssl/engine.go:36:6: could not determine kind of name for C.ENGINE_by_id
vendor/github.com/mendersoftware/openssl/engine.go:46:3: could not determine kind of name for C.ENGINE_finish
vendor/github.com/mendersoftware/openssl/engine.go:42:3: could not determine kind of name for C.ENGINE_free
vendor/github.com/mendersoftware/openssl/engine.go:41:5: could not determine kind of name for C.ENGINE_init
vendor/github.com/mendersoftware/openssl/engine.go:34:8: could not determine kind of name for C.free
make[1]: *** [package/pkg-generic.mk:289: /builds/buildroot.org/buildroot/test-output/TestMender/build/mender-3.4.0/.stamp_built] Error 1

The OpenSSL engine stuff makes me think perhaps this package needs to
select BR2_PACKAGE_LIBOPENSSL_ENGINES, but this isn't spotted directly
as an error.

Could you perhaps have a look?

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-07-22 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 17:24 [Buildroot] [PATCH v3 1/6] configs/mender_x86_64_efi_defconfig: Update kernel to latest LTS version Adam Duskett
2023-12-19 17:24 ` [Buildroot] [PATCH v3 2/6] package/mender-grubenv: Fix per-package building Adam Duskett
2023-12-19 17:24 ` [Buildroot] [PATCH v3 3/6] package/mender-grubenv: bump version to 64e32b01d1bf54784d2a290ad0469c583e843864 Adam Duskett
2023-12-19 17:24 ` [Buildroot] [PATCH v3 4/6] package/mender-artifact: bump version to 3.10.2 Adam Duskett
2023-12-19 17:24 ` [Buildroot] [PATCH v3 5/6] package/mender-connect: bump version to 2.1.1 Adam Duskett
2023-12-19 17:24 ` [Buildroot] [PATCH v3 6/6] package/mender: bump version to 3.5.1 Adam Duskett
2024-07-22 12:55   ` Thomas Petazzoni via buildroot [this message]
2023-12-24 22:08 ` [Buildroot] [PATCH v3 1/6] configs/mender_x86_64_efi_defconfig: Update kernel to latest LTS version Adam Duskett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240722145549.20a7efcd@windsurf \
    --to=buildroot@buildroot.org \
    --cc=adam.duskett@amarulasolutions.com \
    --cc=angelo.compagnucci@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox