Github messages for voidlinux
 help / color / mirror / Atom feed
From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Gstreamer 1.22.1
Date: Wed, 22 Mar 2023 02:25:31 +0100	[thread overview]
Message-ID: <20230322012531.ADODvBJBOB-tgr5J0b66bUinp1J8mGUeeBJDGdns0_Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42861@inbox.vuxu.org>

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

New comment by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/pull/42861#issuecomment-1478796937

Comment:
> I guess that goes back to my OP question - should it be 1.22 or 1.0 like the other gst-plugins ? See 18 and 14 in there too.

It shouldn't really matter. If you can confirm that `libgsttranscoder-1.0.so.0` *is* in gst-plugins-bad1 1.0, then feel free to to use that version, otherwise, feel free to just put the latest version. You should probably leave the other versions alone unless there is a sobump.

  parent reply	other threads:[~2023-03-22  1:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 15:06 [PR PATCH] " zlice
2023-03-22  0:51 ` oreo639
2023-03-22  1:02 ` zlice
2023-03-22  1:24 ` oreo639
2023-03-22  1:25 ` oreo639 [this message]
2023-03-22  1:25 ` oreo639
2023-03-22  1:26 ` oreo639
2023-03-22  1:41 ` oreo639
2023-03-22  1:42 ` oreo639
2023-03-22 12:24 ` [PR PATCH] [Updated] " zlice
2023-03-22 12:31 ` zlice
2023-05-01  0:35 ` [PR PATCH] [Updated] " zlice
2023-05-01  0:36 ` Gstreamer 1.22.2 zlice
2023-06-19 20:22 ` [PR PATCH] [Updated] " zlice
2023-06-23 20:14 ` [PR PATCH] [Merged]: " Duncaen

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=20230322012531.ADODvBJBOB-tgr5J0b66bUinp1J8mGUeeBJDGdns0_Q@z \
    --to=oreo639@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).