From: jsbronder <jsbronder@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] connman: update to 1.41.
Date: Thu, 10 Feb 2022 19:10:43 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35514@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
There is a new pull request by jsbronder against master on the void-packages repository
https://github.com/jsbronder/void-packages connman-1.41
https://github.com/void-linux/void-packages/pull/35514
connman: update to 1.41.
#### Testing the changes
- I tested the changes in this PR: **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
- armv7l
A patch file from https://github.com/void-linux/void-packages/pull/35514.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-connman-1.41-35514.patch --]
[-- Type: text/x-diff, Size: 1097 bytes --]
From 80944373e3754c2cafd8ad45bb60ec3c5b8bc594 Mon Sep 17 00:00:00 2001
From: Justin Bronder <jsbronder@cold-front.org>
Date: Thu, 10 Feb 2022 12:59:53 -0500
Subject: [PATCH] connman: update to 1.41.
---
srcpkgs/connman/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/connman/template b/srcpkgs/connman/template
index f133b12d2967..191814ed79ba 100644
--- a/srcpkgs/connman/template
+++ b/srcpkgs/connman/template
@@ -1,6 +1,6 @@
# Template file for 'connman'
pkgname=connman
-version=1.40
+version=1.41
revision=1
build_style=gnu-configure
configure_args="--enable-polkit --enable-client --enable-pie --enable-ethernet
@@ -17,7 +17,7 @@ license="GPL-2.0-only"
homepage="https://01.org/connman"
changelog="https://git.kernel.org/pub/scm/network/connman/connman.git/plain/ChangeLog"
distfiles="${KERNEL_SITE}/network/${pkgname}/${pkgname}-${version}.tar.xz"
-checksum=1a57ae7ce234aa3a1744aac3be5c2121d98dce999440ef8ab9cc4edfd5edcb12
+checksum=79fb40f4fdd5530c45aa8e592fb16ba23d3674f3a98cf10b89a6576f198de589
lib32disabled=yes
pre_configure() {
next reply other threads:[~2022-02-10 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 18:10 jsbronder [this message]
2022-02-12 15:55 ` [PR PATCH] [Merged]: " paper42
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-35514@inbox.vuxu.org \
--to=jsbronder@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).