From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] blueman: update to 2.3.5.
Date: Wed, 11 Jan 2023 08:58:55 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41573@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
There is a new pull request by steinex against master on the void-packages repository
https://github.com/steinex/void-packages blueman
https://github.com/void-linux/void-packages/pull/41573
blueman: update to 2.3.5.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/41573.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-blueman-41573.patch --]
[-- Type: text/x-diff, Size: 1243 bytes --]
From cea76fd61a4803b0bbc9c447e3ff0641f9542541 Mon Sep 17 00:00:00 2001
From: Frank Steinborn <steinex@nognu.de>
Date: Wed, 11 Jan 2023 08:38:32 +0100
Subject: [PATCH] blueman: update to 2.3.5.
---
srcpkgs/blueman/template | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/srcpkgs/blueman/template b/srcpkgs/blueman/template
index 936ddfce8248..d58e75d5ed2b 100644
--- a/srcpkgs/blueman/template
+++ b/srcpkgs/blueman/template
@@ -1,7 +1,7 @@
# Template file for 'blueman'
pkgname=blueman
-version=2.3.4
-revision=2
+version=2.3.5
+revision=1
build_style=gnu-configure
configure_args="--disable-static"
hostmakedepends="intltool iproute2 pkg-config python3-Cython glib-devel
@@ -15,9 +15,4 @@ license="GPL-3.0-or-later"
homepage="https://github.com/blueman-project/blueman"
changelog="https://raw.githubusercontent.com/blueman-project/blueman/main/CHANGELOG.md"
distfiles="https://github.com/blueman-project/blueman/releases/download/${version}/blueman-${version}.tar.xz"
-checksum=c20633821437f32c9d3d190ecd70d1e2f7255d74a7d6979f22711bdc2e560152
-
-post_extract() {
- # force regeneration of this file
- rm module/_blueman.c
-}
+checksum=b2d21afdf77a06cd86daf5402406f7d2a53459817e29e0bebc4911d4f0dcfda1
next reply other threads:[~2023-01-11 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 7:58 steinex [this message]
2023-01-12 4:41 ` [PR PATCH] [Merged]: " classabbyamp
-- strict thread matches above, loose matches on Subject: below --
2022-12-21 3:19 [PR PATCH] " cinerea0
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-41573@inbox.vuxu.org \
--to=steinex@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).