Devuan logs - #752, boring messages

Message sent to [email protected], Devuan Maintainers <[email protected]>:

Subject: bug#752: FTBFS: qch files not built
Reply-To: Peter Chubb <[email protected]>, [email protected]
Resent-From: Peter Chubb <[email protected]>
Resent-To: [email protected]
Resent-CC: Devuan Maintainers <[email protected]>
Resent-Date: Tue, 21 Mar 2023 03:52:01 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
Received-SPF: Pass (sender SPF authorized) identity=helo; client-ip=103.4.19.249; helo=mx3.chubb.wattle.id.au; [email protected]; receiver=<UNKNOWN> 
MIME-Version: 1.0
From: Peter Chubb <[email protected]>
To: Devuan Bug Tracking System <[email protected]>
Message-ID: <167937059353.32354.3989902258549573594.reportbug@localhost>
Date: Tue, 21 Mar 2023 14:49:53 +1100
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Source: dbus
Version: 1.14.6-1devuan1
Severity: normal
Tags: ftbfs

Dear Maintainer,

I did:
  sudo apt update
  sudo apt build-dep dbus
  apt source dbus
  cd dbus-1.14.6
  debuild -b -uc -us

and after some time and lots of output I see:
  /usr/bin/mkdir -p /home/peterc/src/dbus-1.14.6/debian/tmp/usr/share/doc/dbus
  /usr/bin/install -c -m 644 /home/peterc/src/dbus-1.14.6/debian/build-main/doc/api/qch/dbus-1.14.6.qch /home/peterc/src/dbus-1.14.6/debian/tmp/usr/share/doc/dbus
  /usr/bin/install: cannot stat '/home/peterc/src/dbus-1.14.6/debian/build-main/doc/api/qch/dbus-1.14.6.qch': No such file or directory
  make[4]: *** [Makefile:935: install-data-local] Error 1
  make[4]: Leaving directory '/home/peterc/src/dbus-1.14.6/debian/build-main/doc'
  make[3]: *** [Makefile:784: install-am] Error 2
  make[3]: Leaving directory '/home/peterc/src/dbus-1.14.6/debian/build-main/doc'
  make[2]: *** [Makefile:699: install-recursive] Error 1
  make[2]: Leaving directory '/home/peterc/src/dbus-1.14.6/debian/build-main'
  dh_auto_install: error: cd debian/build-main && make -j1 install DESTDIR=/home/peterc/src/dbus-1.14.6/debian/tmp AM_UPDATE_INFO_DIR=no returned exit code 2
  make[1]: *** [debian/rules:214: override_dh_auto_install] Error 25
  make[1]: Leaving directory '/home/peterc/src/dbus-1.14.6'
  make: *** [debian/rules:12: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
  debuild: fatal error at line 1182:
  dpkg-buildpackage -us -uc -ui -b failed


Maybe some build dependency is missing from the control file?

-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 5 (daedalus/ceres)
Release:	5
Codename:	daedalus ceres
Architecture: x86_64

Kernel: Linux 6.1.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages dbus is related to:
ii  dbus-x11      1.14.6-1devuan1
pn  systemd       <none>
pn  systemd-sysv  <none>

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
Content-Type: text/plain; charset=utf-8
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Peter Chubb <[email protected]>
Subject: bug#752: Acknowledgement (FTBFS: qch files not built)
Message-ID: <[email protected]>
References: <167937059353.32354.3989902258549573594.reportbug@localhost>
X-Devuan-PR-Message: ack 752
X-Devuan-PR-Package: src:dbus
X-Devuan-PR-Source: dbus
Reply-To: [email protected]
Date: Tue, 21 Mar 2023 03:52:07 +0000

Thank you for filing a new bug report with Devuan.

You can follow progress on this bug here: 752: https://bugs.devuan.org/cgi/=
bugreport.cgi?bug=3D752.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Devuan Maintainers <[email protected]>

If you wish to submit further information on this problem, please
send it to [email protected].

Please do not send mail to [email protected] unless you wish
to report a problem with the Bug-tracking system.

--=20
752: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D752
Devuan Bug Tracking System
Contact [email protected] with problems

Message sent to [email protected], Devuan Maintainers <[email protected]>:

Subject: bug#752: Worked out the fix
Reply-To: [email protected], [email protected]
Resent-From: [email protected]
Resent-To: [email protected]
Resent-CC: Devuan Maintainers <[email protected]>
Resent-Date: Tue, 21 Mar 2023 06:22:01 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
References: <167937059353.32354.3989902258549573594.reportbug@localhost>
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=103.4.19.249; helo=mx3.chubb.wattle.id.au; [email protected]; receiver=<UNKNOWN> 
Date: Tue, 21 Mar 2023 17:19:14 +1100
Message-ID: <[email protected]>
From: [email protected]
To: [email protected]
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue)
 FLIM-LB/1.14.9 (=?UTF-8?Q?Goj=C5=8D?=) APEL-LB/10.8 EasyPG/1.0.0
 Emacs/28.2 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII


THe missing build-depend is on qhelpgenerator-qt5

Installing that allowed the build to complete successfully.

Peter C

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
Content-Type: text/plain; charset=utf-8
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: [email protected]
Subject: bug#752: Info received (Worked out the fix)
Message-ID: <[email protected]>
References: <[email protected]>
X-Devuan-PR-Message: ack-info 752
X-Devuan-PR-Package: src:dbus
X-Devuan-PR-Source: dbus
Reply-To: [email protected]
Date: Tue, 21 Mar 2023 06:22:04 +0000

Thank you for the additional information you have supplied regarding
this bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Devuan Maintainers <[email protected]>

If you wish to submit further information on this problem, please
send it to [email protected].

Please do not send mail to [email protected] unless you wish
to report a problem with the Bug-tracking system.

--=20
752: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D752
Devuan Bug Tracking System
Contact [email protected] with problems

Message sent to [email protected], Devuan Maintainers <[email protected]>:

X-Loop: [email protected]
Subject: bug#752: [devuan-dev] bug#752: Worked out the fix
Reply-To: Mark Hindley <[email protected]>, [email protected]
Resent-From: Mark Hindley <[email protected]>
Resent-To: [email protected]
Resent-CC: Devuan Maintainers <[email protected]>
X-Loop: [email protected]
Resent-Date: Tue, 21 Mar 2023 07:40:01 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: followup 752
X-Devuan-PR-Package: src:dbus
X-Devuan-PR-Keywords: 
References: <167937059353.32354.3989902258549573594.reportbug@localhost> <[email protected]> <167937059353.32354.3989902258549573594.reportbug@localhost>
X-Devuan-PR-Source: dbus
Received: via spool by [email protected] id=B752.167938435129896
          (code B ref 752); Tue, 21 Mar 2023 07:40:01 +0000
Received: (at 752) by bugs.devuan.org; 21 Mar 2023 07:39:11 +0000
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Tue, 21 Mar 2023 07:39:11 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id VfHhMeheGWSfEgAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Tue, 21 Mar 2023 07:38:16 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id AD1DA597; Tue, 21 Mar 2023 07:38:16 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 6433F34
	for <[email protected]>; Tue, 21 Mar 2023 07:38:01 +0000 (UTC)
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 <[email protected]>)
	id 1peWZ4-0003rF-0H; Tue, 21 Mar 2023 07:37:50 +0000
Received: (nullmailer pid 11124 invoked by uid 1000);
	Tue, 21 Mar 2023 07:37:49 -0000
Date: Tue, 21 Mar 2023 07:37:49 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Cc: [email protected]
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

Control: tags -1 moreinfo

Peter,

The default for configure --enable-qt-help defaults is auto. However, you
appear to building directly on a production system and I suspect you have some
Qt package installed on the system which then means the build enables qt-help.

To get a standard build you should use a build chroot (pbuilder, sbuild,
qemubuild...)

Doing that, the configure stage includes

 checking for qhelpgenerator... no
 checking for qhelpgenerator-qt5... no

the qt help files are not attempted and the build succeeds.

Can you attach the failing build log without qhelpgenerator-qt5 installed?

Thanks

Mark

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
Content-Type: text/plain; charset=utf-8
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Mark Hindley <[email protected]>
Subject: bug#752: Info received ([devuan-dev] bug#752: Worked out the fix)
Message-ID: <[email protected]>
References: <[email protected]>
X-Devuan-PR-Message: ack-info 752
X-Devuan-PR-Package: src:dbus
X-Devuan-PR-Source: dbus
Reply-To: [email protected]
Date: Tue, 21 Mar 2023 07:40:05 +0000

Thank you for the additional information you have supplied regarding
this bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Devuan Maintainers <[email protected]>

If you wish to submit further information on this problem, please
send it to [email protected].

Please do not send mail to [email protected] unless you wish
to report a problem with the Bug-tracking system.

--=20
752: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D752
Devuan Bug Tracking System
Contact [email protected] with problems

Message received at [email protected]:

Received: (at 752) by bugs.devuan.org; 21 Mar 2023 07:39:11 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Tue, 21 Mar 2023 07:39:11 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id VfHhMeheGWSfEgAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Tue, 21 Mar 2023 07:38:16 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id AD1DA597; Tue, 21 Mar 2023 07:38:16 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 6433F34
	for <[email protected]>; Tue, 21 Mar 2023 07:38:01 +0000 (UTC)
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 <[email protected]>)
	id 1peWZ4-0003rF-0H; Tue, 21 Mar 2023 07:37:50 +0000
Received: (nullmailer pid 11124 invoked by uid 1000);
	Tue, 21 Mar 2023 07:37:49 -0000
Date: Tue, 21 Mar 2023 07:37:49 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: [devuan-dev] bug#752: Worked out the fix
Message-ID: <[email protected]>
References: <167937059353.32354.3989902258549573594.reportbug@localhost>
 <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

Control: tags -1 moreinfo

Peter,

The default for configure --enable-qt-help defaults is auto. However, you
appear to building directly on a production system and I suspect you have some
Qt package installed on the system which then means the build enables qt-help.

To get a standard build you should use a build chroot (pbuilder, sbuild,
qemubuild...)

Doing that, the configure stage includes

 checking for qhelpgenerator... no
 checking for qhelpgenerator-qt5... no

the qt help files are not attempted and the build succeeds.

Can you attach the failing build log without qhelpgenerator-qt5 installed?

Thanks

Mark

Message sent to [email protected], Devuan Maintainers <[email protected]>:

X-Loop: [email protected]
Subject: bug#752: [devuan-dev] bug#752: Worked out the fix
Reply-To: Mark Hindley <[email protected]>, [email protected]
Resent-From: Mark Hindley <[email protected]>
Resent-To: [email protected]
Resent-CC: Devuan Maintainers <[email protected]>
X-Loop: [email protected]
Resent-Date: Tue, 21 Mar 2023 08:34:01 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
X-Devuan-PR-Message: followup 752
X-Devuan-PR-Package: src:dbus
X-Devuan-PR-Keywords: moreinfo
References: <167937059353.32354.3989902258549573594.reportbug@localhost> <[email protected]> <[email protected]> <167937059353.32354.3989902258549573594.reportbug@localhost>
X-Devuan-PR-Source: dbus
Received: via spool by [email protected] id=B752.16793875904570
          (code B ref 752); Tue, 21 Mar 2023 08:34:01 +0000
Received: (at 752) by bugs.devuan.org; 21 Mar 2023 08:33:10 +0000
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Tue, 21 Mar 2023 08:33:09 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id JTrbLJ9rGWSRFAAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Tue, 21 Mar 2023 08:32:31 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id 8595B2A8; Tue, 21 Mar 2023 08:32:31 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 20D6232
	for <[email protected]>; Tue, 21 Mar 2023 08:32:16 +0000 (UTC)
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 <[email protected]>)
	id 1peXPb-00046n-5E; Tue, 21 Mar 2023 08:32:07 +0000
Received: (nullmailer pid 24893 invoked by uid 1000);
	Tue, 21 Mar 2023 08:32:07 -0000
Date: Tue, 21 Mar 2023 08:32:07 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Cc: [email protected]
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

On Tue, Mar 21, 2023 at 07:37:49AM +0000, Mark Hindley wrote:
> Control: tags -1 moreinfo
> 
> Peter,
> 
> The default for configure --enable-qt-help defaults is auto. However, you
> appear to building directly on a production system and I suspect you have some
> Qt package installed on the system which then means the build enables qt-help.

Does your system have qtchooser installed?

If so, that is the cause of the auto enablement of qt-help.

I suppose we could explicitly specify --enable-qt-help=no in d/rules.

Mark

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
Content-Type: text/plain; charset=utf-8
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Mark Hindley <[email protected]>
Subject: bug#752: Info received ([devuan-dev] bug#752: Worked out the fix)
Message-ID: <[email protected]>
References: <[email protected]>
X-Devuan-PR-Message: ack-info 752
X-Devuan-PR-Package: src:dbus
X-Devuan-PR-Keywords: moreinfo
X-Devuan-PR-Source: dbus
Reply-To: [email protected]
Date: Tue, 21 Mar 2023 08:34:03 +0000

Thank you for the additional information you have supplied regarding
this bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Devuan Maintainers <[email protected]>

If you wish to submit further information on this problem, please
send it to [email protected].

Please do not send mail to [email protected] unless you wish
to report a problem with the Bug-tracking system.

--=20
752: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D752
Devuan Bug Tracking System
Contact [email protected] with problems