On 2023-05-23 3:04 a.m., Michael Tokarev wrote:
At this point I don't plan to push new samba release to debian. Next
upstream 4.17 is planned - I guess now when the issue is rehashed by
you, next stable upstream release will include the fix. I definitely
plan to push this to bookworm, hopefully
Package: samba
Version: 2:4.17.8+dfsg-1
Severity: important
X-Debbugs-Cc: stevem...@gmail.com
Dear Maintainer,
Using samba 4.17.8 with bind_dlz DNS backend. A new DC is joined to an
existing domain with a single 4.17.8 DC.
When samba_dnsupdate runs on the newly joined DC, it causes the loca
On 2023-04-29 9:04 p.m., Richard Laager wrote:
Quick approach is try this:
python3 waf configure ...
python3 waf build
I tried this, but the bundled 'waf' tool did not work in Python3. I
could not get past the 'configure' step. Here's the output I got on a
Bookworm host with all the ntpsec bu
On 2023-04-28 10:20 p.m., Richard Laager wrote:
Can you confirm whether you get either of these messages to stderr on
startup:
A) MS-SNTP signd operations currently block ntpd degrading service to
all clients.
Definitely this one, A.
Is there any chance you could test with ntpsec 1.1.3? You
Package: ntpsec
Version: 1.2.2+dfsg1-1
Severity: normal
X-Debbugs-Cc: stevem...@gmail.com
Dear Maintainer,
On my LAN, I run Samba on Debian servers to implement Domain
Controllers (DCs) for an Active Directory (AD) domain. Per the Samba
documentation, I have set up authenticated time service (kn
Package: libosinfo-bin
Version: 1.4.0-1
Severity: normal
Dear Maintainer,
When I run the following on the command line:
osinfo-query os | grep -i buster | sed 's/ */ /g'
there is no output.
I would expect to see a line that is analagous to the output
obtained for every previous Debian st
Thanks, Eduard, for the swift reply. It turns out that a recent change
to the /etc/hosts.allow was blocking access from localhost ([::1]/128),
which the daily cron script (specifically the 'acngtool') needs to work.
My bad. Sorry for the noise.
Please close this bug.
Thanks again,
-S.M.
Package: apt-cacher-ng
Version: 3.2-2
Severity: normal
Dear Maintainer,
I am running apt-cacher-ng on buster. Fairly recently, I began to receive
daily emails from cron with the following body:
/etc/cron.daily/apt-cacher-ng:
Error: cannot fetch
http://localhost:3142/acng-report.html?doExpire=S
Package: live-config
Version: 5.20190415
Severity: normal
Dear Maintainer,
When the package 'libnss-systemd' is included in a debian-live image,
all attempts to boot the image fail, hanging forever at a particular
point in the boot process. The following message appears in the
console (all on one
The latest version of bind9 (1:9.11.5.P4+dfsg-4) still has a problem with its
apparmor profile with respect to the samba BIND9_DLZ use-case. I have submitted
a new bug to address it specifically: https://bugs.debian.org/928398
-S.M.
Package: bind9
Version: 1:9.11.5.P4+dfsg-4
Severity: normal
Dear Maintainer,
I have been testing samba4 and bind9 as an active directory (AD)
controller, specifically using the "BIND9_DLZ" DNS backend.
I am currently running apparmor (as is the default for buster), and I
have
placed the 'usr.
Steven Monai writes:
>My testing continues with the 'usr.sbin.named' profile in 'complain' mode. I
>will continue to report back here with my findings.
Since my last report, my two test servers, still in "complain" mode, have not
"complained"
On Wed, 28 Jun 2017 02:16:47 + JimmyZ wrote:
> Package: debian-live
> Version: 9.0.1
> Severity: normal
>
> It's really glad to see debian-live supports loopback.cfg now, however, two
> minor issues prevented it from working:
>
> # /boot/grub/loopback.cfg:
> source /grub/grub.cfg
> # should
Steven Monai writes:
>Okay. I have installed the latest bind9 from unstable (1:9.11.5.P4+dfsg-3),
>and have purged my local changes to the 'local/usr.sbin.named' apparmor file.
I neglected to mention that I made the same changes to both of my test domain
controllers, which are
Bernhard Schmidt writes:
>I have just uploaded 1:9.11.5.P4+dfsg-3 that should incorporate all your
>local changes and also allowed /dev/urandom. I have upgraded my local
>Samba AD DC to Buster with this configuration and it appears to work
>fine, but this is only my personal server.
>
>The package
Bernhard Schmidt writes:
>Any more warnings you experienced?
I'm glad you asked. Since my last message, I have been getting the following
three logs every two or three days:
Apr 11 00:49:41 dc1 kernel: [489173.713080] audit: type=1400
audit(1554968981.353:17): apparmor="ALLOWED" operation="mkn
Steven Monai writes:
>So far, my buster Samba AD controller appears to be working correctly with the
>'usr.sbin.named' profile in 'complain' mode. I will monitor the logs for a
>while to see if any further apparmor-related issues appear during my testing.
Some
Hello Bernhard. Thank you for your time.
Bernhard Schmidt writes:
>
>Have you configured /var/lib/samba/bind-dns/named.conf manually by any
>
>chance? On my stretch system this file is in /var/lib/samba/private,
>
>which is whitelisted based on the reports in this bug in the apparmor
>
>polic
Greetings.
As of now, this bug still affects Buster.
I have installed samba (2:4.9.4+dfsg-4), bind9 (1:9.11.5.P4+dfsg-1), and
apparmor (2.13.2-9).
In my testing environment, Samba is configured as an Active Directory
controller, and it is using the BIND_DLZ backend for DNS.
When the apparmor
On Thu, 27 Dec 2018 13:55:36 + Michael Biebl wrote:
> Source: systemd
> Source-Version: 240-2
>
> We believe that the bug you reported is fixed in the latest version of
> systemd, which is due to be installed in the Debian FTP archive.
I confirm that udev 240-2 fixes the problem of my root L
On 2018-12-24 7:09 a.m., Rafał Olejnik wrote:
> On Mon, 24 Dec 2018 13:34:40 +0800 John Wong wrote:
>> On 12/24/18 12:58 PM, John Wong wrote:
>> > Yes, udev 240-1 break my lvm2 system.
>> >
>> Hi, replace /lib/systemd/systemd-udevd with udev version 239's
>> (/lib/systemd/systemd-udevd), then upda
On Thu, 30 Nov 2017 12:23:06 +0100 Narcis Garcia
wrote:
> Where to start?
> https://lists.debian.org/debian-cd/2017/06/msg00062.html
In the interest of trying to move this forward, I have submitted a merge
request to the 'live-tasks' repo on salsa:
https://salsa.debian.org/live-team/live-tasks/m
On Sat, 8 Sep 2018 13:04:57 -0400 Austin Roach wrote:
...
> After the kernel upgrade to 4.18 in unstable, attempts to start a VM
> fail with messages like:
...
I am also affected by this bug.
Attempting to start a VM via the virsh tool results in the following:
steve@sid:~$ virsh start jessier
On 17-01-02 04:04 AM, Eduard Bloch wrote:
> * Steven Monai [Sun, Jan 01 2017, 12:59:22PM]:
>> I wanted to try downgrading to the previous version of the package,
>> but it appears that the sid version recently migrated to stretch,
>> and so I can only find the jessie and jess
Package: broadcom-sta-dkms
Version: 6.30.223.271-5
Severity: important
Dear Maintainer,
I am reporting essentially the same issue as in the recently-closed bug
#849034.
After upgrading to latest version of broadcom-sta-dkms, wifi connections
no longer work on my Dell Latitude E5520, running up-t
On Wed, 29 Apr 2015 02:57:28 -0400 Matthew Dawson
wrote:
> On Sun, 15 Jun 2014 01:20:41 +0200 Christoph Anton Mitterer
>>
>> Since openssh-server comes with systemd support, whenever a host
>> is shut down or restarted, ssh connections to that host just
>> hang and are no longer cleanly terminat
As I hinted in my original bug report, the MapServer community has
long maintained that the PHP/MapScript extension is most stable when
PHP is configured to run in CGI mode. I have a link to the MapServer
Wiki that very clearly corroborates this. See here:
http://mapserver.gis.umn.edu/cgi-bin/wiki
Package: php5-mapscript
Version: 5.0.0-2
The PHP5 MapScript extension (from the UMN MapServer project) does not
work when PHP5 is running in either CGI/FCGI or CLI modes. For
example, when trying to use the MapScript extension in a PHP5 script
run from the command line, the following error message
28 matches
Mail list logo
