similar to: [nbdkit PATCH] Check for python3 first

"AM_INIT_AUTOMAKE(foreign) dnl ..." seems to trigger Debian bug#738716 --- configure.ac | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index ee9d377..df31014 100644 --- a/configure.ac +++ b/configure.ac @@ -35,7 +35,8 @@ AC_CONFIG_MACRO_DIR([m4]) AC_USE_SYSTEM_EXTENSIONS AC_SYS_LARGEFILE -AM_INIT_AUTOMAKE(foreign) dnl NB: Do not

This patch proposes to drop support for Python 2 in nbdkit. Rather than abruptly drop it everywhere, my proposal is that we point people to nbdkit 1.14 (the current stable version) if they want to continue with Python 2 plugins, while gently reminding them of the upcoming Python 2.7 end of life announcement. Libnbd never supported Python 2. Libguestfs in theory supports Python 2 but I dropped

Starting with nbdkit 1.16, Python >= 3.3 will be required. Python 2 reaches end of life on 2020-01-01: https://python3statement.org/ https://pythonclock.org/ Debian oldoldstable and RHEL 7 have Python 3.4 and 3.6 respectively, so it seems pointless to try to support Python < 3.3 which lacked support for PyUnicode_AsUTF8. --- README | 13 +++++++------ configure.ac

Hi, few miscellaneous fixes for nbdkit. Thanks, Pino Toscano (3): build: use AC_MSG_RESULT for $PERL_LDOPTS crypto: add missing '{' tests: fix generation of PKI test data configure.ac | 1 + src/crypto.c | 2 +- tests/Makefile.am | 10 +++++----- 3 files changed, 7 insertions(+), 6 deletions(-) -- 2.13.6

When using nbdsh for scripting, it is convenient to let nbdsh fail with status 1 when encountering an API failure. However, doing so by letting the nbd.Error exception leak all the way causes ABRT (on Fedora 32 at least) to assume the program crashed from a programming error, and needlessly complicates clients to have to add try: blocks. Better is if nbdsh itself prints the same stack trace that

CentOS Errata and Security Advisory 2020:5010 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2020:5010 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 69b52b527f2581aac941a0d4fa71d1bce28da1b79f2f313b12818e1090892dfb python3-3.6.8-18.el7.i686.rpm

Hallo, I?m using samba 4.11 from sernet and the vfs object full_audit. After update samba to 4.12 from sernet full_audit is broken and the shares with full_audit are not accessible. Can anyone tell me please how to install python 3 on centos7 while the Centos system needs python 2 but samba sould use python3? Thanks in advance, Peter

https://bugzilla.netfilter.org/show_bug.cgi?id=1484 Bug ID: 1484 Summary: configure script fails to detect python3 Product: nftables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: normal Priority: P5 Component: nft Assignee: pablo at

On Tue, 2019-03-19 at 21:35 +0000, Jonathan Hunter via samba wrote: > Hi, > > First of all - thanks very much to the team for the work that has gone > into 4.10.0, I have downloaded it and am looking forward to upgrading > :) > > I decided to try and use Python3 with my 4.10.0 upgrade, given the > comments in the release notes; but I have some newbie questions that >

Hi List I want to install samba 4.10.2 on centos. but after run the ./configure command show "/usr/bin/env: python3: no such file or directory" how to fix this problem, my friends. tanks.

Hello Everyone, don't know how to fix this: [andy at localhost snappergui]$ sudo python3 ./__init__.py [sudo] password for andy: Traceback (most recent call last): File "./__init__.py", line 3, in <module> import gi ImportError: No module named 'gi' [andy at localhost snappergui]$ python ./__init__.py [andy at localhost snappergui]$ sudo python ./__init__.py

Hi, First of all - thanks very much to the team for the work that has gone into 4.10.0, I have downloaded it and am looking forward to upgrading :) I decided to try and use Python3 with my 4.10.0 upgrade, given the comments in the release notes; but I have some newbie questions that hopefully others can help with. I'm really not up to speed with python3 yet! This version of Debian evidently

Hi all, In the past there was some interest in having lit supporting use with Python3, which had become the default on some Linux distributions. I've been working on this recently and as of r188398, the LLVM/Clang tests all run and pass on my system with Python 3.3. There are still some quality of implementation issues to iron out, and there may be problems with lit-based tests in other

On Wed, Jan 15, 2020 at 12:06:45PM +0000, Nick Howitt wrote: > Hello Richard, > > I am using ClearOS7 (a Centos 7 derivative which also uses EPEL) and > am using various packages in the EPEL repository. I am interested in > seeing python3-libguestfs added to EPEL in order to use wok-3.0.0 > and kimchi-3.0.0. > > Would it be possible for you to maintain the package in

On Fri, Mar 24, 2017 at 12:47:51PM +1300, Andrew Bartlett wrote: > On Thu, 2017-03-23 at 16:23 -0700, John Hixson via samba wrote: > > Are there plans to migrate the samba python code to python3? If so, > > is > > there a roadmap? If not, why not?  > > There is work ongoing for this, thanks to a number of patient and > persistent engineers at Red Hat. > > It

Are there plans to migrate the samba python code to python3? If so, is there a roadmap? If not, why not? -- John Hixson iXsystems Enterprise Storage & Servers Driven By Open Source

Hi all, Arch Linux (a rolling release distro) has updated to python3 a while back. python2 is still installed in parallel, but part of the ramifications of this move is the following:-0 1. /usr/bin/python points to /usr/bin/python3 instead of /usr/bin/python2 2. /usr/bin/python-config points to /usr/bin/python3-config instead of /usr/bin/python2-config I'm having problems with make for

On Mon, Mar 27, 2017 at 12:26:35PM +1300, Andrew Bartlett wrote: > On Fri, 2017-03-24 at 08:04 -0700, John Hixson via samba wrote: > > On Fri, Mar 24, 2017 at 12:47:51PM +1300, Andrew Bartlett wrote: > > > On Thu, 2017-03-23 at 16:23 -0700, John Hixson via samba wrote: > > > > Are there plans to migrate the samba python code to python3? If > > > > so, >

Looking for advice for best practices on fetching status of the samba server and share information. One option is to parse the output of `smbstatus` into a machine-readable format. But I noticed there are some apis documented. We are using samba 4.11 which is supposed to have full python3 api support. So the question is, can the share and lock information displayed in the `smbstatus` command

> If anyone is interested in this support, I'd appreciate it if you changed > your setup to use Python3 for running the tests and let me know (or file > bugs) for any issues you find. Excellent! The only reason I set my interpreter back to 2.7 a while back was LLVM. Back to 3.2 now. Tim. P.S. All passes here too.