similar to: my debian/ubuntu samba packages: update to samba-ad-dc split

Thanks for your work, Michael!!! On Sat, Oct 26, 2024 at 8:04?AM Michael Tokarev via samba < samba at lists.samba.org> wrote: > Hi! > > A while back, with 4.20.1+dfsg-2 version (26 May 2024), > I split AD-DC functionality from samba package to a separate > samba-ad-dc package. Adding a NEWS entry for this, which > suggests to install samba-ad-dc package separately for

Hi Michael, thanks for your effort from me, too... By the way, have you planned to get the Bookworm backports up to 4.21.x? Regards Ingo https://github.com/WAdama Elias Pereira via samba schrieb am 26.10.2024 um 13:30: > Thanks for your work, Michael!!! > > On Sat, Oct 26, 2024 at 8:04?AM Michael Tokarev via samba < > samba at lists.samba.org> wrote: > >> Hi!

On 26.10.2024 16:37, Ingo Asche via samba wrote: > Hi Michael, > > thanks for your effort from me, too... Thank you for the support as well, it makes me feel excellent :) > By the way, have you planned to get the Bookworm backports up to 4.21.x? Yes, it is waiting for current 4.21.1+dfsg-2 to migrate to testing (with the fixes mentioned in this thread), and I'll push it to

Hi! I just uploaded binaries of samba versions 4.19.7-1 and 4.20.1-5 for ubuntu and debian to the usual location, http://www.corpit.ru/mjt/packages/samba/ . There are a few changes in there. First, I changed debian release suffix to be like: 4.20.1+dfsg-5~mjt-deb11 4.20.1+dfsg-5~mjt-ubt24 This should not change anything, just make it easier to track if neded, hopefully. And for 4.20

Hello mjt, I can only speak for myself: For bigger upgrades (e. g. samba 4.19 -> 4.20) Im manually updating a few servers and check if everything works. For smaller updates (e. g. 4.20.1 -> 4.20.2) Im using saltstack to automate updating the servers. It suppresses these messages and this is fine in 99% of all cases because a minor update is not supposed to change much (e. g. split a

04.07.2024 21:27, Paul Leiber via samba wrote: > Dear Samba list, > > I have a Samba instance running as an ad-dc on debian bullseye. Some time ago, I changed the standard installation to backports with > > apt -t bullseye-backports install samba > > After a recent update, samba-ad-dc service didn't start anymore. The journal gave the following hint: > > Jul 04

[Not including ellerhold.de address since the MXes in question does not accept connections form my part of the world] 05.07.2024 09:58, Matthias K?hne | Ellerhold Aktiengesellschaft via samba wrote: > Hello mjt, > > I can only speak for myself: > > For bigger upgrades (e. g. samba 4.19 -> 4.20) Im manually updating a > few servers and check if everything works. > >

Hi! I've uploaded samba packages for debian & ubuntu in my repository, to include the fix for recent login/trust issue with 07/2023 windows updates. 4.16 packages will also be available later today (build is in progress now). http://www.corpit.ru/mjt/packages/samba/ JFYI. Thanks, /mjt

Replying here as well, since this is a frequent question. I uploaded the updated samba packages to the official debian archives in parallel with updating my repository - exactly the same source packages as are used to build samba for my repository. 4.18 should already be available on sid/unstable, I think. In trixie/testing it will migrate within 5 days if nothing other breaks. Updated bookworm

First, thanks so much for doing this. I used Louis's packages previously and was in a quandary about what to do when those stopped getting updates. Having you fill that gap has been super nice. Thanks! ? Second. I'm on Ubuntu (22.04) I'm currently using your MJT repo. ? I note you list official debian repos that are part of the official debian system... And that would perhaps be better

On Wed, 2014-12-10 at 12:47 +0100, Fabio Fantoni wrote: > Thanks for your work on xen packages, I have some question about 4.5 > packages: > I saw a debian/rules that disable blktap2 but > debian/patches/tools-blktap2-prefix.diff is still present and used in > series, if blktap2 is now disable I think is nomore needed. Yes, this can probably go. > I saw also many other patches

Greetings all, I'm trying to create a CentOS 4.4 kickstart CD (not a network install), duplicating what I've done for Fedora Core 3. I am having a cirular dependency for initscripts, which causes initscripts not to be installed (no /etc/inittab when the boot gets to INIT) The cascade is: initscripts-7.39.25.EL-1.centos4 requires /sbin/nash /sbin/nash is in mkinitrd-4.2.1.8-1

We just made the updated packages available in the official debian bookworm archives, see https://lists.debian.org/debian-stable-announce/2023/07/msg00000.html (yes, it is exactly the same package as has been available from my repository, just built within debian infrastructure instead of my local). Thanks, /mjt

Dear Samba list, I have a Samba instance running as an ad-dc on debian bullseye. Some time ago, I changed the standard installation to backports with apt -t bullseye-backports install samba After a recent update, samba-ad-dc service didn't start anymore. The journal gave the following hint: Jul 04 20:05:37 xxx (samba)[5864]: samba-ad-dc.service: Failed at step EXEC spawning

On Fri, 7 Jun 2024 08:50:11 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > on the problematic DC "systemctl status" doesn't even show > "samba-ad-dc". > > Although: > > # systemctl status samba-ad-dc.service > ? samba-ad-dc.service - LSB: Samba daemons for the AD DC > Loaded: loaded

Michael, Maybe I can answer why so few are seeing the NEWS entries you created.? I checked all my Debian systems, and only one has apt-listchanges installed.? The systems were all done via a netinstall .iso.? I don't recall installing apt-listchanges on the one system, but I must have somewhere in time.? So, for any other individuals who installed the OS as I did, there is no NEWS

Hi, When I initially boot my system, it fails to bring up the network. Once booted, if I run "systemctl restart network.service", or even stop, wait a while, then start, it starts up fine and all is well. I'm running Fedora 19 (updated). I followed the instructions on this page to set up a bridged network: http://wiki.libvirt.org/page/Networking I note however that I did *not*

Hi, I have recently installed NUT 2.7.3.1 on a freshly installed Ubuntu 16.04 LTS (64-bit) system, connected via USB cable to APC Smart-UPS 1500 (SMT model). I am trying to make this configuration work for automatic shutdown/restart but it seems that it completely ignores /etc/killpower presence. I know the APC SMT models are problematic but it looks like I could not even make the simplest

I wanted to update to CentOS 4.3 from CentOS 4.2. While updating packages using yum, there was serveral error messages, and I've found that some packages has not been updated. So I tried to update again but the packages would not be updated. I attached the messages shown below. Sungsoo Kim ------------------------------------------- [root at phobos ~]# yum update Setting up Update Process

Am 07.06.24 um 08:45 schrieb Michael Tokarev: > Please check version of samba-ad-dc package, - is it the same as other > samba package versions? that package isn't installed according to "apt-cache policy" ! Seems it got lost while upgrading. > Did samba-ad-dc start at all? seemed like, but was very fast (so did nothing, as it seems) Did "apt install