search for: 4.11.1

Hi everyone, In case anyone's interested, I've posted some rpm builds of samba 4.11.1 for RHEL/Centos 7.x (currently 7.7). The samba 4.11.1 SPEC file is closely based on the Fedora Samba 4.11.1 SPEC file with some additions for using Samba as an AD/DC. These rpms use the python3 and python3-devel rpms introduced in the standard RHEL/Centos repos at the same time as the 7.7 version.

CentOS Errata and Security Advisory 2014:1976 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1976.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 42d0d9d8c43646be6bb73af2645e7e7d00613ffbd7281a167e938e13254d838d rpm-4.11.1-18.el7_0.x86_64.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

On Thu, Oct 24, 2019 at 12:43 PM Vincent S. Cojot via samba <samba at lists.samba.org> wrote: > > > Hi everyone, > > In case anyone's interested, I've posted some rpm builds of samba 4.11.1 > for RHEL/Centos 7.x (currently 7.7). The samba 4.11.1 SPEC file is closely > based on the Fedora Samba 4.11.1 SPEC file with some additions for using > Samba as an AD/DC.

Hai, My plan was to release the all of the coming builds of 4.11.1 today.. But... There are still processes building.. So whats new, what is there and what is not there. The 4.11.1 is based on the Debian Testing 4.11.0. My changes. * d/control changes: - Package samba, added acl to Recommends, obligated for member and AD-DC's. - re-enabled trackers to allow spotlight to

Hai, Ive just uploaded a new build. samba_4.11.1-0.1~buster~2 Changes: samba (2:4.11.1-0.1~buster~2) buster; urgency=medium . * d/control, samba-common-bin: added python3-markdown as needed package - fixes:samba-tool schemaupgrade to Windows ServerR2 does not work. ! Thank Dirk S. for reporting that! ----------- THE REPO SETUP --------------- - Import my key. wget -O -

======================================================== Arthur Spooner: "Darling, I need to borrow the iron." Carrie Spooner Heffernan: "Dad, I told you. If you want a grilled cheese sandwich, I will make you one." King of Queens ======================================================== Release Announcements --------------------- This is the

======================================================== Arthur Spooner: "Darling, I need to borrow the iron." Carrie Spooner Heffernan: "Dad, I told you. If you want a grilled cheese sandwich, I will make you one." King of Queens ======================================================== Release Announcements --------------------- This is the

I'm just dumping all I got in here, after initial feedback we can see how to organize todo's around it. tl;dr: * Does not upgrade cleanly from 4.8 packages, so we have to prevent this from entering testing until we fix that. * Live migration is broken, explodes with memory allocation errors. ---- >8 ---- 1. Build packages * I have built salsa/master using pbuilder targeting sid.

On Thu, 2019-10-24 at 21:38 -0400, Vincent S. Cojot via samba wrote: > On Thu, 24 Oct 2019, Nico Kadel-Garcia wrote: > > > You do realize I've been publishing .spec files and build tools for > > all of this for a while now, with hooks to build for CentOS 7, 8, > > and > > Fedora 30 with full AD features enabled for a few years now? My > > source > >

On Fri, 25 Oct 2019, S?rgio Basto wrote: > Hello, count with me, "my" project [1] , I have sync my spec from Nico > repo, I think the biggest difference is I'm using all internal > libraries ... Hi Sergio and Nico, I revisited nico's SPEC main samba 4.11 SPEC file last night to see if I had missed much and found huge similarities (we must have have forked

Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 05 Oct 2018 19:38:52 +0100 Source: xen Binary: xenstore-utils xen-utils-common xen-hypervisor-common xen-doc xen-utils-4.11 xen-hypervisor-4.11-amd64 xen-system-amd64 xen-hypervisor-4.11-arm64 xen-system-arm64 xen-hypervisor-4.11-armhf xen-system-armhf libxen-dev libxenmisc4.11 libxencall1 libxendevicemodel1

I have now finished totally rewriting the Xen package in Debian, from scratch. Amazingly as soon as I got a package which was lintian-clean and would install, it worked first time ! I have generated 18 patches to go upstream which I have sent to xen-devel. There are two more, xenstore ABI patches, which need a bit of tidying up. There is still room for improvement but it is now clearly ready

Hello, We have setup ctdb+Samba v 4.11.1 and testing with Windows client and failover works mostly ok. However when using regular Windows file copy, the copy operation is interrupted during ip takeover. Is there any solution to make the failover transparent to Windows file copy ? I understand that SMB2 durable handles should not be used in a clustered setup, and SMB3 persistent handles +

On Thu, 24 Oct 2019, Nico Kadel-Garcia wrote: > You do realize I've been publishing .spec files and build tools for > all of this for a while now, with hooks to build for CentOS 7, 8, and > Fedora 30 with full AD features enabled for a few years now? My source > repo is over at https://github.com/nkadel/samba4repo . Yes, I am aware of your efforts. Your project is much more

reassign 768005 src:xen 4.11.1-1 thanks Hi, I was browsing the bash-completion package bug list before filing a bug to remove the obsolete 'xm' file, and then I ran into this one. Reassigning to Debian Xen team, since I that makes more sense. We totally missed this on our (release) radar. And indeed, we're shipping the upstream completion file now. Adi, I see how you're

Package: xen-utils-4.11 Severity: important Dear Maintainer, We have discovered that the `pygrub` binaries, expected under `/usr/lib/xen-4.11/bin`, are no longer present in the xen-utils-4.11 package. Reviewing the source package reveals that the binary is still present under `tools/pygrub/src/pygrub`, however it is not referenced anywhere obvious in the package build configurations, nor is

This is awesome! What needs to be done before this can make it to unstable? I’d love to help if there’s anything I can do. Stephen On Fri, Oct 5, 2018 at 8:00 PM Hans van Kranenburg <hans at knorrie.org> wrote: > On 10/05/2018 08:04 PM, Ian Jackson wrote: > > I have now finished totally rewriting the Xen package in Debian, from > > scratch. Amazingly as soon as I got a

Package: xen Version: 4.8.0-1 Severity: important Starting with 4.8 the xen-hypervisor-4.8* package will contain a grub config file in /etc/default/grub.d/xen.cfg. This will be causing problem when moving to Xen 4.9 because then xen-hypervisor-4.9* will try to install the same file again. This will prevent two versions of the hypervisor to be co-installable. Maybe the solution would be to have a

Package: xen-utils-4.4 Severity: normal Dear Maintainer, the xen-utils-4.4 and xen-utils-4.1 prerm maintainer scripts contain the following code snippet: remove|upgrade) update-alternatives --remove xen-default /usr/lib/xen-4.4 if [ -x "/etc/init.d/xen" ]; then invoke-rc.d xen stop || exit $? fi ;; which, in conjunction with the postinst