Skip to content

fix(setup): only resolve MySQL SSL attributes when an option is set - #64975

Merged
provokateurin merged 1 commit into
masterfrom
worktree-fix-mysql-setup-test-32bit
Oct 1, 2026
Merged

provokateurin merged 1 commit into
masterfrom
worktree-fix-mysql-setup-test-32bit

Conversation

@CarlSchwan

Copy link
Copy Markdown
Member

Summary

The PDO MySQL attributes only exist with the pdo_mysql extension, so resolving them unconditionally broke the MySQL setup without any encryption option when the extension is missing, e.g. in the 32-bit test environment.

TODO

  • ...

Checklist

AI (if applicable)

  • The content of this PR was partly or fully generated using AI

The PDO MySQL attributes only exist with the pdo_mysql extension, so
resolving them unconditionally broke the MySQL setup without any
encryption option when the extension is missing, e.g. in the 32-bit
test environment.

Assisted-by: ClaudeCode:claude-opus-5-5
Signed-off-by: Carl Schwan <carl@carlschwan.eu>
@CarlSchwan CarlSchwan added this to the Nextcloud 36 milestone Oct 1, 2026
@CarlSchwan
CarlSchwan requested a review from susnux October 1, 2026 07:34
@CarlSchwan CarlSchwan self-assigned this Oct 1, 2026
@CarlSchwan
CarlSchwan requested a review from a team as a code owner October 1, 2026 07:34
@CarlSchwan CarlSchwan added the bug label Oct 1, 2026
@CarlSchwan
CarlSchwan requested review from icewind1991 and removed request for a team October 1, 2026 07:34
@CarlSchwan CarlSchwan added the 3. to review Waiting for reviews label Oct 1, 2026
@provokateurin

Copy link
Copy Markdown
Member

/backport to stable35

@CarlSchwan

Copy link
Copy Markdown
Member Author

/backport to stable34

@CarlSchwan

Copy link
Copy Markdown
Member Author

/backport to stable33

@provokateurin
provokateurin merged commit ee0b6e9 into master Oct 1, 2026
207 checks passed
@provokateurin
provokateurin deleted the worktree-fix-mysql-setup-test-32bit branch October 1, 2026 10:33
@backportbot

backportbot Bot commented Oct 1, 2026

Copy link
Copy Markdown

The backport to stable33 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable33
git pull origin stable33

# Create the new backport branch
git checkout -b backport/64975/stable33

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick e299c08f

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/64975/stable33

Error: Failed to check for changes with origin/stable33: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

@backportbot

backportbot Bot commented Oct 1, 2026

Copy link
Copy Markdown

The backport to stable34 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable34
git pull origin stable34

# Create the new backport branch
git checkout -b backport/64975/stable34

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick e299c08f

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/64975/stable34

Error: Failed to check for changes with origin/stable34: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants