Releases: dionysius/seafile-deb
Releases · dionysius/seafile-deb
Release list
debian/13.0.25-1_beta1
Immutable
release. Only release title and notes can be modified.
- Drop upstream's unused seafile-admin and parse_seahub_db.py, ship no bytecode or eslint config, clear exec bits on non-scripts, no ldconfig trigger for the venv
- Lintian overrides: match both trixie's and resolute's lintian, cover the vendored venv and frontend, seafile.target
- Ship no build-only files: collectstatic sources, translation sources, test suites, the uv project, upstream's install scripts and wsgidav samples
- One THIRD-PARTY-LICENSES.txt.gz per package, add the frontend's npm packages to seafile-server-data
debian/13.0.25-1_alpha12
Immutable
release. Only release title and notes can be modified.
[ wdclub ]
- Add seafdav.service: WebDAV is shipped but nothing started it
[ dionysius ]
- seafdav: serve the private /var/tmp as the placeholder root, skip wsgidav.yaml, note seafdav for data relocation, align comments
- seaf-dbctl: source seafile.env itself, so a direct invocation uses the configured database host and credentials
- Rename seafile.service to seafile-server.service, bundle the server units in seafile.target
- Carry seafile.service's enabled and running state over to seafile-server.service on upgrade, move the bundled units' links to seafile.target
- CI: manage the stack through seafile.target, check it is enabled and active
- README: align with the other packaging repos, leave the setup details to the wiki
- Order the bundled units after seafile.target, so stopping it returns once they are stopped
debian/13.0.25-1_alpha11
Immutable
release. Only release title and notes can be modified.
- admin-tools-check: stop and restart the whole stack, seaf-gc refuses while the fileserver runs
- Manage seahub's schema with upstream's sql like its installer and docker image do, instead of django migrations
- Create seafevents' tables in seahub-migrate (seahub writes into them before seafevents' first start); tests start and check the whole stack
- Serve shipped seahub media from /usr, avatars and custom branding from SEAHUB_DATA_DIR, assets and thumbnails from /var/cache
- Stamp SEAFILE_VERSION into seahub's settings at build, as upstream's release build does
- Ship the collected assets in the package and serve the default avatars from the install tree; seahub-migrate is down to manage.py migrate
- Units: prune comments, update the suggested limits, provision only the state root, drop ENABLE_SEAFEVENTS in favour of systemctl
- seahub: make createsuperuser honour --password, so seahub-reset-admin --noinput creates an account that can log in
- Ship tested nginx, Caddy and Apache reverse proxy examples, suggest the three, hint at Before= ordering in the proxied units
- CI: run the stack through the shipped nginx example (login, assets, transfer, thumbnail, websocket)
- Patches: reference the upstream PR for the createsuperuser and reset-admin argument fixes
debian/13.0.25-1_alpha8
Immutable
release. Only release title and notes can be modified.
- rework db migration: refuse unstamped data, replace seafile-db-upgrade with seafile-db-tool
- Inline the reason for seafile-db-tool's tolerant SQL error handling
- Stop shipping upstream's manual-install scripts, patch the admin tools worth keeping
- Rename seafile-db-tool to seaf-dbctl, move version/stamp ownership into it
- Add seafevents.service for background tasks (email, indexing, auto-expiry)
- seafobj: defer the pylibmc import so seafevents actually starts
- Add django-pylibmc so seahub's CACHE_PROVIDER=memcached actually works
- Add libmemcached-dev: uv still builds pylibmc from source to satisfy django-pylibmc's own dependency, even though it's discarded afterward
debian/13.0.25-1_alpha6
Immutable
release. Only release title and notes can be modified.
- add seahub dir to seafile.env
- rename units to a seafile- prefix (core: seafile, seahub keeps its name), decouple units via Wants (no stop/restart cascade)
- drop whitenoise, static assets are served by seahub's SERVE_STATIC default
- mysql-only backend, migrate gates the stack until credentials are configured
- enable the go fileserver and notification server by default, units gate on their seafile.env toggle
- drop SERVICE_URL glue (upstream derives it from the environment), fix references stale since the seahub merge
- pass REMOTE_USER through gunicorn like upstream's generated config
- workers and threads set in gunicorn.conf like upstream, drop the env hook
- fix dead documentation references
- drop the /etc/default layer and env vars nothing reads, migrate scripts own their environment
- config templates document the full option surface, notification server binds localhost, seahub logs to the journal
- connection and process limit defaults sized per service, LimitNOFILE only where fd counts scale
- dh_ucf owns ucf registration and purge, postinst only adds the --three-way pass
- secrets are set by the admin instead of generated, migrate gates on all of them
- dpkg removes /etc/seafile on purge itself, the generated postrm suffices
- neutral "Other options" section naming in the config templates
- seafile.conf notes which file server reads single-implementation options
- unit comments stay service-agnostic so the units diff cleanly
- seaf-fuse mounts at its state directory, fuse options are a unit directive
- data dir configured once in seafile.env, fixed unit paths use specifiers
- version stamp lives in the data dir like upstream docker deployments
- seahub predefined environment as a section in seafile.env
debian/13.0.25-1_alpha3
Immutable
release. Only release title and notes can be modified.
- debian: compute daemon and venv-wheel shlibdeps in one run
debian/13.0.25-1_alpha1
Immutable
release. Only release title and notes can be modified.
- Initial packaging of Seafile Community Edition server (v13), built from
source without docker - single source package with seafile-server as the main upstream; libsearpc,
libevhtp, seahub, seafobj, seafdav and seafevents are pulled in by tag as
upstream components and compiled together - produces seafile-server (daemons), seahub (Django web frontend, python via
uv), libsearpc (RPC library) and the seafile metapackage - SQLite backend by default, MySQL/MariaDB backend supported
- NOT CRITICALLY AUTHORED, EVERYTHING CAN CHANGE, STEPS STILL REQUIRE
GOOD THOUGHT FOR PLANNED COMPATIBILITY/MAINTENANCE FLOWS