similar to: [PATCH NOT WORKING nbdkit 0/3] python: Allow thread model to be set from Python plugins.

Hi, R has been built against FlexiBLAS in rawhide [1, 2]. These are the R packages that need to be rebuilt: R-ape-0:5.4-2.fc33.x86_64 R-expm-0:0.999.4-7.fc33.x86_64 R-gee-0:4.13.20-4.fc33.x86_64 R-gss-0:2.2.2-3.fc33.x86_64 R-igraph-0:1.2.5-3.fc33.x86_64 R-msm-0:1.6.8-5.fc33.x86_64 R-preprocessCore-0:1.50.0-4.fc33.x86_64 R-qtl-0:1.46.2-4.fc33.x86_64 R-quadprog-0:1.5.8-5.fc33.x86_64 Could

Hi, I'm hitting that issue since Mesa 20.0.6 and it is present still in latest version 20.1.7 ``` [tkloczko at barrel SPECS]$ coredumpctl gdb 3926866 PID: 3926866 (test_va_api) UID: 1000 (tkloczko) GID: 1000 (tkloczko) Signal: 11 (SEGV) Timestamp: Sun 2020-09-13 18:57:06 BST (32s ago) Command Line: ./test_va_api Executable:

On Fri, Oct 30, 2020 at 10:30:00AM +0800, Han Han wrote: > Hello, > I encountered errors when building rpm on fedora33: > > Versions: > libvirt: v6.9.0-rc2 > gcc-10.2.1-5.fc33.x86_64 > meson-0.55.3-1.fc33.noarch > ninja-build-1.10.1-2.fc33.x86_64 > binutils-2.35-11.fc33.x86_64 > > Steps: > 1. Archive libvirt source code to

I have two domain controller servers, with samba in version 4.18 On both DCs both the Sysvol share and the subdirectories (including GPOs) have the same permission: getfacl /usr/local/samba/var/lib/samba/sysvol # file: usr/local/samba/var/lib/samba/sysvol # owner: root # group: 3000000 user::rwx user:root:rwx user:3000000:rwx user:3000001:r-x user:3000002:rwx user:3000003:r-x group::rwx

Hello, I was hoping to reprovision the same domain by specifying the domain GUID in the command line tool 'samba-tool domain provision' but I am not sure if I missed something or if there is a bug but the specified domain GUID is not the one which is created for my domain. Specifying the domain SID seems to work as I would expect. I tested it with Samba shipped by Debian 11 (samba2

Hi! I executed the command "samba-tool ntacl sysvolcheck" on a DC and I got the following I pasted below. The first DC was provisioned migrating from a samba NT4 PDC with an LDAP backend using the classic upgrade procedure. I haven't detected any problem but I wanted to make sure there isn't any problem I might not be seeing yet. ERROR(<class

That's not a problem its just a ACL provisioning message as you can see the result was "DAG:DAD:PAI" but expected was "O:DAG:DAD:PAR" that's "normal" ;-) just ignore it or do a "samba-tool ntacl sysvolreset" Am 19.10.23 um 17:27 schrieb bd730c5053df9efb via samba: > Hi! > > I executed the command "samba-tool ntacl sysvolcheck"

On Mon, 16 Dec 2024 13:01:53 +0000 Peter Mittermayer via samba <samba at lists.samba.org> wrote: > While resuming my testing for adding a new DC with higher Samba > version I have some questions: > > 1. do I have to expunge tombstones on each DC or just one (and > replication will remove it from others). - I think it should be run > on all DCs. > > 2. same question

Greetings, This post pertains to Samba version 4.16.8 on FreeBSD 13.1. When GPMC.MSC is invoked from within a Windows server domain member, it displays an inconsistency error: <https://attachments.samba.org/attachment.cgi?id=8386> <https://bugzilla.samba.org/show_bug.cgi?id=14927> # samba-tool ntacl sysvolreset # samba-tool ntacl sysvolcheck ERROR(<class

Hello everybody, i tried "samba-tool domain backup online --server=dc01 --targetdir=/autofs/backup/linux/samba_dom/backup.tgz -U administrator" and got this error: ERROR(<class 'OSError'>): uncaught exception - [Errno 39] Directory not empty: 'sam.ldb.d' File "/usr/lib/python3/dist-packages/samba/netcmd/__init__.py", line 185, in _run

Now I just need to find a solution how to allow dyndns updates only for the DCs and not the clients. Reason for this is that all our servers have multiple interfaces. Although they are connecting to AD mostly via default route we have seen issues where some register with wrong interface thus creating incorrect DNS records.All the DNS records A & PTR are usually created automatically during

Full output: root at iob-master:~# samba-tool domain backup online --server=dc01 --targetdir=/autofs/backup/linux/samba_dom/$(hostname -d) -U administrator Password for [SAMBA\administrator]: INFO 2023-11-20 15:30:05,639 pid:73781 /usr/lib/python3/dist-packages/samba/join.py #1614: workgroup is SAMBA INFO 2023-11-20 15:30:05,640 pid:73781 /usr/lib/python3/dist-packages/samba/join.py #1617: realm

I see. Thanks for clarification. Checking the detailed of using debuglevel 10 I see this message: ../../source4/dsdb/samdb/ldb_modules/repl_meta_data.c:5583: Resolving conflict record via existing-record rename 'CN=Vikas Rajan,CN=Users,DC=SUB,DC=DOM,DC=TLDbg' -> 'CN=Vikas Rajan\0ACNF:de5b7fa1-e3ec-4631-a8d7-cdfc137ac3b7,CN=Users,DC=SUB,DC=DOM,DC=TLD' Although it was renamed

Hello, I encountered errors when building rpm on fedora33: Versions: libvirt: v6.9.0-rc2 gcc-10.2.1-5.fc33.x86_64 meson-0.55.3-1.fc33.noarch ninja-build-1.10.1-2.fc33.x86_64 binutils-2.35-11.fc33.x86_64 Steps: 1. Archive libvirt source code to ~/rpmbuild/SOURCES/libvirt-6.9.0.tar.xz 2. Copy libvirt.spec.in to ~/rpmbuild/SPECS/libvirt.spec. Then `sed -i s/@VERSION@/6.9.0/g

On Sat, 7 Dec 2024 12:56:08 +0000 Peter Mittermayer via samba <samba at lists.samba.org> wrote: > > Hi, > > I'm trying to upgrade my very old samba domain controllers (4.11) to > latest samba. (4.21). The process I'm following is to demote on of > the existing DCs and repalce it with a news system (up-to-date OS & > samba version). Unfortunately when

Hi, I'm trying to upgrade my very old samba domain controllers (4.11) to latest samba. (4.21). The process I'm following is to demote on of the existing DCs and repalce it with a news system (up-to-date OS & samba version). Unfortunately when trying to join as DC I get below error: INFO 2024-12-05 19:29:42,222 pid:126140 /usr/local/samba/lib64/python3.9/site-packages/samba/join.py

$ libguestfs-test-tool ... libguestfs: launch: version=1.42.0fedora=33,release=5.fc33,libvirt ... libguestfs: build appliance libguestfs: error: cannot find any suitable libguestfs supermin, fixed or old-style appliance on LIBGUESTFS_PATH (search path: /usr/lib/guestfs) ... It appears that this configure test is now failing:

Hi, here are the versions: dc01: Raspberry Pi 3 Model B Rev 1.2 root at dc01:~# cat /etc/debian_version 11.8 root at dc01:~# samba -V Version 4.17.12-Debian root at dc01:~# uname -a Linux dc01 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux Dc02: Raspberry Pi 3 Model B Rev 1.2 root at dc02:~# cat /etc/debian_version 11.8 root at dc02:~# samba -V Version

On Mon, 20 Nov 2023 15:34:19 +0100 Dirk Laurenz via samba <samba at lists.samba.org> wrote: > Full output: > > root at iob-master:~# samba-tool domain backup online --server=dc01 > --targetdir=/autofs/backup/linux/samba_dom/$(hostname -d) -U > administrator Password for [SAMBA\administrator]: > INFO 2023-11-20 15:30:05,639 pid:73781 >

On Tue, Feb 14, 2023 at 08:02:59PM +0200, Yonatan Shtarkman wrote: > The attached code snippet?reproduces the issue when running: > python3 libugestfs_segfault_repro.py > > With: > guestfs version: 1.48.6 > guestfs-python version: 1.48.6 Can confirm with {python3-,}libguestfs-1.51.1-1.fc39.x86_64 The stack trace is roughly the same as yours. Rich. > Stacktrace: > #0