all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: jgart <jgart@dismail.de>
Cc: 59372@debbugs.gnu.org
Subject: [bug#59372] [PATCH] gnu: peek: Add missing input.
Date: Sat, 19 Nov 2022 10:38:26 +0100	[thread overview]
Message-ID: <87o7t39sql.fsf@nckx> (raw)
In-Reply-To: <20221118220730.GB6211@dismail.de>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

jgart 写道:
> It was complaining on Ubuntu when I started it that either 
> ffmpeg needs
> to be installed or a gnome-shell needs to be running. I didn't 
> log the
> exact error message but that was more or less it.

And how does this patch provide ffmpeg?  It adds it to the build 
environment, but what happens then?

We know it doesn't add a reference to the final ‘peek’ output (you 
can verify this yourself, assuming peek builds reproducibly).  It 
doesn't change any code in the peek binary.

So what's the mechanism by which it would work?  It will need to 
be documented.

>> How are you invoking both peeks, and testing the difference?
>
> When I add ffmpeg it worked without the warning and actually 
> started
> recording my screen as expected. After pressing the record 
> button of
> course ;()

But how exactly?  Please provide exact steps and commands.

( 写道:
> Could you also update the inputs/arguments style to gexp form?

…but in a separate patch, please.)

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2022-11-19  9:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19  1:27 [bug#59372] [PATCH] gnu: peek: Add missing input jgart via Guix-patches via
2022-11-19  2:50 ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-19  4:07   ` jgart via Guix-patches via
2022-11-19  9:38     ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2022-11-21 14:27       ` jgart via Guix-patches via
2022-11-21 15:14         ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-21 20:18         ` Tobias Geerinckx-Rice via Guix-patches via
2022-11-21 20:58           ` jgart via Guix-patches via
2023-01-29  6:02             ` bug#59372: " 宋文武 via Guix-patches via
2022-11-21 17:13   ` [bug#59372] " zimoun
2022-11-21 19:38     ` jgart via Guix-patches via
2022-11-22 14:39       ` zimoun
2022-11-22 18:29         ` jgart via Guix-patches via
2022-11-19  9:13 ` ( via Guix-patches 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=87o7t39sql.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=59372@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    --cc=me@tobias.gr \
    /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.