Devuan bug report logs - #575
postgresql-common packaging not handling Devuan version number

Package: postgresql-common; Maintainer for postgresql-common is (unknown); Source for postgresql-common is src:postgresql-common.

Reported by: Stephen Lyons <slysven@virginmedia.com>

Date: Sat, 17 Apr 2021 18:48:01 UTC

Severity: wishlist

Tags: debian

Found in version 200+deb10u4

Fixed in version 243

Full log

Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):

Received: (at submit) by bugs.devuan.org; 17 Apr 2021 18:40:03 +0000
Return-Path: <slysven@virginmedia.com>
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Sat, 17 Apr 2021 18:40:03 +0000 (UTC)
Received: from know-smtprelay-omc-11.server.virginmedia.net (know-smtprelay-omc-11.server.virginmedia.net [80.0.253.75])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id E6E4AF604B3
	for <submit@bugs.devuan.org>; Sat, 17 Apr 2021 20:34:56 +0200 (CEST)
Authentication-Results: vm6.ganeti.dyne.org;
	dkim=pass (2048-bit key; unprotected) header.d=virginmedia.com header.i=@virginmedia.com header.b="XPQ2XWbB";
	dkim-atps=neutral
Received: from [192.168.1.103] ([77.101.114.27])
	by cmsmtp with ESMTPA
	id XpmQlGVxkOvGxXpmQlmq1g; Sat, 17 Apr 2021 19:34:55 +0100
X-Originating-IP: [77.101.114.27]
X-Authenticated-User: slysven@virginmedia.com
X-Spam: 0
X-Authority: v=2.3 cv=RZUk9Glv c=1 sm=1 tr=0 cx=a_exe
 a=Lp89TJ372ekD+PueIMK5vQ==:117 a=Lp89TJ372ekD+PueIMK5vQ==:17
 a=r77TgQKjGQsHNAKrUKIA:9 a=qV6qeoQ_AAAA:8 a=T6ZAMzLjzzofN00Q6agA:9
 a=QEXdDO2ut3YA:10 a=KSb9T-wMAAAA:8 a=0waMV55F_q30gSo9Uw8A:9 a=m-Z_27IZkzAA:10
 a=NFiIfuRHoi4Aw3BdIEuW:22 a=KF4VuIdXkMyp4E_ug72i:22 a=Z5ABNNGmrOfJ6cZ5bIyy:22
 a=jd6J4Gguk5HxikPWLKER:22
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=virginmedia.com;
	s=meg.feb2017; t=1618684495;
	bh=lrP7mypPedLpUshVjI/czQ4EQEb/ewCDQSWpvanshk4=;
	h=To:From:Subject:Date;
	b=XPQ2XWbBrxIm73+iImAaFpwZDCjnp4aR88iAjz+Dd6PRRUYQlFI4rfkmL0F+lPSbY
	 B8IoAoGhLMP+e8RMNpEXC7LQHaI1HJhsbBWFSUo69XyDrHr3a7f5gLKEWVL4XK//6i
	 M/tAMs5UYer7eRwN6uBne2hgdAI3UC/SUexehaO14Z6JpodRyl4Qmhb7d9MZE1CzFb
	 RSnuR6QXNKJLWPOCo3PbuFm5uCV3nmXzqcdVAMtJagxWZULnKfZ4TJ9ylsX6vSz29c
	 RrmcSW1TZkUeOqHypnRIWWxU93W8+Bt/l9PM6lCAhgQU0FkFtCDRpT46Gaf3gsfWni
	 0B0j2wqFjD5Ng==
To: submit@bugs.devuan.org
From: Stephen Lyons <slysven@virginmedia.com>
Subject: postgresql-common packaging not handling Devuan version number
Message-ID: <42e7c218-75d3-fdec-ecba-52bb70d842a8@virginmedia.com>
Date: Sat, 17 Apr 2021 19:34:54 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary="------------ABC839664C638F843130BDB6"
Content-Language: en-GB
X-CMAE-Envelope: MS4wfNLsChwfZ82xqsJNdqOHxWXBO2XltxjisYbDxso3oBZN+IaIhgw1dxOw2GNVfACrl8aMKqiEFgSDwxiKy8/zgFj1Hrkc1aoTTIbjnizVzbQ/szLL5WIF
 QPAblIzxRzLwQ2bZV2sXNndr6uu+xHlKdozLHQ+83SLnBA7kj/NJH/a258+jOZ+8xWO7kPk2ZpXpXQ==
X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,
	RCVD_IN_MSPIKE_H2,SPF_PASS autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

[Message part 1 (text/plain, inline)]

Package: postgresql-common
Version: 200+deb10u4

I was doing a routine upgrade of the packages in my Devuan "Beowulf"
install, during the "apt upgrade" process I saw and captured the
following error(?) messages:

======================
Processing triggers for postgresql-common (200+deb10u4) ...
supported-versions: WARNING! Unknown distribution: devuan
debian found in ID_LIKE, treating as Debian
supported-versions: WARNING: Unknown Debian release: 3
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
  da_dk
  de_de
  en_ca
  en_gb
  en_us
  es_es
  et_ee
  fr
  hy_am
  ko
  ru_ru
Removing obsolete dictionary files:
======================

This was a part of the output which I captured and include as an attachment.

I do not actively (or at least consciously) use Postgresql on this
system (and there is no other real life user) so I cannot tell if this
was in fact harmful. However it doesn't take a genius to realise that
the (presumably) upstream script (trigger) involved is expecting a
Debian version number - probably greater than, say, 4 or 5, certainly
more than 3 - and is unhappy about seeing a 3. Somehow it needs to be
told that Devuan "3" is like Debian "10" - except when it isn't!

I wonder whether this is linked to - or rather follows on from:
https://bugs.devuan.org/cgi/bugreport.cgi?bug=159 ?

My "uname -a" output (for a machine called "rachel") is:
Linux rachel 4.19.0-14-rt-amd64 #1 SMP PREEMPT RT Debian 4.19.171-2
(2021-01-30) x86_64 GNU/Linux

Regards

Stephen

[Devuan_postgressql_upgrade_bug.txt (text/plain, attachment)]

Send a report that this bug log contains spam.

Devuan bug report logs - #575 postgresql-common packaging not handling Devuan version number

Devuan bug report logs - #575
postgresql-common packaging not handling Devuan version number