unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 52837@debbugs.gnu.org
Subject: bug#52837: Failed to compile rav1e which is dependence for tons of packages
Date: Tue, 28 Dec 2021 14:35:09 -0500	[thread overview]
Message-ID: <Yctm7dV44R2gZm65@jasmine.lan> (raw)
In-Reply-To: <878rw4allc.fsf@nicolasgoaziou.fr>

On Tue, Dec 28, 2021 at 02:46:23PM +0100, Nicolas Goaziou wrote:
> You reverted 100+ commits but only one of them is problematic. Could you
> unrevert them barring ad1e8a0906cca4f5c2fd18534a935a375161e608?

I did so like this:

`git cherry-pick 5b1ec376239602725171d4523406801b684ee195^..13d3120095e4baa03594d095b0afe9febbb7cee0 && \
git revert ad1e8a0906cca4f5c2fd18534a935a375161e608`

Then, rav1e (and FFmpeg) built successfully.

So, I pushed as 9309b488ca4ceef4fcc9283546e3b05c57b16ca8.

> IIUC, a safe solution would be to exceptionally provide both
> rust-dav1d-sys 0.3.2 (for rav1e) and 0.3.4 (for nushell), the latter
> being called rust-dav1d-sys-0.3.
> 
> With this we do not have to bother updating rav1e yet.
> 
> WDYT?

Sounds like a plan. Are you able to do it?




  reply	other threads:[~2021-12-28 19:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-27 23:09 bug#52837: Failed to compile rav1e which is dependence for tons of packages Evgenii Lepikhin via Bug reports for GNU Guix
2021-12-28  1:20 ` Leo Famulari
2021-12-28  1:32 ` Leo Famulari
2021-12-28 13:46   ` Nicolas Goaziou
2021-12-28 19:35     ` Leo Famulari [this message]
2021-12-28 20:31       ` Nicolas Goaziou
2021-12-28 21:29         ` Leo Famulari
2021-12-28  3:04 ` 0xFA11BABE via Bug reports for GNU Guix
2021-12-28  6:01 ` bug#52837: We need deeper research Evgenii Lepikhin via Bug reports for GNU Guix
2021-12-28 19:41   ` Leo Famulari
2021-12-29  8:42     ` Evgenii Lepikhin via Bug reports for GNU Guix
2021-12-29 13:57       ` Nicolas Goaziou

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=Yctm7dV44R2gZm65@jasmine.lan \
    --to=leo@famulari.name \
    --cc=52837@debbugs.gnu.org \
    --cc=mail@nicolasgoaziou.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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).