Github messages for voidlinux
 help / color / mirror / Atom feed
From: lemmi <lemmi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] gerbera: update to 1.12.1.
Date: Tue, 14 Mar 2023 11:23:55 +0100	[thread overview]
Message-ID: <20230314102355.m4G9gzphn7MLE3hcex0blmoOBoJFBwkPVmB7lCOijQE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42716@inbox.vuxu.org>

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

There is an updated pull request by lemmi against master on the void-packages repository

https://github.com/lemmi/void-packages gerbera
https://github.com/void-linux/void-packages/pull/42716

gerbera: update to 1.12.1.
Also adds `libupnp` options since `gerbera` complains about them otherwise:
```
CMake Warning at CMakeLists.txt:405 (message):
      !! It is strongly recommended to build libupnp with --enable-reuseaddr !!
      Without this option Gerbera will be unable to restart with the same port number.

CMake Warning at CMakeLists.txt:412 (message):
      !! It is strongly recommended to build libupnp with --disable-blocking-tcp-connections !!
      Without this option non-responsive control points can cause libupnp to hang.
```
Restarts are indeed not cleanly possible without them.

A patch file from https://github.com/void-linux/void-packages/pull/42716.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-gerbera-42716.patch --]
[-- Type: text/x-diff, Size: 0 bytes --]



      parent reply	other threads:[~2023-03-14 10:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12  7:37 [PR PATCH] " lemmi
2023-03-12  7:37 ` lemmi
2023-03-12  7:58 ` [PR PATCH] [Updated] " lemmi
2023-03-14  8:55 ` crater2150
2023-03-14 10:23 ` [PR PATCH] [Closed]: " lemmi
2023-03-14 10:23 ` lemmi [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=20230314102355.m4G9gzphn7MLE3hcex0blmoOBoJFBwkPVmB7lCOijQE@z \
    --to=lemmi@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).