From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: julien.boibessot@armadeus.com
Cc: Romain Naour <romain.naour@smile.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] configs/armadeus_apf27: add hashes for Linux/U-Boot
Date: Sun, 5 May 2024 22:40:27 +0200 [thread overview]
Message-ID: <Zjfuu1QNP4nf1908@landeda> (raw)
In-Reply-To: <dc60d28929a40047698d678e756c2dd4@armadeus.com>
Julien, All,
On 2024-05-05 22:07 +0200, julien.boibessot@armadeus.com spake thusly:
> Le 2024-05-05 10:38, Yann E. MORIN a écrit :
> > Julien, All,
> > On 2024-05-03 17:48 +0200, Julien BOIBESSOT spake thusly:
> > > And enable BR2_DOWNLOAD_FORCE_CHECK_HASHES. As asked By Romain.
> > $ ./utils/docker-run make check-package
> > configs/armadeus_apf27_defconfig:0: lib_defconfig.ForceCheckHash
> > was expected to fail, did you fix the file and forget to update
> > .checkpackageignore?
[--SNIP--]
> Thanks for the fix ! I also saw the messages when running "make
> check-package" but didn't know if it was my job or not to fix
> .checkpackageignore file.
Entries in .checkpackageignore means that those files are exempleted
from the associated tests. Presumably, those files pre-existed
check-package, and thus we did not want to fail for those, so we
excluded them.
So, when a file is fixed, the corresponding exclusion must be removed.
In this case, you fixed the lib_defconfig.ForceCheckHash test, so now it
no longer fails, but it was expected to fail. so the correct solution is
indeed for you to state "yes, I fixed it, so it is no longer excluded!".
> Is there any documentation on what I was supposed to do ?
Err... Joker.
Thanks!
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-05-05 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 15:48 [Buildroot] [PATCH 1/3] configs/armadeus_apf27: add hashes for Linux/U-Boot Julien BOIBESSOT
2024-05-03 15:48 ` [Buildroot] [PATCH 2/3] configs/armadeus_apf28: activates BR2_DOWNLOAD_FORCE_CHECK_HASHES Julien BOIBESSOT
2024-05-03 15:48 ` [Buildroot] [PATCH 3/3] configs/armadeus_apf51: " Julien BOIBESSOT
2024-05-05 8:38 ` [Buildroot] [PATCH 1/3] configs/armadeus_apf27: add hashes for Linux/U-Boot Yann E. MORIN
2024-05-05 20:07 ` julien.boibessot
2024-05-05 20:40 ` Yann E. MORIN [this message]
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=Zjfuu1QNP4nf1908@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=julien.boibessot@armadeus.com \
--cc=romain.naour@smile.fr \
/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