Repository navigation
revert: stop packaging dbdoctor - #115
Merged
Merged
Conversation
The DB Doctor check engine now lives in serverinfo (nextcloud/serverinfo#1123), which these builds already package, so building dbdoctor on its own would put the same code in the tarball twice. This reverts #112. The legacy release script loses the same entries in nextcloud-gmbh/release-script, branch enh/unship-dbdoctor. Assisted-by: ClaudeCode:claude-opus-5 Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
blizzz
approved these changes
Sep 9, 2026
AndyScherzinger
approved these changes
Sep 9, 2026
Contributor
|
/backport to stable35 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The DB Doctor check engine moved into serverinfo (nextcloud/serverinfo#1123, stable35 backport in nextcloud/serverinfo#1130), and serverinfo is already in both configs, so building dbdoctor on its own would put the same code in the tarball twice.
This reverts #112, dropping the entry from
master.jsonandstable35.json:{ "id": "dbdoctor", "repo": "nextcloud/dbdoctor", "composer_args": "--no-dev -a --quiet" },The legacy script loses the same entries in nextcloud-gmbh/release-script#356, and nextcloud/server#64157 drops the app from
core/shipped.json.nextcloud/dbdoctorstays alive as a standalone appstore app, this only stops it being packaged.Both files still parse and still list 25 apps each after the removal. I have not run a build against either config.
👾 This pull request was assisted by Claude Code, commits carry an
Assisted-bytrailer.