Hi,

Sorry for taking so long to fix this :-/
Details follow below.

Olaf Meeuwissen <olaf@???> writes:

> Hi,
>
> Simon Josefsson <simon@???> writes:
>
>> wirelessduck@??? writes:
>>
>>> This is a known issue. I haven’t yet found the cause of the incorrect
>>> permissions.
>>
>> Thanks for the pointer -- my workaround in .gitlab-ci.yml was simple:
>>
>> - ls -ald /usr/sbin | grep -q ^drwxr-xr-x || chmod -v 755 /usr/sbin
>>
>> Maybe this helps others meanwhile. I think the official images should
>> have this chmod applied to them, as a post-processing step, until we
>> identify (and fix) the real bug causing this to happen is.
>
> Additional feedback provided on the issue[1] reported by wirelessduck
> suggests a more serious problem with filesystem permissions.
>
> [1]: https://git.devuan.org/paddy-hack/container-images/issues/67
>
> I have rather little time to look into this at the moment and will be
> travelling until the end of the month but I'll see what I can do.
> Please use the issue for follow-up or if just curious about progress.

I have confirmed that all devuan/devuan:*-2025-12-03 container images
now have correct permissions.

As of writing, all the non-timestamped tags point to the corresponding
2025-12-03 tags. Any container images built after that should have the
fix (and non-timestamped tags will be updated to point to those newly
build container images).

So, as of writing

  ceres-2025-12-03     -> ceres     -> unstable
  freia-2025-12-03     -> freia     -> testing
  excalibur-2025-12-03 -> excalibur -> stable       -> latest
  daedalus-2025-12-03  -> daedalus  -> oldstable
  chimaera-2025-12-03  -> chimaera  -> oldoldstable

Hope this helps,
--
Olaf Meeuwissen