Github messages for voidlinux
 help / color / mirror / Atom feed
From: jadynbrammer <jadynbrammer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: vlc: update to 3.0.19.
Date: Sat, 11 Nov 2023 21:11:25 +0100	[thread overview]
Message-ID: <20231111201125.obRt_jJdmDEiRp7ZJ4eJK4F6xvQQCN4eKWapcyqJ2zY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46831@inbox.vuxu.org>

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

New comment by jadynbrammer on void-packages repository

https://github.com/void-linux/void-packages/pull/46831#issuecomment-1806906842

Comment:
Ah, the build is now failing due to 'libFLAC.so.8'; Because this file is versioned, is a shlibs addition the correct fix this time?

```diff
diff --git a/common/shlibs b/common/shlibs
index 7e9cee83f84..348a342dbfc 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -1465,6 +1465,7 @@ libvlccore.so.9 libvlc-3.0.2_1
 libvlc_vdpau.so.0 libvlc-2.2.0_1
 libvlc_pulse.so.0 libvlc-3.0.2_1
 libvlc_xcb_events.so.0 libvlc-3.0.2_1
+libFLAC.so.8 libvlc-3.0.19_1
 libcmocka.so.0 cmocka-1.1.1_1
 libbtrfs.so.0 libbtrfs-3.12_1
 libreiserfscore.so.0 reiserfsprogs-3.6.27_3
```
It builds successfully with this on my machine.

If this looks good, I'll update the PR.

  parent reply	other threads:[~2023-11-11 20:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46831@inbox.vuxu.org>
2023-10-25 16:32 ` [PR PATCH] [Updated] " jadynbrammer
2023-10-25 16:34 ` jadynbrammer
2023-10-30 21:15 ` [PR REVIEW] " mhmdanas
2023-10-30 21:37 ` mhmdanas
2023-10-30 21:37 ` mhmdanas
2023-11-09 18:22 ` classabbyamp
2023-11-09 18:24 ` classabbyamp
2023-11-10 20:49 ` [PR PATCH] [Updated] " jadynbrammer
2023-11-10 20:54 ` jadynbrammer
2023-11-10 20:55 ` jadynbrammer
2023-11-10 20:56 ` jadynbrammer
2023-11-10 21:06 ` classabbyamp
2023-11-10 21:17 ` [PR PATCH] [Updated] " jadynbrammer
2023-11-10 21:35 ` jadynbrammer
2023-11-10 21:41 ` classabbyamp
2023-11-10 22:03 ` [PR PATCH] [Updated] " jadynbrammer
2023-11-11 20:11 ` jadynbrammer [this message]
2023-11-11 20:53 ` classabbyamp
2023-11-11 21:30 ` jadynbrammer
2023-11-15 17:22 ` [PR PATCH] [Merged]: " Hoshpak
2023-11-15 17:22 ` Hoshpak

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=20231111201125.obRt_jJdmDEiRp7ZJ4eJK4F6xvQQCN4eKWapcyqJ2zY@z \
    --to=jadynbrammer@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).