Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] fvwm: use python3.
Date: Sun, 21 Feb 2021 20:07:40 +0100	[thread overview]
Message-ID: <20210221190740.o7XCja0GS9XD14O7XhCyLmreqvt2NLVtDZGyT2uk4I8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28908@inbox.vuxu.org>

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

There is an updated pull request by ericonr against master on the void-packages repository

https://github.com/ericonr/void-packages fvwm
https://github.com/void-linux/void-packages/pull/28908

fvwm: use python3.
<!-- Mark items with [x] where applicable -->

@leahneukirchen 

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/28908.patch is attached

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

From d6d382188899dafd13bb853b93afa87046c4bdb7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89rico=20Rolim?= <erico.erc@gmail.com>
Date: Sat, 20 Feb 2021 01:37:25 -0300
Subject: [PATCH] fvwm: use python3.

---
 srcpkgs/fvwm/INSTALL.msg | 3 +++
 srcpkgs/fvwm/template    | 8 ++++----
 2 files changed, 7 insertions(+), 4 deletions(-)
 create mode 100644 srcpkgs/fvwm/INSTALL.msg

diff --git a/srcpkgs/fvwm/INSTALL.msg b/srcpkgs/fvwm/INSTALL.msg
new file mode 100644
index 00000000000..1efd94107c7
--- /dev/null
+++ b/srcpkgs/fvwm/INSTALL.msg
@@ -0,0 +1,3 @@
+The FVWM package has moved from Python 2 to Python 3,
+so be sure to check your scripts for compatibility
+with Python 3.
diff --git a/srcpkgs/fvwm/template b/srcpkgs/fvwm/template
index f5c988338a9..6ca6338a49a 100644
--- a/srcpkgs/fvwm/template
+++ b/srcpkgs/fvwm/template
@@ -1,13 +1,13 @@
 # Template file for 'fvwm'
 pkgname=fvwm
 version=2.6.9
-revision=1
+revision=2
 build_style=gnu-configure
-hostmakedepends="libxslt pkg-config python"
+hostmakedepends="libxslt pkg-config python3"
 makedepends="fribidi-devel libXcursor-devel libXft-devel libXinerama-devel
  libXpm-devel libXt-devel librsvg-devel perl readline-devel"
-depends="perl python"
-short_desc="An extremely powerful ICCCM-compliant window manager"
+depends="perl python3"
+short_desc="Extremely powerful ICCCM-compliant window manager"
 maintainer="Leah Neukirchen <leah@vuxu.org>"
 license="GPL-2.0-or-later, MIT"
 homepage="http://fvwm.org/"

  parent reply	other threads:[~2021-02-21 19:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20  4:38 [PR PATCH] " ericonr
2021-02-21 15:25 ` ThomasAdam
2021-02-21 19:07 ` ericonr [this message]
2021-02-21 19:15 ` [PR PATCH] [Updated] " ericonr
2021-02-21 19:15 ` [PR PATCH] [Merged]: " ericonr

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=20210221190740.o7XCja0GS9XD14O7XhCyLmreqvt2NLVtDZGyT2uk4I8@z \
    --to=ericonr@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).