all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: William <willbilly@fedora.email>
To: help-guix@gnu.org
Subject: Inconsistency between resolved issues/patches and source files.
Date: Thu, 21 Mar 2024 18:28:33 +0100	[thread overview]
Message-ID: <20240321182833.19ff1335@fedora.email> (raw)

Hello.

A few days ago I tried reencoding several video files I have laying
around to save storage, using libsvtav1 through ffmpeg, and then to my
surprise (and frustration) I realized that ffmpeg distributed by
GNU/Guix does not include such encoding library.

I checked the issue tracker and found out issues that indeed commented
on this library missing, strangely enough, an issue with a patch was
marked as solved on 16 February 2024[0], over a month ago, however when
I check the source files I notice that the patch that includes a flag to
enable this library is still not present on the latest build of ffmpeg
yet[1].


Why? How does the merging process work on Guix? Why are issues marked
as solved/done yet patches are still one month due, to submit upstream?
Am I missing something or this is a mistake on the mantainers side?

[0]: https://issues.guix.gnu.org/63095
[1]:
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/video.scm#n1780


             reply	other threads:[~2024-03-21 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 17:28 William [this message]
2024-03-21 18:21 ` Inconsistency between resolved issues/patches and source files Vagrant Cascadian
2024-03-21 18:21   ` [bug#63095] " Vagrant Cascadian
2024-04-08 23:31   ` William
2024-04-09 12:52     ` Felix Lechner via

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=20240321182833.19ff1335@fedora.email \
    --to=willbilly@fedora.email \
    --cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index

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

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.