Devuan bug report logs - #490
gpsd: Current version of gpsd does not install /etc/init.d/gpsd and fails to start

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#490: [devuan-dev] bug#490: gpsd: Current version of gpsd does not install /etc/init.d/gpsd and fails to start
Reply-To: Boian Bonev <bbonev@ipacct.com>, 490@bugs.devuan.org
Resent-From: Boian Bonev <bbonev@ipacct.com>
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: devuan-dev@lists.dyne.org
X-Loop: owner@bugs.devuan.org
Resent-Date: Sun, 09 Aug 2020 00:33:01 +0000
Resent-Message-ID: <handler.490.B490.159693240711559@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: followup 490
X-Devuan-PR-Package: gpsd
X-Devuan-PR-Keywords: 
References: <1594691276.4473.8.camel@ipacct.com>  <d9d718de-ca5c-4324-95eb-2bd12e77330c@email.android.com>  <20200716101610.GM5316@hindley.org.uk>  <7c5be8a78d2fbf7acfb1b627d326b361bff24c78.camel@ipacct.com>  <20200718142839.GS5316@hindley.org.uk>  <b7d78465db6be555eb71540a0becbb5dfa6c3d48.camel@ipacct.com>  <20200719121632.GU5316@hindley.org.uk>  <5ec55c97c61ba31cb29a2a8126cc778d14467887.camel@ipacct.com>  <20200807162109.GC3011@hindley.org.uk>  <bb7ca9c158a8af390fed739ed67cfccd05ec520b.camel@ipacct.com>  <20200808095021.GE3011@hindley.org.uk> <159451128337.26059.1765209716187424471.reportbug@rpi-gpsntp1>
Received: via spool by 490-submit@bugs.devuan.org id=B490.159693240711559
          (code B ref 490); Sun, 09 Aug 2020 00:33:01 +0000
Received: (at 490) by bugs.devuan.org; 9 Aug 2020 00:20:07 +0000
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); Sun, 09 Aug 2020 00:20:07 +0000 (UTC)
Received: from mx1.bul.net (mx1.bul.net [195.85.215.56])
	by vm6.ganeti.dyne.org (Postfix) with ESMTP id B7812F604B6
	for <490@bugs.devuan.org>; Sun,  9 Aug 2020 02:11:46 +0200 (CEST)
Received: by mx1.bul.net (Postfix, from userid 1002)
	id BBA4B60702; Sun,  9 Aug 2020 03:11:43 +0300 (EEST)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=disabled
	version=3.4.2
Received: from purple.bonev.com (purple.bonev.com [195.85.215.215])
	by mx1.bul.net (Postfix) with ESMTP id C5FE0606EA
	for <490@bugs.devuan.org>; Sun,  9 Aug 2020 03:11:35 +0300 (EEST)
Received: (qmail 3298 invoked by uid 64020); 9 Aug 2020 03:11:35 +0300
Received: from unknown (HELO asus) (bbonev@ipacct.com@195.85.215.8)
  by purple.bonev.com with AES256-GCM-SHA384 encrypted SMTP; 9 Aug 2020 03:11:35 +0300
Message-ID: <dbd58ca61c5d37f439d1312344eca652d7fc3659.camel@ipacct.com>
From: Boian Bonev <bbonev@ipacct.com>
To: Mark Hindley <mark@hindley.org.uk>
Cc: 490@bugs.devuan.org
Date: Sun, 09 Aug 2020 03:13:40 +0300
In-Reply-To: <20200808095021.GE3011@hindley.org.uk>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.5-1.1 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit

Hi Mark,

On Sat, 2020-08-08 at 10:50 +0100, Mark Hindley wrote:
> On Fri, Aug 07, 2020 at 11:57:57PM +0300, Boian Bonev wrote:
> > > I assume you have checked functionality.
> > 
> > Not all of it, because I do the development on an amd64 vm and
> > there I
> > can only test install and to see that the daemon starts, but not
> > that
> > it actually works. I have an aarch64 RPI GPS NTP server and will
> > test
> > it there (it is a production one, but I have means to bypass in
> > case it
> > breaks).
> 
> OK.

Test in a real gpsd usage went fine. I just upgraded the package,
restarted gpsd and all is fine:

~# dpkg -l|grep gps
ii  gpsd                                3.20-
12+devuan1                    arm64        Global Positioning System -
daemon
ii  gpsd-clients                        3.20-
12+devuan1                    arm64        Global Positioning System -
clients
ii  gpsd-debugtools                     3.20-
12+devuan1                    arm64        Global Positioning System -
debugging tools
ii  gpsd-tools                          3.20-
12+devuan1                    arm64        Global Positioning System -
tools
ii  libgps26:arm64                      3.20-
12+devuan1                    arm64        Global Positioning System -
library
ii  libqgpsmm26:arm64                   3.20-
12+devuan1                    arm64        Global Positioning System -
Qt wrapper for libgps
ii  python3-gps                         3.20-
12+devuan1                    arm64        Global Positioning System -
Python 3 libraries
> 
> > > Are you able to fix #314?
....
>  
> > I am wondering how bugs are distinguished, is there a tag like LP:
> > that
> > closes Devuan bugs? I did a test build of iwd and lintian was
> > complaining about improbable-bug-number-in-closes.
> 
> They aren't. It is just that building on Devuan buildhosts will close
> Devuan BTS
> bugs.

OK. Some day these will clash, anyways I believe there is enough time
to find a solution until then. It would be a good idea to have a tag
for Devuan specific tag - this will allow Debian package to close
Devuan bugs (like LP:).

> If you install devuan-lintian-profile you should get more sane
> lintian warnings.

I did, but most probably not using it.

> > >  - d/control: as you have renamed gpsd-dbg to gpds-dbg-tools
> > > (which
> > > seems
> > >    sensible) you will need conflicts, provides and replaces for
> > > gpsd-
> > > dbg
> > >    otherwise upgrades will fail due to a file conflict.
> > 
> > I have planned one more change for this part - to install the
> > executables under /usr/libexec/gpsd/debug; then there will be no
> > conflict.
> > 
> > But on second thought, to avoid possible confusion, it is a
> > good idea to set them - when main package is upgraded it will be a
> > good
> > idea to also upgrade this part and not leave the old gpsd-dbg
> > installed
> > with new gpsd-dbg-tools.
> 
> Yes, exactly.

I have abandoned the idea to rename a package - that will be too big
hassle to support in future and there is no other benefit. Fixing the
other things is enough, IMHO.

> > Also I see that there is a transition for
> > gpsd-dbg to gpsd-dbgsym which I believe is long ago finished.
> > 
> > > Once those are fixed I can copy the repo to 
> > > https://git.devuan.org/devuan/gpsd
> > > and make you maintainer. Then you will be able to trigger the
> > > production build.
> > 
> > I have no idea how that part works. Is there a way to test it
> > first?
> 
> Not really. If a local build with gbp works it should be OK. The
> documentation
> for how to trigger the production build is

OK, lets go for it. Current repo should be fine to go, also if there is
something to fix, I will do it fast.

https://git.devuan.org/devuan/documentation/src/branch/master/maintainers/JenkinsAutobuild.md


With best regards,
b.

Send a report that this bug log contains spam.