From: Vagrant Cascadian <vagrant@debian.org>
To: William <willbilly@fedora.email>, help-guix@gnu.org
Cc: 63095@debbugs.gnu.org
Subject: [bug#63095] Inconsistency between resolved issues/patches and source files.
Date: Thu, 21 Mar 2024 11:21:33 -0700 [thread overview]
Message-ID: <87msqrv42a.fsf@wireframe> (raw)
In-Reply-To: <20240321182833.19ff1335@fedora.email>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
On 2024-03-21, William wrote:
> 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].
It appears to be applied in core-updates as
9400188b2b57cea2f3efc998a2f3b24769db04b7, but not yet merged into the
master branch. This is probably because it would trigger too many
rebuilds...
> 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?
When closing an issue, ideally such information (commit hash and branch
if not on master) should be included in the closing message to avoid
having to look it up. :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
parent reply other threads:[~2024-03-21 19:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240321182833.19ff1335@fedora.email>]
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=87msqrv42a.fsf@wireframe \
--to=vagrant@debian.org \
--cc=63095@debbugs.gnu.org \
--cc=help-guix@gnu.org \
--cc=willbilly@fedora.email \
/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).