Github messages for voidlinux
 help / color / mirror / Atom feed
From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libmtp: update to 1.1.19.
Date: Wed, 29 Dec 2021 22:42:28 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34757@inbox.vuxu.org> (raw)

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

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

https://github.com/tornaria/void-packages libmtp
https://github.com/void-linux/void-packages/pull/34757

libmtp: update to 1.1.19.
Also add a group _libmtp with r/w permission to accesss mtp devices.
#### Testing the changes
- I tested the changes in this PR: **YES**

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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libmtp-34757.patch --]
[-- Type: text/x-diff, Size: 1476 bytes --]

From a20e47eb61bce327d104f0ad3abc4af0bcc12e1c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Gonzalo=20Tornar=C3=ADa?= <tornaria@cmat.edu.uy>
Date: Wed, 29 Dec 2021 18:36:58 -0300
Subject: [PATCH] libmtp: update to 1.1.19.

Also add a group _libmtp with r/w permission to accesss mtp devices.
---
 srcpkgs/libmtp/template | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/libmtp/template b/srcpkgs/libmtp/template
index 5bf05cd6bbe3..0ec1366dc11d 100644
--- a/srcpkgs/libmtp/template
+++ b/srcpkgs/libmtp/template
@@ -1,9 +1,10 @@
 # Template file for 'libmtp'
 pkgname=libmtp
-version=1.1.18
+version=1.1.19
 revision=1
 build_style=gnu-configure
-configure_args="--disable-static --with-udev=/usr/lib/udev"
+configure_args="--disable-static --with-udev=/usr/lib/udev
+ --with-udev-group=_libmtp"
 hostmakedepends="pkg-config"
 makedepends="libgcrypt-devel libusb-devel"
 short_desc="Library for Microsoft's Media Transfer Protocol (MTP)"
@@ -11,7 +12,10 @@ 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=7280fe50c044c818a06667f45eabca884deab3193caa8682e0b581e847a281f0
+checksum=deb4af6f63f5e71215cfa7fb961795262920b4ec6cb4b627f55b30b18aa33228
+
+# the group that gets r/w permission to access mtp devices
+system_groups=_libmtp
 
 if [ "$CROSS_BUILD" ]; then
 	# XXX needs host mtp-hotplug

             reply	other threads:[~2021-12-29 21:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 21:42 tornaria [this message]
2022-01-04  8:01 ` [PR REVIEW] " ericonr
2022-01-05  1:15 ` tornaria
2022-01-20 13:21 ` tornaria
2022-02-25 21:55 ` Piraty
2022-02-25 21:57 ` Piraty
2022-02-25 22:03 ` tornaria
2022-02-25 22:15 ` tornaria
2022-02-25 23:08 ` Piraty
2022-02-26  0:32 ` Piraty
2022-02-26 13:35 ` tornaria
2022-02-26 21:58 ` Piraty
2022-02-27 17:38 ` tornaria
2022-03-19 23:07 ` [PR PATCH] [Updated] " tornaria
2022-03-19 23:10 ` [PR REVIEW] " tornaria
2022-03-19 23:12 ` tornaria
2022-04-06 22:53 ` 0x5c
2022-04-10 20:42 ` libmtp: update to 1.1.19, use plugdev group for r/w access to mtp devices tornaria
2022-04-10 23:39 ` [PR PATCH] [Merged]: " q66

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-34757@inbox.vuxu.org \
    --to=tornaria@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).