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

Full log

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

Received: (at 490) by bugs.devuan.org; 8 Aug 2020 10:00:06 +0000
Return-Path: <mark@hindley.org.uk>
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, 08 Aug 2020 10:00:06 +0000 (UTC)
Received: from mx.hindley.org.uk (mohindley.plus.com [81.174.245.179])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id 08E7DF60D01
	for <490@bugs.devuan.org>; Sat,  8 Aug 2020 11:50:25 +0200 (CEST)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <mark@hindley.org.uk>)
	id 1k4LUc-0001nX-3b; Sat, 08 Aug 2020 10:50:22 +0100
Received: (nullmailer pid 27926 invoked by uid 1000);
	Sat, 08 Aug 2020 09:50:21 -0000
Date: Sat, 8 Aug 2020 10:50:21 +0100
From: Mark Hindley <mark@hindley.org.uk>
To: Boian Bonev <bbonev@ipacct.com>
Cc: 490@bugs.devuan.org
Subject: Re: [devuan-dev] bug#490: gpsd: Current version of gpsd does not
 install /etc/init.d/gpsd and fails to start
Message-ID: <20200808095021.GE3011@hindley.org.uk>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <bb7ca9c158a8af390fed739ed67cfccd05ec520b.camel@ipacct.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_PASS autolearn=disabled
	version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

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.

> > Are you able to fix #314?
> 
> Checked it just now - that one does not apply to gpsd 3.20; previous
> gpsd versions generated header file with a fix for roll overs during
> build time (based on current time), so gpsd 3.16 built back in time had
> the problem while newly built one didn't have it. Upstream reworked the
> whole thing long ago. Unfortunatelly I can't verify it, just checked
> the source of gpsd and https://gitlab.com/gpsd/gpsd/-/issues/3 and it
> seems fixed.
> 
> > A couple of comments about the packaging:-
> > 
> >  - Please close #490 in the 'Fork for Devuan' changelog entry.
> 
> sure, also closed 314

Great.
 
> 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.

If you install devuan-lintian-profile you should get more sane lintian warnings.
 
> >  - 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.

> 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
https://git.devuan.org/devuan/documentation/src/branch/master/maintainers/JenkinsAutobuild.md

Thanks.

Mark

Send a report that this bug log contains spam.