From: JezerM <JezerM@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] lightdm: update to 1.32.0.
Date: Mon, 18 Jul 2022 09:24:08 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38120@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
There is a new pull request by JezerM against master on the void-packages repository
https://github.com/JezerM/void-packages lightdm-update
https://github.com/void-linux/void-packages/pull/38120
lightdm: update to 1.32.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (aarch64-glibc)
Maybe it is too early to make this PR, but I didn't encounter any issue so far.
A patch file from https://github.com/void-linux/void-packages/pull/38120.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-lightdm-update-38120.patch --]
[-- Type: text/x-diff, Size: 1232 bytes --]
From 164732de44b88cc04461c01d34bfee3550b949a3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jezer=20Mej=C3=ADa?= <amyuki4@icloud.com>
Date: Mon, 18 Jul 2022 01:10:27 -0600
Subject: [PATCH] lightdm: update to 1.32.0.
---
srcpkgs/lightdm/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/lightdm/template b/srcpkgs/lightdm/template
index b2fed5ac3c6a..e93d7845ef59 100644
--- a/srcpkgs/lightdm/template
+++ b/srcpkgs/lightdm/template
@@ -1,6 +1,6 @@
# Template file for 'lightdm'
pkgname=lightdm
-version=1.30.0
+version=1.32.0
revision=3
build_style=gnu-configure
build_helper="gir"
@@ -13,7 +13,7 @@ license="GPL-3.0-or-later, LGPL-2.0-or-later"
homepage="https://github.com/CanonicalLtd/lightdm"
changelog="https://raw.githubusercontent.com/CanonicalLtd/lightdm/master/NEWS"
distfiles="https://github.com/CanonicalLtd/lightdm/releases/download/${version}/lightdm-${version}.tar.xz"
-checksum=a118779650a3a5b20f05d53c4f9e377b484fbc1810a6b0914a60840d9a581f95
+checksum=12f5ab432748f0387c7cf8b94430495a558a035a4f8465e5181af6faff133e4b
hostmakedepends="pkg-config intltool itstool $(vopt_if gir 'gobject-introspection vala')"
makedepends="dbus-glib-devel libxklavier-devel libxml2-devel
next reply other threads:[~2022-07-18 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 7:24 JezerM [this message]
2022-07-18 7:40 ` [PR PATCH] [Updated] " JezerM
2022-07-18 22:56 ` [PR REVIEW] " classabbyamp
2022-07-18 23:26 ` [PR PATCH] [Updated] " JezerM
2022-07-18 23:29 ` [PR REVIEW] " JezerM
2022-07-19 0:18 ` [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-38120@inbox.vuxu.org \
--to=jezerm@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).