Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart <christian@paral.in>
Cc: Anisse Astier <anisse@astier.eu>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	Christian Stewart via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/gocryptfs: fix build against riscv
Date: Sat, 23 Jul 2022 22:22:37 +0200	[thread overview]
Message-ID: <20220723222237.7989b5c6@windsurf> (raw)
In-Reply-To: <CA+h8R2og5UzGbLs-NHFKdLYyEus0v20EqgdZMtHnJDQa9dY4Gg@mail.gmail.com>

On Sat, 23 Jul 2022 12:44:01 -0700
Christian Stewart <christian@paral.in> wrote:

> > You're patching go.mod/go.sum, and this patching happens after we have
> > done the vendoring of the dependencies in the download step (an issue
> > you have reported already), so how can this patch work? I am missing
> > something here?
> 
> The patch includes the changes to vendor/

Aaah, indeed, I missed that, but re-reading the patch it's now obvious.

> Go uses minimum version selection and indirect dependencies. If you change
> the version of a dependency, it will also update any dependencies to be at
> least the version selected by the updated dependency

Right.

> That said if you check the patch to vendor/ these are really just
> additional lines that explicitly say which version is imported, same
> versions as before, there were no changes to vendor/ outside the one crypto
> package.

But I see this:

-# github.com/jacobsa/oglematchers v0.0.0-20150720000706-141901ea67cd
-## explicit
-# github.com/jacobsa/oglemock v0.0.0-20150831005832-e94d794d06ff
-## explicit
-# github.com/jacobsa/ogletest v0.0.0-20170503003838-80d50a735a11
-## explicit
-# github.com/jacobsa/reqtrace v0.0.0-20150505043853-245c9e0234cb
-## explicit

So these lines are really removed.

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

  reply	other threads:[~2022-07-23 20:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-25 22:42 [Buildroot] [PATCH 1/1] package/gocryptfs: fix build against riscv Christian Stewart via buildroot
2022-07-23 16:41 ` Thomas Petazzoni via buildroot
2022-07-23 19:44   ` Christian Stewart via buildroot
2022-07-23 20:22     ` Thomas Petazzoni via buildroot [this message]
2022-07-24 23:42       ` Christian Stewart via buildroot
2022-07-25  6:25         ` Thomas Petazzoni via buildroot
2022-07-25  6:27           ` Christian Stewart via buildroot
2022-07-25  6:42             ` Thomas Petazzoni via buildroot
2022-08-02 22:06 ` Thomas Petazzoni via buildroot
2022-09-14  9:10   ` Peter Korsgaard

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=20220723222237.7989b5c6@windsurf \
    --to=buildroot@buildroot.org \
    --cc=anisse@astier.eu \
    --cc=christian@paral.in \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.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