similar to: Bug#1062048: xen: FTBFS with Python 3.12 as default

...as recommended on the Samba Wiki here: https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ#I_have_to_Use_Different_Names_to_Resolve_Host_Names_Internally_and_Externally I'm trying to use the "clever trick" to make a certain internal server resolve to the name I'm forced to use to resolve it externally. I successfully created the new zone (fictionalizing the names

On 12-10-2024 02:25, John R. Graham via samba wrote: > ...as recommended on the Samba Wiki here: > https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ#I_have_to_Use_Different_Names_to_Resolve_Host_Names_Internally_and_Externally > > I'm trying to use the "clever trick" to make a certain internal server > resolve to the name I'm forced to use to resolve

On Fri, 11 Oct 2024 20:25:00 -0400 "John R. Graham via samba" <samba at lists.samba.org> wrote: > ...as recommended on the Samba Wiki here: > https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ#I_have_to_Use_Different_Names_to_Resolve_Host_Names_Internally_and_Externally > > I'm trying to use the "clever trick" to make a certain internal >

On 10/12/24 05:15, Kees van Vloten via samba wrote: > > On 12-10-2024 02:25, John R. Graham via samba wrote: >> ...as recommended on the Samba Wiki here: >> https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ#I_have_to_Use_Different_Names_to_Resolve_Host_Names_Internally_and_Externally >> >> >> I'm trying to use the "clever trick" to

On 12-10-2024 17:15, John R. Graham via samba wrote: > > On 10/12/24 05:15, Kees van Vloten via samba wrote: >> >> On 12-10-2024 02:25, John R. Graham via samba wrote: >>> ...as recommended on the Samba Wiki here: >>> https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ#I_have_to_Use_Different_Names_to_Resolve_Host_Names_Internally_and_Externally

So, in the end looks like this setuptools 36 was deleted from pypi. There is an issue [1] open on setuptools. I can confirm by trying to force to install this version: $ pip install setuptools==36.0.0 Collecting setuptools==36.0.0 Could not find a version that satisfies the requirement setuptools==36.0.0 (from versions:<many version numbers>) No matching distribution found for

Hi All, Does anyone have experience successfully installing and loading the R package ?ggbreak? in a Docker container? I ask because I have successfully used the ?ggbreak? package in a script outside the Docker container (on my local computer), but for some reason, I get the following error message when trying to load it using library(ggbreak) or library(?ggbreak?) inside the same script that

Don't you have to load BiocManager before using it? -----Original Message----- From: R-SIG-Debian <r-sig-debian-bounces at r-project.org> On Behalf Of Gerber, Lauren J Sent: Tuesday, October 15, 2024 9:15 AM To: r-sig-debian at r-project.org Cc: dirk at eddelbuettel.com Subject: Re: [R-sig-Debian] R Package: 'ggbreak' in Dockerfile Hi All, Does anyone have experience

Hi James, I just tried fixing my script and added library(BiocManager) before library(ggbreak), then rebuilt the image, and am still getting the same error. Error in library(ggbreak) : there is no package called 'ggbreak' Execution halted I will say that when I ran docker exec docker_container_id R -e "installed.packages()" I get the following: Package

Hi, There was a new Python setuptools release (36.0.0) today, that caused this compatibility issue. The suggestion to stop breaking the builds is to add a static setuptools version on lnt's requirements.client.txt. The latest known compatible version is 35.0.2. I have tested it building a LNT sandbox and it seems to works. setuptools==35.0.2 I'll create a bug on LNT so we can

CentOS 7 box. As there's no package in any of the repos, we're trying to install scikit-learn in the user's space. It refuses. My late try was, after d/l a .whl from last year, hoping that would work with the numpy package in the regular repos, I did a pip install --user scikit-learn..., and it still seems to want to write to system space: OSError: [Errno 13] Permission denied: