Github messages for voidlinux
 help / color / mirror / Atom feed
From: OliveThePuffin <OliveThePuffin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Updated ceres-solver to 2.1.0_1
Date: Sat, 22 Jul 2023 08:49:57 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45190@inbox.vuxu.org> (raw)

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

There is a new pull request by OliveThePuffin against master on the void-packages repository

https://github.com/OliveThePuffin/void-packages ceres-solver-2.1.0
https://github.com/void-linux/void-packages/pull/45190

Updated ceres-solver to 2.1.0_1
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**|**briefly**|**NO**
YES


#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl (cross-built on x86_64-glibc)



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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ceres-solver-2.1.0-45190.patch --]
[-- Type: text/x-diff, Size: 771 bytes --]

From 35f3065ec53c2692675533755b41659a74d20b28 Mon Sep 17 00:00:00 2001
From: Samuel Clay <samuel.clay99@gmail.com>
Date: Sat, 22 Jul 2023 00:40:34 -0600
Subject: [PATCH] Updated ceres-solver to 2.1.0_1

---
 common/shlibs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/common/shlibs b/common/shlibs
index dc2e91141d95..bedfdce9ff66 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -3699,7 +3699,7 @@ libircclient.so.1 libircclient-1.10_5
 libFAudio.so.0 FAudio-19.05_1
 libqaccessibilityclient-qt5.so.0 libqaccessibilityclient-0.4.0_1
 libnitrokey.so.3 libnitrokey-3.4.1_1
-libceres.so.2 ceres-solver-2.0.0_1
+libceres.so.3 ceres-solver-2.1.0_1
 libgraphene-1.0.so.0 graphene-1.8.2_1
 libflite.so.1 flite-2.1_1
 libflite_cmu_us_kal.so.1 flite-2.1_1

             reply	other threads:[~2023-07-22  6:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22  6:49 OliveThePuffin [this message]
2023-07-22  7:05 ` [PR PATCH] [Updated] " OliveThePuffin
2023-07-23 18:17 ` ceres-solver: update to 2.1.0 OliveThePuffin
2023-07-23 22:20 ` Duncaen
2023-07-24  0:46 ` [PR PATCH] [Updated] " OliveThePuffin
2023-07-24 20:41 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45190@inbox.vuxu.org \
    --to=olivethepuffin@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).