> On 19 Apr 2023, at 15:44, Johannes Kastl <kastl@b1-systems.de> wrote:
>
> Hi William,
>
> On 19.04.23 at 01:19 William Brown wrote:
>
>> The docker.com images are maintained by myself at SUSE. Because of how we
>> build them from https://build.opensuse.org/ and via
>> https://registry.opensuse.org/ we can't actually "patch" 2.2 and 2.1, so we
>> really only have latest. Hindsight is perfect I guess ....
>
> Hmmm.
>
>> I've also been really busy lately with other projects which probably hasn't
>> helped me keep things "up to date" as they should be either.
>
> I know what you mean...
>
>> As well, worth pointing out that 389-ds does not support *downgrades*. only
>> upgrades. So downpatching may/may not always work.
>
> Is that also true for patch releases? 2.2.6 to 2.2.5?
Generally for patch releases it's okay to downgrade. But 2.2 -> 2.3 would be a one-way change.
>
> I'd be happy to take that risk, and take snapshots/backups before larger upgrades. But without proper tags, that's not possible at all.
>
> Let's see what Viktor comes up with in quay.io.
>
Yep I've followed up with Viktor on some of the github issues so lets key the docker conversation about image tag and maintenance there.
--
Sincerely,
William Brown
Senior Software Engineer,
Identity and Access Management
SUSE Labs, Australia
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
No comments:
Post a Comment