On Tue, Oct 06, 2026 at 05:14:09PM -0400, Paul Tagliamonte wrote:
debusine-server declares postgres as recommends. I installed as no
recommends (i'd like to have debusine use a remote postgres instance
-- having
a local psql is not required here), and fully expected it to fail on startup,
but it wound up failing on postinst instead.
```
Setting up debusine-server (0.16.0) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
debconf: unable to initialize frontend: Teletype
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Noninteractive
dbconfig-common: writing config to /etc/dbconfig-common/debusine-server.conf
Creating config file /etc/dbconfig-common/debusine-server.conf with new version
Creating config file /etc/debusine/server/db_postgresql.py with new version
chown: invalid user: 'postgres'
I think the chown comes from dbconfig-common. Isn't the problem here
that you're using the noninteractive frontend and don't have appropriate
preseeding for dbconfig-common's questions? Off the top of my head I'm
not sure exactly what the preseeding would need to be, but it probably
involves at least debusine-server/remote/host. I'd start by installing
debusine-server in a throwaway test environment with an interactive
debconf frontend and see what questions you need to answer to get it to
select a remote database.
--
Colin Watson (he/him) [[email protected]]
