First, thank you all for the insightful replies !
> - psrecord as source package name
> - python3-psrecord as binary package name (shipping executable and module)
>
>
> Is choosing psrecord as source package name still advisable in the above
> cases? Or is python-psrecord as source package name
On October 27, 2024 9:04:41 PM UTC, Peter Wienemann wrote:
>Hi Scott,
>
>On 2024-10-27 20:12:28, Peter Wienemann wrote:
>> On 2024-10-26 17:00:18, Scott Kitterman wrote:
>>> From reading this thread, it seems like psrecord is an application written
>>> in Python. Upstream could, if they felt
Hi Scott,
On 2024-10-27 20:12:28, Peter Wienemann wrote:
On 2024-10-26 17:00:18, Scott Kitterman wrote:
From reading this thread, it seems like psrecord is an application
written in Python. Upstream could, if they felt like it, re-implement
the whole thing in
Rust and it would still be psrec
Hi Alexandru,
On 2024-10-24 21:30:48, Peter Wienemann wrote:
d/control
-
a) The present code fails to build in a clean build environment because
the following build dependencies are missing:
- python3-psutil
- help2man
b) The "Provides" field should be removed (cf. [3]).
I forgot on
Hi Scott,
On 2024-10-26 17:00:18, Scott Kitterman wrote:
From reading this thread, it seems like psrecord is an application written in
Python. Upstream could, if they felt like it, re-implement the whole thing in
Rust and it would still be psrecord. Assuming that's at least generally
correct,
Hi all,
I would like to join the Debian Python Team on salsa. My username is @harry.
I am currently a DM and have been maintaining several packages[1].
I would like to maintain some new packages along with the team, like virtualbmc
(#1086153).
I have read have read the Debian Python Team Policy
Package: wnpp
Severity: wishlist
Owner: harry-c...@outlook.com
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org
* Package name: virtualbmc
Version : 3.1.0
* URL : https://github.com/openstack/virtualbmc
* License : Apache-2.0
Programmi
7 matches
Mail list logo
