From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Updates: OTPClient 3.1.8, libcotp 2.0.1
Date: Wed, 28 Jun 2023 10:11:55 +0200 [thread overview]
Message-ID: <20230628081155.b-V6Bmx04L-MBx8PeognuGng4ol6T3fIumZ8paH4Dk4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42619@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
There's a merged pull request on the void-packages repository
Updates: OTPClient 3.1.8, libcotp 2.0.1
https://github.com/void-linux/void-packages/pull/42619
Description:
The new library version is needed for *OTPClient*, since it replaces `libbaseencode` in new releases.
I am also willing to adopt *OTPClient*, but it has a listed maintainer.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64)
- I built this PR locally for these architectures:
- i686
prev parent reply other threads:[~2023-06-28 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 14:38 [PR PATCH] Updates: OTPClient 3.1.4, libcotp 2.0.0 realcharmer
2023-04-06 20:08 ` [PR PATCH] [Updated] " realcharmer
2023-05-05 4:32 ` [PR PATCH] [Updated] Updates: OTPClient 3.1.6, " realcharmer
2023-05-30 13:51 ` [PR PATCH] [Updated] Updates: OTPClient 3.1.6, libcotp 2.0.1 realcharmer
2023-05-30 13:53 ` Updates: OTPClient 3.1.7, " realcharmer
2023-06-27 21:58 ` [PR REVIEW] " classabbyamp
2023-06-28 7:34 ` [PR PATCH] [Updated] " realcharmer
2023-06-28 7:36 ` Updates: OTPClient 3.1.8, " realcharmer
2023-06-28 7:38 ` [PR PATCH] [Updated] " realcharmer
2023-06-28 8:11 ` classabbyamp [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=20230628081155.b-V6Bmx04L-MBx8PeognuGng4ol6T3fIumZ8paH4Dk4@z \
--to=classabbyamp@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).