packages, this can create issues down the road if one is not
expericenced in Debian packaging quirks. (renaming src:passage also
breaks it's history in Debian tooling…)
It would be much cleaner to have a new name for the new package,
both binary and source.
Looking at passage:
Would it be a possiblity to see if the support for age could be
implemented in pass, the project passage forked from? This seems to
be the only difference, especially as upstream of passage doesn't look
quite active, last commit 1 year ago, and there are unanswered issues
and pull requests as well -- I fear it's development might have stalled
upstream, making the case for taking over the name "passage" weaker.