From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Gstreamer 1.22.2
Date: Fri, 23 Jun 2023 22:14:12 +0200 [thread overview]
Message-ID: <20230623201412.eWlVHsBtr8Z5o8OQDm1bUhKfpOsKzbtDWz3cFV7Nllg@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: 788 bytes --]
There's a merged pull request on the void-packages repository
Gstreamer 1.22.2
https://github.com/void-linux/void-packages/pull/42861
Description:
#### Testing the changes
- I tested the changes in this PR: **YES** **partially**
not installed:
- gst-omx
- gst-rtsp-server
- gst1-editing-services
- gst1-python3
#### Local build testing
- I built this PR locally for my native architecture **x86_64**
#### Comments
Change distfiles to vars for rtsp like the other packages.
#### Questions
I see `shlibs` has some libgst* links to 1.0 versions and then what I assume are leftover 1.18.3_2 versions? should those be removed? I don't see anything like a 1.xx on my box, only 2023 and 1.0s. It's a relatively new build and gst* is getting bumped from 1.20.3.
prev parent reply other threads:[~2023-06-23 20:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 15:06 [PR PATCH] Gstreamer 1.22.1 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
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 ` Duncaen [this message]
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=20230623201412.eWlVHsBtr8Z5o8OQDm1bUhKfpOsKzbtDWz3cFV7Nllg@z \
--to=duncaen@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).