similar to: python3

On Thu, Apr 11, 2019 at 8:43 AM Gabriel O. Franca via samba <samba at lists.samba.org> wrote: > > Good morning people, > > I am opening my lab with version 4.10.2 in centos 7.6. > I'm trying to compile using python3 without success. > Has anyone managed to compile using python3 in the centos 7.6 that might > give way to the stones? > Here is the error message

On Sun, 2019-04-14 at 10:38 -0400, Nico Kadel-Garcia via samba wrote: > On Sat, Apr 13, 2019 at 11:43 PM Sérgio Basto <sergio at serjux.com> > wrote: > > > > On Sat, 2019-04-13 at 07:43 -0400, Nico Kadel-Garcia via samba > > wrote: > > > On Fri, Apr 12, 2019 at 7:20 AM Andreas Habel via samba > > > <samba at lists.samba.org> wrote: > >

Hi, is it possible to use a so called disjointed namespaces without having to "fake" the hosts fqdn giving it the AD-name as hostname? Background: We have a unix and a Windows world and each runs below it's domain. Let's say UNIX-DOMAIN and WIN-DOMAIN. When there is the need to bring the two worlds together the first choice is to use samba4 on unix joined to the AD domain name

Hi Gabriel, I've compiled Samba 4.10.2 on CentOS 7 successfully. I've read the wiki that 4.10.2 version is full compatible with python 3, specifically python 3.4. Then I've install, use the yum command, the package python34-devel and I've added an environment variable at /etc/profile with export PYTHON=python3.4. Thus, I've run ./configure, make and make install with no

Hi Nico, I've understood about use export PYTHON=python3.4 in /etc/profile. The host that I've done it is in my test environment. I have only question about this: after samba 4.10.2 installed, it ever never need use python3 to do anything about samba? PS1: In my environment, the host run only Samba (samba and bind) service. I disagree about use python 3.6 instead python 3.4, though. In

Hi all, I wanted to update my CentOS 7 install this morning and I started getting the errors from below. Any ideas on a fix? They seem to be related to cinnamon which I actually don't use at all (the machine was prepared by our IT at work and they install both Gnome and Cinnamon by default). Since I don't use it, I guess an option would be to remove it altogether and then I will

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

On Thu, 15 Jun 2017, Andreas Benzler wrote: > pygtk2-2.24.0-9.el7.x86_64 > pygtk2-libglade-2.24.0-9.el7.x86_64 > pygpgme-0.3-9.el7.x86_64 > pygobject3-3.14.0-3.el7.x86_64 > pygobject3-base-3.14.0-3.el7.x86_64 > pygobject2-2.28.6-11.el7.x86_64 > [andy at localhost ~]$ rpm -qa | grep python3 > python34-dbus-1.2.4-2.el7.x86_64 > python34-libs-3.4.5-4.el7.x86_64 >

Hi Nico, Glad to hear you're feeling better. So now we've got several builds of samba-4.10.x for centos7/rhel7: - Your 4.10.2 build (requires python36 from EPEL but is more future-proof) - Sergio's (don't know the details on those). - My modest builds (based on python2.7 and which don't require addons). As much as I agree that doing anything python2 these days in pretty much

On Fri, 2018-12-07 at 23:32 -0500, Nico Kadel-Garcia via samba wrote: > On Thu, Dec 6, 2018 at 2:35 PM Vincent S. Cojot via samba > <samba at lists.samba.org> wrote: > > > So, IMHO RHEL7/Centos7 does just fine in a Samba AD/DC setup either as > > clients or DCs. I still have a few details to work out (how to move the > > Samba servers from local auth to AD auth,

On Friday, 15 May 2020 11.33.26 WEST I?aki Ucar wrote: > The rationale behind the user settings is that the user dir is not > controlled by the system, so versioning it is the only way to avoid > breakage. For the system library, there are better tools to prevent > that. Do you know the difference between theory and practice? :-) In theory they are equal but in practice... :-) >

>I wanted to update my CentOS 7 install this morning and I started>getting the errors from below. >Any ideas on a fix? Certainly! >Error: Package: python34-xapps-overrides-1.0.4-13.el7.x86_64 (@epel) > Requires: xapps(x86-64) = 1.0.4-13.el7 > Removing: xapps-1.0.4-13.el7.x86_64 (@epel) > xapps(x86-64) = 1.0.4-13.el7 > Updated By:

On Sat, 18 May 2019, Nico Kadel-Garcia wrote: > On Wed, May 15, 2019 at 4:32 PM Tom Diehl via samba > <samba at lists.samba.org> wrote: >> >> Hi, >> >> I have a new Centos 7.6 VM that I self compiled 4.10.3 and joined it to an >> existing samba AD domain that has 2 existing DCs. One of the existing DCs is >> running 4.8.7 and the other is running

On Mon, 22 Apr 2019 01:27:47 -0400 Nico Kadel-Garcia via samba <samba at lists.samba.org> wrote: > Sergio's used python36 from iusrelease. I used the one from EPEL. Our > builds are very similar, except that I compile all the added libraries > such as libtdb, libtevent, etc. as distinct RPM's as they are > published by RHEL, just with Pythone 3.6 as well as with Python

On Mon, 20 May 2019, Nico Kadel-Garcia wrote: > On Mon, May 20, 2019 at 3:33 PM <me at tdiehl.org> wrote: >> >> On Sat, 18 May 2019, Nico Kadel-Garcia wrote: >> >>> On Wed, May 15, 2019 at 4:32 PM Tom Diehl via samba >>> <samba at lists.samba.org> wrote: >>>> >>>> Hi, >>>> >>>> I have a new Centos

On Thu, Mar 10, 2016 at 10:27:07AM -0800, Akemi Yagi wrote: > On Thu, Mar 10, 2016 at 10:07 AM, Fred Smith <fredex at fcshome.stoneham.ma.us> > wrote: > > > I'm interested in trying out the new OpenShot beta (2.06) on CentOS 7. > > Openshot requires Python3. > > > > so I look at available packages where I find a bunchof python3 packages > > as well

I'm interested in trying out the new OpenShot beta (2.06) on CentOS 7. Openshot requires Python3. so I look at available packages where I find a bunchof python3 packages as well as python34 packages. I'm assuming that python34 is version 3.4 of python, while python3 is some other 3.x version. Can anyone here explain to me what are the differences, any compatibility across these

On Thursday, 14 May 2020 23.58.02 WEST I?aki Ucar wrote: > But we still have to rebuild the packages anyway, and this setup > doesn't force us to actually rebuild them, nor the user to update > them. So a user could end up with R major.minor and a bunch of > packages installed in some major.minor-1 path that are just junk. Or > the other way around: a bunch of packages updated

> # yum install python34 I already have epel installed. If it breaks something is it as simple as yum erase python34 to restore everything back to normal? On Thu, Mar 23, 2017 at 6:27 PM, Christian, Mark <mark.christian at intel.com> wrote: > On Thu, 2017-03-23 at 18:16 -0500, Matt wrote: >> Is there a way to install Python 3.x on Centos 7.x without breaking >>

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