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

version graph

Package: gpsd; Maintainer for gpsd is Boian Bonev <bbonev@ipacct.com>; Source for gpsd is src:gpsd.

Reported by: Boian Bonev <bbonev@ipacct.com>

Date: Sun, 12 Jul 2020 00:03:01 UTC

Severity: grave

Found in version 3.20-12

Fixed in version 3.20-12+devuan1

Done: dak@devuan.org

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: Fri, 17 Jul 2020 18:03:01 +0000
Resent-Message-ID: <handler.490.B490.15950082224578@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> <159451128337.26059.1765209716187424471.reportbug@rpi-gpsntp1>
Received: via spool by 490-submit@bugs.devuan.org id=B490.15950082224578
          (code B ref 490); Fri, 17 Jul 2020 18:03:01 +0000
Received: (at 490) by bugs.devuan.org; 17 Jul 2020 17:50:22 +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); Fri, 17 Jul 2020 17:50:22 +0000 (UTC)
Received: from mx1.bul.net (mx1.bul.net [195.85.215.56])
	by vm6.ganeti.dyne.org (Postfix) with ESMTP id 66798F60972
	for <490@bugs.devuan.org>; Fri, 17 Jul 2020 19:41:51 +0200 (CEST)
Received: by mx1.bul.net (Postfix, from userid 1002)
	id 13F4060A1C; Fri, 17 Jul 2020 20:41:50 +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 728B260868
	for <490@bugs.devuan.org>; Fri, 17 Jul 2020 20:41:47 +0300 (EEST)
Received: (qmail 24237 invoked by uid 64020); 17 Jul 2020 20:41:47 +0300
Received: from unknown (HELO aware) (bbonev@ipacct.com@195.85.215.8)
  by purple.bonev.com with AES256-GCM-SHA384 encrypted SMTP; 17 Jul 2020 20:41:47 +0300
Message-ID: <7c5be8a78d2fbf7acfb1b627d326b361bff24c78.camel@ipacct.com>
From: Boian Bonev <bbonev@ipacct.com>
To: Mark Hindley <mark@hindley.org.uk>
Cc: 490@bugs.devuan.org
Date: Fri, 17 Jul 2020 20:41:47 +0300
In-Reply-To: <20200716101610.GM5316@hindley.org.uk>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.3-0ubuntu1 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Hi Mark,

> The documentation is here:
> https://git.devuan.org/devuan/documentation/src/branch/master/maintainers/PackagingGuide.md
> 
> You will need to follow that. Out package builder uses git
> buildpackage and your
> repo doesn't build with that ATM.

I have been following exactly that.

Have tried on ascii and chimaera hosts - on ascii the build fails
because scons requires newer Python while on chimaera "dpkg-source -b
." exits with 127 without particular reason for that:

 dpkg-source -b .
dpkg-source: warning: upstream signing key but no upstream tarball
signature
dpkg-source: info: using options from gpsd-3.20/debian/source/options:
--extend-diff-ignore=^\.travis\.yml$
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building gpsd using existing ./gpsd_3.20.orig.tar.gz
dpkg-source: info: using patch list from debian/patches/series
dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit
status 127

I have got the same error on aarch64/RPI with Devuan/chimaera while
using debuild and could make it work only by renaming dpkg-source and
wrapping it to change 127 to 0 (but obviously that is only a temp
workaround). I suppose there is some problem in latest dpkg-source or I
have missed to install/configure something but couldn't find what it
is.

Can you share some error message that you have seen?

> Ping me on #devuan-dev if you need more help.

Haven't been on irc last 25+ years ;) Will try to see if I still
remember how that is done.

> It might be worth asking the Debian maintainer to update their tree
> and then you
> can just import it with history.

Will try that. It wouldn't be too hard to rebase my commits on top of
it.

With best regards,
b.

Send a report that this bug log contains spam.


Devuan BTS -- Powered by Debian bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Devuan Bugs Owner <owner@bugs.devuan.org>.
Last modified: Fri Mar 29 15:12:23 2024;