similar to: Problem compiling Samba4, Python installed in nonstandard location

Hi How would i upgrade python to python2.6.4 using a yum repository ( on all my servers ) and cause manual configuration is time consuming, i am using cent OS 5.4 32 bit Is there an already available repository to do this.? ------------------------------------------------------------------------------ I had tried to install it using contemporary method ( ./configure ; make ;make install) ..

I've just tried a yum update on one of my C7 boxes and got the following output. I'm guessing to fix this I need to re-install the RPM, but I can't remove it because of dependancies, so how can I fix the problem? I've managed to download a later version of the RPM, but haven't managed to find the same version as the one installed. Gary [root at zeppo ~]# yum install There

Hi Paddy, I was suspecting the same, and from the output below I think you're right. However, I was hoping I could just repair this problem for now, and worry about replacing the HDD later. I need to resume some services that also seem to generate this same error. Gary [root at zeppo services]# ll /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so -rwxr-xr-x. 1 root root 61976 Sep 15

On 26.09.2016 14:29, Richard W.M. Jones wrote: > On Mon, Sep 26, 2016 at 02:18:02PM +0200, Carl-Daniel Hailfinger wrote: >> Hi, >> >> has anyone ever run "make check" from nbd against nbdkit with a python >> plugin? I usually get segfaults during such a run, and sometimes various >> other errors happen before the segfault, suggesting that some memory

hai, ? Just an informational message and below the fixed for the problems..? ? when upgrading a member server with debian jessie with samba 4.1.17? with samba and winbind installed.? ? For me this was on?my print server. ? steps to take. ? setup the apt sources for sernet. ? install the sernet packages. apt-get install sernet-samba sernet-samba-winbind sernet-samba-common sernet-samba-libs

I'm trying to compile ices-0.3 on a RedHat 9, kernel 2.4.23 box and I receive the following error: : the use of `tmpnam_r' is dangerous, better use `mkstemp' /usr/lib/python2.2/config/libpython2.2.a(posixmodule.o)(.text+0x385e): In function `posix_tempnam': : the use of `tempnam' is dangerous, better use `mkstemp' playlist/libplaylist.a(pm_perl.o)(.text+0x515): In

Hi Gary, That "Input/output error" suggests a disk problem to me. Does that file /usr/lib64/python2.7/lib-dynload/itertoolsmodule.so actually exist and is it readable? Also look the the output of 'rpm -V python-libs' to see if rpm considers the installed files to be corrupt. If it's not that, then you could try 'yum reinstall python-libs'. Paddy On Thu, Nov 07,

On 26.09.2016 19:20, Carl-Daniel Hailfinger wrote: > On 26.09.2016 14:29, Richard W.M. Jones wrote: >> On Mon, Sep 26, 2016 at 02:18:02PM +0200, Carl-Daniel Hailfinger wrote: >>> Hi, >>> >>> has anyone ever run "make check" from nbd against nbdkit with a python >>> plugin? I usually get segfaults during such a run, and sometimes various

Dear Sir I'm facing this problem with samba 4 [root at localhost ~]# /usr/local/samba/bin/samba-tool domain provision Traceback (most recent call last): File "/usr/local/samba/bin/samba-tool", line 33, in <module> from samba.netcmd.main import cmd_sambatool File "/usr/local/samba/lib/python2.7/site-packages/samba/__init__.py", line 27, in <module>

Hi, has anyone ever run "make check" from nbd against nbdkit with a python plugin? I usually get segfaults during such a run, and sometimes various other errors happen before the segfault, suggesting that some memory corruption is underway. AFAICS a pure python plugin should not be able to cause memory corruption. Examples of nbdkit logs for running "make check" or subsets of

On 02/12/2019 10:07, Stefan G. Weichinger via samba wrote: > Am 02.12.19 um 08:47 schrieb L.P.H. van Belle via samba: >> Hai, >> >> Sorry for the late reply. > Never mind, weekend is important ... > >> Here its just apt-get distupgrade --autoremove --purge >> Without the autoremove libldb1 is not removed so libldb2 can be installed. > # apt-get distupgrade

Am 02.12.19 um 11:43 schrieb Rowland penny via samba: > On 02/12/2019 10:07, Stefan G. Weichinger via samba wrote: >> Am 02.12.19 um 08:47 schrieb L.P.H. van Belle via samba: >>> Hai, >>> >>> Sorry for the late reply. >> Never mind, weekend is important ... >> >>> Here its just apt-get distupgrade --autoremove --purge >>> Without

In that case. apt-get update apt-get remove samba winbind --autoremove apt-get dist-upgrade --autoremove apt-get install samba winbind libnss-winbind libpam-winbind tdb-tools apt-get dist-upgrade --autoremove --purge As long as you dont use --purge, everything of samba will stay on the system and you able to install the buster version. Greetz, Louis > -----Oorspronkelijk bericht-----

On 02/12/2019 10:51, Stefan G. Weichinger via samba wrote: > Am 02.12.19 um 11:43 schrieb Rowland penny via samba: >> On 02/12/2019 10:07, Stefan G. Weichinger via samba wrote: >>> Am 02.12.19 um 08:47 schrieb L.P.H. van Belle via samba: >>>> Hai, >>>> >>>> Sorry for the late reply. >>> Never mind, weekend is important ... >>>

That could do it http://packages.ubuntu.com/trusty-backports/libcgmanager0 Seems to be libc related, which is a pretty core library to much of the whole system. Hmm, which model Dell? We just got a Dell 5000 series with Ubuntu, I have not checked with my boss if there was R installation issues. Thanks, Alex On 03/23/2016 11:22 AM, Barnet Wagman wrote: > Synaptic can show the origin of

At least libpython2.7-dev and libpython3.3-dev on current Debian/unstable ship with pkg-config files. As with the pkg-config check for Lua, we check for versioned and an unversioned .pc files. --- configure.ac | 35 ++++++++++++++++++++--------------- python/Makefile.am | 2 +- 2 files changed, 21 insertions(+), 16 deletions(-) diff --git a/configure.ac b/configure.ac index

Possibly off the wall and a long shot, but is pre-installed Linux perhaps 32 bit, while the R attempt is 64? JN On 16-03-23 02:22 PM, Barnet Wagman wrote: > Synaptic can show the origin of packages. > > The only thing I see from a backport is > > libcmanager0 > > I don't think this is relevant to R. Or is it. > > The only thing I've got installed from

> Run it through its phases and report any bugs you find! [ 1495s] CMake Warning (dev) at projects/dragonegg/CMakeLists.txt:34 (get_target_property): [ 1495s] Policy CMP0026 is not set: Disallow use of the LOCATION target property. [ 1495s] Run "cmake --help-policy CMP0026" for policy details. Use the cmake_policy [ 1495s] command to set the policy and suppress this warning. [

I can make a few suggestions to help you hunt for the issue. This kind of error is often caused by conflicting packages from proposed, backports, ppas, or other 3rd party repos. If for some reason you have a dependency installed from one of those sources that is newer than what R on cran was built against (stock ubuntu 14.04) then you will hit a conflict. Simply removing backports from your repos

I just ran "apt upgrade" on my DC (Ubuntu 18.04, Samba 4.10 from Louis Repo) and it ended with error messages about unmet dependencies in regards to libldb1. root at DC1:~# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet