starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-07-16 05:43:54 +03:00
Code Issues 822 Packages Projects Releases 17 Wiki Activity

[PR #13853] [MERGED] Fix backup not written to correct directory #13741

New Issue
Closed
opened 2026-02-07 07:18:23 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 07:18:23 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/13853
Author: @JPVenson
Created: 4/6/2025
Status: ✅ Merged
Merged: 4/7/2025
Merged by: @crobibero

Base: master ← Head: bugfix/FixBackupDirectory

📝 Commits (3)

  • e3bb23a Fix backup not written to correct directory
  • d4eff69 Improve restore handling and only restore on actual error
  • ae76f9f Fix first failed migration not causing a rollback

📊 Changes

2 files changed (+30 additions, -7 deletions)

View changed files

📝 Jellyfin.Server/Migrations/MigrationRunner.cs (+27 -6)
📝 src/Jellyfin.Database/Jellyfin.Database.Providers.Sqlite/SqliteDatabaseProvider.cs (+3 -1)

📄 Description

Fix backup only restored when actual errors with the database occure
Fix writing successfully performed migrations to the xml file

🔄 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/jellyfin/jellyfin/pull/13853 **Author:** [@JPVenson](https://github.com/JPVenson) **Created:** 4/6/2025 **Status:** ✅ Merged **Merged:** 4/7/2025 **Merged by:** [@crobibero](https://github.com/crobibero) **Base:** `master` ← **Head:** `bugfix/FixBackupDirectory` --- ### 📝 Commits (3) - [`e3bb23a`](https://github.com/jellyfin/jellyfin/commit/e3bb23abc076ff97a45f04ff56390f1f0b6a2562) Fix backup not written to correct directory - [`d4eff69`](https://github.com/jellyfin/jellyfin/commit/d4eff6985fd88b3ea2ccb2b9501f133fdc1ff33a) Improve restore handling and only restore on actual error - [`ae76f9f`](https://github.com/jellyfin/jellyfin/commit/ae76f9f622bdac9b6d3b29eddb5099a76b09c344) Fix first failed migration not causing a rollback ### 📊 Changes **2 files changed** (+30 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `Jellyfin.Server/Migrations/MigrationRunner.cs` (+27 -6) 📝 `src/Jellyfin.Database/Jellyfin.Database.Providers.Sqlite/SqliteDatabaseProvider.cs` (+3 -1) </details> ### 📄 Description Fix backup only restored when actual errors with the database occure Fix writing successfully performed migrations to the xml file --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 07:18:23 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#13741
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?