Bug#994249: postgresql-client-common: vacuumlo erroneously complains about missing client package
Control: forwarded -1 https://salsa.debian.org/postgresql/postgresql/-/issues/1 Re: Matthew Gabeler-Lee > When only postgresql client package(s) are installed, the vacuumlo wrapper > erroneously reports: > > Error: You must install at least one postgresql-client- package > > Even though the client package(s) _are_ installed. This seems to be because > the underlying binaries are provided by the postgresql _server_ package(s). > > Which may also be a bug? The upstream documentation for the vacuumlo package > implies that it can be run as a client, it doesn't seem to need to be run > directly on/from the server system. Hi, that's a tricky one. Historically, vacuumlo used to be in the postgresql-contrib-XX package (and it still is in contrib/ in the source). The alternatives system is used to manage the (version-dependent) manpages, and contrib is part of the server package in that area. Now, when we merged the server and contrib packages we could not simply move the vacuumlo.1 manpage to the client package since update-alternatives doesn't allow "slave" links to be part of different master groups. If /usr/share/postgresql/9.6/man/man1/vacuumlo.1.gz is part of the postgresql-server group, /usr/share/postgresql/10/man/man1/vacuumlo.1.gz cannot move to the postgresql-client group. It's on the TODO list, but it's complicated. https://salsa.debian.org/postgresql/postgresql/-/issues/1 Christoph
Bug#994249: postgresql-client-common: vacuumlo erroneously complains about missing client package
Package: postgresql-client-common Version: 225 Severity: minor When only postgresql client package(s) are installed, the vacuumlo wrapper erroneously reports: Error: You must install at least one postgresql-client- package Even though the client package(s) _are_ installed. This seems to be because the underlying binaries are provided by the postgresql _server_ package(s). Which may also be a bug? The upstream documentation for the vacuumlo package implies that it can be run as a client, it doesn't seem to need to be run directly on/from the server system. -- System Information: Debian Release: 11.0 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'testing'), (500, 'oldstable'), (490, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages postgresql-client-common depends on: ii netbase 6.3 Versions of packages postgresql-client-common recommends: ii libreadline8 8.1-1 postgresql-client-common suggests no packages. -- no debconf information
