[PR #7336] Pin Debian MariaDB client library snapshot #27490

New Issue

Open

opened 2026-06-15 14:47:55 -05:00 by GiteaMirror · 0 comments

GiteaMirror commented 2026-06-15 14:47:55 -05:00

Owner

Copy Link

📋 Pull Request Information

Original PR: https://github.com/dani-garcia/vaultwarden/pull/7336
Author: @maxpetrusenkoagent
Created: 6/15/2026
Status: 🔄 Open

Base: main ← Head: hermes/oss-pr-2026-06-15-vaultwarden-7268

---

📝 Commits (1)

• dc82ad6 Pin Debian MariaDB client library

📊 Changes

2 files changed (+39 additions, -1 deletions)

View changed files

📝 docker/Dockerfile.debian (+19 -0)
📝 docker/Dockerfile.j2 (+20 -1)

📄 Description

Summary

• pin Debian image builds to the 2025-07-07 Debian Trixie snapshot for libmariadb*/mariadb*
• apply the same pin in the runtime image so the shipped Debian image uses the known-good MariaDB Connector/C package set
• keep the generated Dockerfile.debian in sync with Dockerfile.j2

Context

Recent MariaDB Connector/C releases can make Diesel misread result sets. In #7268 this shows up as Diesel not seeing existing __diesel_schema_migrations rows, then replaying migrations and failing on duplicate columns. This is the same class of MariaDB client-library issue previously tracked in #6416.

The pinned snapshot contains libmariadb3/libmariadb-dev 1:11.8.1-4; current Trixie provides 1:11.8.6-0+deb13u1.

Refs #6416
Refs #7268

Verification

• git diff --check
• static check that both docker/Dockerfile.j2 and generated docker/Dockerfile.debian contain the snapshot pin and #7268 reference
• checked Debian snapshot package metadata for libmariadb3, libmariadb-dev, and libmariadb-dev-compat at 1:11.8.1-4

Note: make -C docker could not run in this local environment because Python modules yaml/jinja2 are not installed, so Dockerfile.debian was updated to match the template change manually.

---

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/dani-garcia/vaultwarden/pull/7336 **Author:** [@maxpetrusenkoagent](https://github.com/maxpetrusenkoagent) **Created:** 6/15/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `hermes/oss-pr-2026-06-15-vaultwarden-7268` --- ### 📝 Commits (1) - [`dc82ad6`](https://github.com/dani-garcia/vaultwarden/commit/dc82ad6d6cb0d8e8e350fa330045162b835c12d0) Pin Debian MariaDB client library ### 📊 Changes **2 files changed** (+39 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `docker/Dockerfile.debian` (+19 -0) 📝 `docker/Dockerfile.j2` (+20 -1) </details> ### 📄 Description ## Summary - pin Debian image builds to the 2025-07-07 Debian Trixie snapshot for `libmariadb*`/`mariadb*` - apply the same pin in the runtime image so the shipped Debian image uses the known-good MariaDB Connector/C package set - keep the generated `Dockerfile.debian` in sync with `Dockerfile.j2` ## Context Recent MariaDB Connector/C releases can make Diesel misread result sets. In #7268 this shows up as Diesel not seeing existing `__diesel_schema_migrations` rows, then replaying migrations and failing on duplicate columns. This is the same class of MariaDB client-library issue previously tracked in #6416. The pinned snapshot contains `libmariadb3`/`libmariadb-dev` `1:11.8.1-4`; current Trixie provides `1:11.8.6-0+deb13u1`. Refs #6416 Refs #7268 ## Verification - `git diff --check` - static check that both `docker/Dockerfile.j2` and generated `docker/Dockerfile.debian` contain the snapshot pin and #7268 reference - checked Debian snapshot package metadata for `libmariadb3`, `libmariadb-dev`, and `libmariadb-dev-compat` at `1:11.8.1-4` Note: `make -C docker` could not run in this local environment because Python modules `yaml`/`jinja2` are not installed, so `Dockerfile.debian` was updated to match the template change manually. --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

GiteaMirror added the pull-request label 2026-06-15 14:47:55 -05:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

revert-7033-patch-1

cached-config-operations

test_dylint

1.36.0

1.35.8

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

wontfix

No Label pull-request

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/vaultwarden#27490