Skip to content

Rename to SecretSpace (1.0.0-alpha.2) - #17

Merged
usermaneGermane merged 2 commits into
mainfrom
rebrand-secretspace
Nov 9, 2026
Merged

usermaneGermane merged 2 commits into
mainfrom
rebrand-secretspace

Conversation

@usermaneGermane

Copy link
Copy Markdown
Owner

What

PassMan → SecretSpace (owner, 2026-11-09), version 1.0.0-alpha.2. This is the same rename as Windows #19.

Was Now
package passman secretspace
/usr/bin/passman, /usr/lib/passman /usr/bin/secretspace, /usr/lib/secretspace
passman.desktop, icon passman.png secretspace.desktop, secretspace.png
deb/passman.py deb/secretspace.py
window title, dialogs, README SecretSpace

Not renamed (as on Windows): the b"PassMan3 …" key-derivation strings, the DPAPI context, the file magics, the X-PassMan-* sync headers (the prod server reads them), PASSMAN_DATA_DIR, the test copy of the server, and "PassMan 2.x" in the import dialog.

Upgrading from passman

  • Package: Conflicts:, Replaces: and Provides: passman. apt install ./secretspace_…deb removes passman in the same step.

  • Data: vault.data_home uses ~/.local/share/secretspace, unless only ~/.local/share/passman exists; then that one is used. Nothing is moved.

  • New CI check:

    1. Install the real v0.9.0 passman release.
    2. Put a vault in ~/.local/share/passman.
    3. Upgrade to the new package.
    4. Assert that passman is gone, the vault is untouched, and the installed app's home is the passman folder.

    The fresh-install checks then run as before.

Checks

  • pytest (Windows run): 494 passed, 6 skipped. New tests:
    • the old folder is kept (and no empty new folder appears);
    • the new folder wins once it exists;
    • the control fields.
  • CI on Ubuntu 22.04 and 24.04 runs the real package, including the upgrade above.

After merge: tag v1.0.0-alpha.2, then a pre-release with the CI .deb.

🤖 Generated with Claude Code

https://claude.ai/code/session_011ojnyVg7ccsR3pZ64s7aRH

usermaneGermane and others added 2 commits November 9, 2026 22:27
Owner decision 2026-11-09: another password manager is already called
PassMan. Same rename as SecretSpace for Windows 3.0.0-alpha.2: every name
a user sees, the package (secretspace), the command (/usr/bin/secretspace),
/usr/lib/secretspace, secretspace.desktop and its icon, the launcher
deb/secretspace.py. Logo file renamed, image unchanged.

Not renamed, as on Windows: the b"PassMan3 ..." key-derivation strings, the
DPAPI context, the file magics, the X-PassMan-* sync headers,
PASSMAN_DATA_DIR, the test copy of the server, "PassMan 2.x" in the import
dialog.

Upgrade from the passman package: the control file says Conflicts,
Replaces and Provides passman, so apt installs secretspace and removes
passman in one step. Data: vault.data_home picks ~/.local/share/secretspace
unless only ~/.local/share/passman exists; nothing is moved. CI now
installs the real v0.9.0 passman release first, puts a vault in
~/.local/share/passman, upgrades to the new package and checks: passman is
gone, the vault is untouched, and the installed app's home is the passman
folder.

pytest 494 passed, 6 skipped (Windows run; CI runs it on Ubuntu 22.04 and
24.04 with the package).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ojnyVg7ccsR3pZ64s7aRH
passman_server.py is again an unchanged copy of the servers' file
(SecretSpace-Server-* #8: two display strings). The note names the renamed
repositories.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ojnyVg7ccsR3pZ64s7aRH
@usermaneGermane
usermaneGermane merged commit b0973f5 into main Nov 9, 2026
6 checks passed
@usermaneGermane
usermaneGermane deleted the rebrand-secretspace branch November 9, 2026 20:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant