Github messages for voidlinux
 help / color / mirror / Atom feed
From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] [WIP] py-spy: update to 0.3.3.
Date: Mon, 28 Mar 2022 05:29:15 +0200	[thread overview]
Message-ID: <20220328032915.VhTT6qE8bYhun9BJ6I_aLklkwxbIA-STcACoTdqnSLs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22932@inbox.vuxu.org>

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

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

https://github.com/abenson/void-packages py-spy_0.3.3
https://github.com/void-linux/void-packages/pull/22932

[WIP] py-spy: update to 0.3.3.
Trying to see if it works for other archs now. 

I get this error at least for `aarch64`:

    aarch64-linux-gnu-objdump: warning: /destdir/aarch64-linux-gnu/py-spy-0.3.3/usr/bin/py-spy: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0000000



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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-py-spy_0.3.3-22932.patch --]
[-- Type: text/x-diff, Size: 1120 bytes --]

From 471d1f668b9fd3c9ad95047c7bfa3dd7e9282c16 Mon Sep 17 00:00:00 2001
From: Andrew Benson <abenson+void@gmail.com>
Date: Mon, 15 Jun 2020 21:56:52 -0500
Subject: [PATCH] py-spy: update to 0.3.11.

---
 srcpkgs/py-spy/template | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/py-spy/template b/srcpkgs/py-spy/template
index fcedf8091027..eee2f3a6dfab 100644
--- a/srcpkgs/py-spy/template
+++ b/srcpkgs/py-spy/template
@@ -1,13 +1,14 @@
 # Template file for 'py-spy'
 pkgname=py-spy
-version=0.1.11
-# other archs can't compile remoteprocess
-archs="x86_64* i686*"
+version=0.3.11
 revision=1
 build_style=cargo
+makedepends="libunwind-devel"
+checkdepends="python3"
 short_desc="Sampling profiler for Python programs"
 maintainer="Wilson Birney <wpb@360scada.com>"
 license="GPL-3.0-or-later"
 homepage="https://github.com/benfred/py-spy"
 distfiles="https://github.com/benfred/py-spy/archive/v${version}.tar.gz"
-checksum=399a1be66414c2f1a3d57b20d1b219393e0dfd5370815b2c0d1406fa0886917e
+checksum=094cfb80e2c099763453fc39cfa9c46cfa423afa858268c6a7bc0d867763b014
+make_check=extended

  parent reply	other threads:[~2022-03-28  3:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22932@inbox.vuxu.org>
2021-02-01 16:57 ` abenson
2021-02-01 16:59 ` abenson
2021-03-29 18:03 ` [PR PATCH] [Updated] " abenson
2021-04-13 15:40 ` abenson
2021-04-13 21:31 ` ericonr
2021-05-26 17:20 ` [PR PATCH] [Updated] " abenson
2021-05-26 17:31 ` abenson
2022-01-03 22:11 ` ericonr
2022-03-28  3:28 ` [PR PATCH] [Updated] " abenson
2022-03-28  3:29 ` abenson [this message]
2022-06-27  2:14 ` github-actions
2022-07-12  2:15 ` [PR PATCH] [Closed]: " github-actions

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=20220328032915.VhTT6qE8bYhun9BJ6I_aLklkwxbIA-STcACoTdqnSLs@z \
    --to=abenson@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).