similar to: Samba 4.7rc4. (Debian Stretch Amd64 packages/sources available)

> -----Oorspronkelijk bericht----- > Van: Andrew Bartlett [mailto:abartlet at samba.org] > Verzonden: donderdag 17 augustus 2017 20:57 > Aan: L.P.H. van Belle; samba at lists.samba.org > Onderwerp: Re: [Samba] Samba 4.7rc4. (Debian Stretch Amd64 > packages/sources available) > > On Thu, 2017-08-17 at 12:35 +0200, L.P.H. van Belle via samba wrote: > > Can anyone (

Hello Andrew, First, thank you for the very quick reply. ... > > When a higer samba version is added? or when the dc with > FSMO DC is upgrade? > > I know its against recommendations to run different > versions of the DC's. > > The DB of the new domain will be in a slightly new (but backward > compatible) format. The domain isn't upgraded. We may

Hai guys, I've updated the Debian Stretch package for Samba 4.10.2, 4.9.6 and 4.8.11. Repo info : https://apt.van-belle.nl Build logs: http://downloads.van-belle.nl/samba4/Buildlogs/stretch/ Quick repo setup: Optional: apt-get install apt-transport-https Import my public key: wget -O - http://apt.van-belle.nl/louis-van-belle.gpg-key.asc | apt-key add - # Example repo stretch 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 the autoremove libldb1 is not removed so libldb2 can be installed. > # apt-get distupgrade

On 14 December 2014 at 20:50, David Majnemer <david.majnemer at gmail.com> wrote: > Just a reminder, these bots are still not operational because of this > change. Well, there were valid objections to lowering the requirement. If we can require the host compiler to be upgraded, it is probably ok to require python to be upgraded too, no? Cheers, Rafael

On 24 February 2016 at 19:49, Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Great! I'll circle around to this at some point. Despite the "obvious" > nature of it I still am wary of underestimating the cruftiness of the > buildbots, so I'll probably do it some time at night when the bots are > mostly green so that I can easily see if any bots

At the beginning of the year, I've landed a large set of patches to support both Python 2 and Python3 in most Python scripts. Looks like I missed some of them :-) At that time, backward portability with Python2 was still relevant, and I suspect it will still be the case for a few distributions that ship Python2 by default. That being said, Even RHEL8 uses Python3 by default, so at some point

Hai, ? We have noticed a depency that was missing in the latest 4.10.6 builds.? Affected are Debian Stretch and Buster. ? If you where running samba 4.10.5 and upgraded you might not?notice this problem. If you did not use samba-tool, you might not have noticed it. New installs?and people building from my sources did noticed it. ? Thank you guys for the reports ! @Marcio Demetrio Bacci

IMO, having non-critical utility scripts require python 3 should be allowed now. But, not yet for any scripts which are critical to build or test the distributed components. If we need to spend some time to fix the test runner to allow properly skipping tests of python3-only components when python3 isn't available, that seems entirely worthwhile, since we only need to do that once. On Tue,

I define "critical" as: anything which is required to build or test any components which are part of a release. The intent being that we DO continue to support python 2 for building llvm, and for end-users of llvm, for now. However, developers of LLVM can be assumed to be able to install python3 if they want to be able to run these various optional, auxiliary, scripts. Having a unit

Nope. Regarding "python" potentially pointing to python3: Arch Linux has done that for years. That unilateral decision on their part was widely-decried as a mistake at the time, and spawned the python doc you reference saying that shouldn't be done. However, Fedora is now making noises about doing the same, in a few years, after driving a change in the upstream recommendation.

Upgrading DC1 at site 3 (next site ;-)) I edited sources.list and van-belle.list (s/stretch/buster/g ...) apt-get update: ok apt-get upgrade: as well apt-get dist-upgrade: DANGER -> it tells me it would remove samba! Die folgenden Pakete werden ENTFERNT: libcurl3 libkdb5-8 libmariadbclient18 libnss-winbind libpam-winbind libsmbclient libuptimed0 python3-ldb python3-samba samba

Hai Guys, ? Its finaly done, so the latest are online now. The following has been done:? Debian Stretch samba 4.9.11?and?4.10.6?settings are updated with latest Official Debian Samba packages. Other packages?will follow soon. ? The changes logs of these changes, including the debian changes. For 4.9.11 and 4.10.6 where the base of 4.9.11 is also re-used. ? The samba Change logs.

On 12/03/2012 08:18 AM, Marc J. Driftmeyer wrote: > One of the most conservative distributions is Debian. > > The python_defaults package has moved to 2.7.3 in Sid and 2.7.3~rc2-1 in > Wheezy (Debian 7.0 now on its 4th beta and soon to be release candidate > status). > > I personally run Sid/Unstable in order to get general release builds of > LLVM/Clang > 2.9, never

It sounds like you ran into a bug in the test infrastructure's code to determine if python3 is supported. Fixing that might be harder, but it only needs to be fixed once no matter how much more python3 development there will be. Right now, most of our scripts were originally written for python 2, so certainly it's easy for them to support python 2. But, it was a lot of work by various

On Fri, Nov 30, 2018 at 03:25:10PM +0100, Serge Guelton via llvm-dev wrote: > On Thu, Feb 01, 2018 at 04:47:03PM -0500, James Y Knight via llvm-dev wrote: > > That said, I do think it could make sense to prepare llvm for the world in > > which "python" is python3 on some systems. So, I'd propose the following: > > 1. Change all #! lines to say

Sadly, neither the latest version of RedHat (released in 2014), nor the latest version of macOS (released in 2017) have any version of python3 available with the default system. On the other hand, TTBOMK, every system that does have python3 available also makes python2.7 also easily available. LLVM is not a primarily python project, so keeping up with the latest features of the language, and

As mentioned in https://docs.python.org/3/using/unix.html#miscellaneous, for Python 3 the shebang line should be: #!/usr/bin/env python3 For Python 2 the shebang line should probably be: #!/usr/bin/env python2 but as Python 3 should never install its executable under the name "python", you could also let it stay at: #!/usr/bin/env python instead. -Dimitry > On 1 Feb 2018, at

On 12/04/2012 12:28 AM, Sean Silva wrote: > On Mon, Dec 3, 2012 at 6:56 AM, Tobias Grosser<tobias at grosser.es> wrote: >> The gcc compile farm currently only has python 2.4 and 2.5. I know Duncan is >> using it quiet extensively, especially all dragonegg buildbots run on it. >> >> I very much agree we should ensure our python scripts are valid python 2.7 >>

Hi, I intend to upgrade our Samba AD DC from 4.9 to 4.10 on a CentOS 7 server . On the Wiki page : https://wiki.samba.org/index.php/Package_Dependencies_Required_to_Build_Samba#Manually_maintained_Distribution-specific_Package_lists <https://wiki.samba.org/index.php/Package_Dependencies_Required_to_Build_Samba> the yum command that lists all needed packages includes python3 for RHEL 8 /