From: arete <arete@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libmtp: update to 1.1.20.
Date: Tue, 11 Oct 2022 22:02:00 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39896@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
There is a new pull request by arete against master on the void-packages repository
https://github.com/arete/void-packages libmtp
https://github.com/void-linux/void-packages/pull/39896
libmtp: update to 1.1.20.
<!-- 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/39896.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libmtp-39896.patch --]
[-- Type: text/x-diff, Size: 1059 bytes --]
From cdbbcb2317ddd06a7c460dc89e87e67b4524ebf9 Mon Sep 17 00:00:00 2001
From: Gerardo Di iorio <arete74@gmail.com>
Date: Tue, 11 Oct 2022 21:59:23 +0200
Subject: [PATCH] libmtp: update to 1.1.20.
---
srcpkgs/libmtp/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/libmtp/template b/srcpkgs/libmtp/template
index 1114a4d7bb85..e12ad1db5120 100644
--- a/srcpkgs/libmtp/template
+++ b/srcpkgs/libmtp/template
@@ -1,6 +1,6 @@
# Template file for 'libmtp'
pkgname=libmtp
-version=1.1.19
+version=1.1.20
revision=1
build_style=gnu-configure
configure_args="--disable-static --with-udev=/usr/lib/udev
@@ -12,7 +12,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="LGPL-2.1-or-later"
homepage="http://libmtp.sourceforge.net"
distfiles="${SOURCEFORGE_SITE}/${pkgname}/${pkgname}-${version}.tar.gz"
-checksum=deb4af6f63f5e71215cfa7fb961795262920b4ec6cb4b627f55b30b18aa33228
+checksum=c9191dac2f5744cf402e08641610b271f73ac21a3c802734ec2cedb2c6bc56d0
if [ "$CROSS_BUILD" ]; then
# XXX needs host mtp-hotplug
next reply other threads:[~2022-10-11 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 20:02 arete [this message]
2022-10-13 19:04 ` [PR REVIEW] " classabbyamp
2022-10-15 19:19 ` [PR PATCH] [Updated] " arete
2022-10-15 19:19 ` [PR REVIEW] " arete
2022-10-15 20:54 ` [PR PATCH] [Merged]: " classabbyamp
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-39896@inbox.vuxu.org \
--to=arete@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).