debian 13 installer fixes - #7
Open
AZLyyds wants to merge 3 commits into
Open
Conversation
install.sh looks for packaging/fossilsafe.service and aborts if it is missing. Also create /mnt/fossilsafe paths up front so ProtectSystem=strict does not fail with NAMESPACE errors. Signed-off-by: AZLyyds <2773638053@qq.com>
Pull in npm, pick libfuse3-3 or libfuse3-4 from apt, and copy packaging/ plus fsafe-cli.py when using rsync. Point install-service.sh at the repo-root packaging template. Signed-off-by: AZLyyds <2773638053@qq.com>
tsc -b fails on unused Link/React imports during npm run build. Signed-off-by: AZLyyds <2773638053@qq.com>
|
Hi not sure if I'm doing something wrong or not but I've been pulling my hair out trying to get literally any fork of this to actually work and your fork has gotten the farthest in so far on debian 13 So far the installer gets to step 10 of 12 on consistently gives a namespace error 
I'm also seeing some syntax errors that could likely be the issue but I know to little about coding to find them let alone fix them would it be possible to update the code to fix these errors or guide me through how to fix them myself? 
|
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
2 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.
Hit a bunch of installer failures on Debian 13 while trying to get FossilSafe running. Looks like the same stuff people mentioned in #3.
What broke for me:
no packaging/fossilsafe.service, so install died when it tried to write the systemd unit
libfuse3-3 is gone on trixie (it's libfuse3-4 now), and npm wasn't in the package list
rsync install path skipped packaging/ and fsafe-cli.py
UI build failed on unused imports (tsc TS6133)
service wouldn't start (NAMESPACE) because /mnt/fossilsafe didn't exist under ProtectSystem=strict
After these changes, install finished on my Debian 13 box, fossilsafe stays active, and the web UI loads over https. I don't have tape hardware so I only checked install + basic health.
Happy to tweak anything if I missed a corner case.
Tested
Debian 13: sudo ./scripts/install.sh --yes
systemctl is-active fossilsafe → active
curl http://127.0.0.1:5000/api/healthz → ok
frontend npm run build no longer hits those unused-import errors