All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Alexander Kanavin" <alex.kanavin@gmail.com>
Cc: <openembedded-core@lists.openembedded.org>,
	"Alexander Kanavin" <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH] librsvg: update 2.58.2 -> 2.59.2
Date: Thu, 05 Dec 2024 15:20:51 +0100	[thread overview]
Message-ID: <D63U0HCPA3YJ.3FKI2W07OQF0@bootlin.com> (raw)
In-Reply-To: <CANNYZj_P=3e++=WSGrCEA_6C02H5M5fp2p=cQ4Mad_7a_xexNQ@mail.gmail.com>

On Thu Dec 5, 2024 at 11:06 AM CET, Alexander Kanavin wrote:
> On Thu, 5 Dec 2024 at 10:39, Mathieu Dubois-Briand
> <mathieu.dubois-briand@bootlin.com> wrote:
> > Sorry but we still have the same error. Looking at the patch, I believe
> > it did not change from the previous version. Maybe some issue while
> > sending the v2 ?
> >
> > https://valkyrie.yoctoproject.org/#/builders/65/builds/595/steps/11/logs/stdio
>
> The difference is that one of the patches needs to be applied to a
> file in the source tree with CRLF line endings.
>
> v2 does this correctly in my build, but maybe somewhere on the way to
> you it still got corrupted. Can you cherry pick from
> akanavin/package-version-updates on poky-contrib please?
> (I just force pushed there so do a git fetch first)
>
> Alex

Thanks, it looks like it works better now. I had a similar issue with
the ovmf patch, also fixed. Let's see how this build ends, but I'm
pretty confident now.

https://valkyrie.yoctoproject.org/#/builders/29/builds/590

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2024-12-05 14:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04 12:08 [PATCH] librsvg: update 2.58.2 -> 2.59.2 Alexander Kanavin
2024-12-05  9:39 ` [OE-core] " Mathieu Dubois-Briand
2024-12-05 10:06   ` Alexander Kanavin
2024-12-05 14:20     ` Mathieu Dubois-Briand [this message]
2024-12-12 13:45 ` Ross Burton
2024-12-12 13:59   ` Alexander Kanavin

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=D63U0HCPA3YJ.3FKI2W07OQF0@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.