From: Andrew Tropin <andrew@trop.in>
To: 46113@debbugs.gnu.org
Subject: [bug#46113] [PATCH] gnu: obs: Update obs to fb347c.
Date: Tue, 26 Jan 2021 19:26:24 +0300 [thread overview]
Message-ID: <87bldbwtov.fsf@trop.in> (raw)
In-Reply-To: <87eei7wugf.fsf@trop.in>
It's a commit from master branch containing changes from PR:
https://github.com/obsproject/obs-studio/pull/4067
It's just few commits after 26.1.2 and it seems there is no any big
changes since that and should be safe to use.
I asked for 26.1.3 tag, but it seems that it won't happen in nearest
future: https://github.com/obsproject/obs-studio/issues/4100
As one of developers said to me, usually obs releases once in 3-4
months, that is why I decided to use a commit instead of tag.
The changes is needed to be able to specify plugin load path using
native-search-paths to be able to package obs plugins with guix.
next prev parent reply other threads:[~2021-01-26 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 15:59 [bug#46113] [PATCH] gnu: obs: Update obs to fb347c Andrew Tropin
2021-01-26 16:26 ` Andrew Tropin [this message]
2021-01-27 7:27 ` Alexey Abramov
2021-01-26 21:10 ` Leo Famulari
2021-01-27 9:36 ` Andrew Tropin
2021-01-27 9:45 ` [bug#46113] [PATCH] gnu: obs: Update " Andrew Tropin
2021-02-02 0:48 ` Leo Famulari
2021-02-02 11:39 ` Andrew Tropin
2021-02-02 19:33 ` Leo Famulari
2021-02-02 19:43 ` Andrew Tropin
-- strict thread matches above, loose matches on Subject: below --
2021-02-03 14:40 [bug#45707] [PATCH] gnu: obs: Update obs " Andrew Tropin
2021-02-03 21:11 ` [bug#46113] " Ludovic Courtès
2021-02-04 10:45 ` 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
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=87bldbwtov.fsf@trop.in \
--to=andrew@trop.in \
--cc=46113@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).