unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 53893@debbugs.gnu.org
Subject: [bug#53893] Fix non-sequencer from failing to build
Date: Wed, 9 Feb 2022 14:02:27 -0500	[thread overview]
Message-ID: <YgQPw+twaJthrfXD@jasmine.lan> (raw)
In-Reply-To: <045524f36b0dd4124dde52319e09a70b@disroot.org>

On Wed, Feb 09, 2022 at 03:46:02AM +0000, sughosha--- via Guix-patches via wrote:
> diff --git a/gnu/packages/music.scm b/gnu/packages/music.scm
> index ddb1126a47..5a67a6e0d2 100644
> --- a/gnu/packages/music.scm
> +++ b/gnu/packages/music.scm
> @@ -1773,7 +1773,7 @@ (define-public non-sequencer
>                       '()))
>           #:python ,python-2))
>        (inputs
> -       (list jack-1 libsigc++ liblo ntk))
> +       (list jack-1 libsigc++-2 liblo ntk))
>        (native-inputs
>         (list pkg-config))
>        (home-page "https://non.tuxfamily.org/wiki/Non%20Sequencer")

Thanks! I confirm it fixes the issue.

Normally I would push your change now. However, I'm not sure who to
credit for the fix.

You are free to use any name and email address that you prefer,
including pseudonyms.

Because this is your first patch (and would be your first commit in our
Git repo), I want to check with you what you want to appear in the Git
author field and the list of authors of 'gnu/packages/music.scm':

https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/music.scm

As you continue to contribute, you can learn how to follow the steps
in the manual section Submitting Patches, and then your patches will
include this info when they are sent.




  reply	other threads:[~2022-02-09 19:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09  3:46 [bug#53893] Fix non-sequencer from failing to build sughosha--- via Guix-patches via
2022-02-09 19:02 ` Leo Famulari [this message]
2022-02-10 11:18 ` sughosha--- via Guix-patches via
2022-02-14  0:26   ` Leo Famulari

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=YgQPw+twaJthrfXD@jasmine.lan \
    --to=leo@famulari.name \
    --cc=53893@debbugs.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 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).