Your message dated Mon, 09 Mar 2026 20:39:33 +0000
with message-id <[email protected]>
and subject line Bug#1085104: fixed in rlinetd 0.9.3-4
has caused the Debian Bug report #1085104,
regarding rlinetd FTCBFS: debian/rules hard codes the build architecture pkgconf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1085104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085104
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rlinetd
Version: 0.9.3-3
Tags: patch
User: [email protected]
Usertags: ftcbfs

rlinetd fails to cross build from source, because debian/rules hard
codes the build architecture pkgconf. As a result tirpc is not found and
things go bad. I'm attaching a patch to make it use the host
architecture one for your convenience.

Helmut
diff --minimal -Nru rlinetd-0.9.3/debian/changelog 
rlinetd-0.9.3/debian/changelog
--- rlinetd-0.9.3/debian/changelog      2024-09-01 23:55:53.000000000 +0200
+++ rlinetd-0.9.3/debian/changelog      2024-10-14 18:45:50.000000000 +0200
@@ -1,3 +1,10 @@
+rlinetd (0.9.3-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Use the host architecture pkgconf. (Closes: #-1)
+
+ -- Helmut Grohne <[email protected]>  Mon, 14 Oct 2024 18:45:50 +0200
+
 rlinetd (0.9.3-3) unstable; urgency=low
 
   * Fix FTBFS by switching to libtirpc (closes: #1066466). Thanks to
diff --minimal -Nru rlinetd-0.9.3/debian/control rlinetd-0.9.3/debian/control
--- rlinetd-0.9.3/debian/control        2024-09-01 23:55:53.000000000 +0200
+++ rlinetd-0.9.3/debian/control        2024-10-14 18:45:50.000000000 +0200
@@ -9,7 +9,7 @@
                libcap2-dev [linux-any],
                libtirpc-dev,
                libwrap0-dev,
-               pkgconf-bin
+               pkgconf,
 Rules-Requires-Root: no
 Homepage: https://salsa.debian.org/debian/rlinetd
 Vcs-Git: https://salsa.debian.org/debian/rlinetd.git -b debian
diff --minimal -Nru rlinetd-0.9.3/debian/rules rlinetd-0.9.3/debian/rules
--- rlinetd-0.9.3/debian/rules  2024-09-01 23:55:53.000000000 +0200
+++ rlinetd-0.9.3/debian/rules  2024-10-14 18:45:50.000000000 +0200
@@ -2,26 +2,22 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
+include /usr/share/dpkg/architecture.mk
+include /usr/share/dpkg/buildtools.mk
+
 BUILD_DIR       := BUILD
 DH_AUTO_OPTIONS := -v -Sautoconf --parallel -B$(BUILD_DIR)
 DESTDIR         := $(CURDIR)/debian/$(shell dh_listpackages)
 
 DEB_BUILD_MAINT_OPTIONS  := hardening=+all abi=+lfs
 # TODO: add support for libtirpc into upstream packaging instead
-DEB_CFLAGS_MAINT_APPEND  := $(shell pkgconf --cflags libtirpc)
-DEB_LDFLAGS_MAINT_APPEND := $(shell pkgconf --libs libtirpc)
+DEB_CFLAGS_MAINT_APPEND  := $(shell $(PKG_CONFIG) --cflags libtirpc)
+DEB_LDFLAGS_MAINT_APPEND := $(shell $(PKG_CONFIG) --libs libtirpc)
 DPKG_EXPORT_BUILDFLAGS   := 1
 
 include /usr/share/dpkg/buildflags.mk
-include /usr/share/dpkg/architecture.mk
 include /usr/share/dpkg/pkg-info.mk
 
-ifneq ($(DEB_HOST_GNU_TYPE),$(DEB_BUILD_GNU_TYPE))
-  CC := $(DEB_HOST_GNU_TYPE)-gcc
-else
-  CC := gcc
-endif
-
 # check for maintainer mode
 ifneq (,$(findstring maintainer,$(DEB_BUILD_OPTIONS)))
   MAINTAINER_MODE := yes

--- End Message ---
--- Begin Message ---
Source: rlinetd
Source-Version: 0.9.3-4
Done: Robert Luberda <[email protected]>

We believe that the bug you reported is fixed in the latest version of
rlinetd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Robert Luberda <[email protected]> (supplier of updated rlinetd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 09 Mar 2026 08:27:25 +0100
Source: rlinetd
Architecture: source
Version: 0.9.3-4
Distribution: unstable
Urgency: medium
Maintainer: Robert Luberda <[email protected]>
Changed-By: Robert Luberda <[email protected]>
Closes: 1039349 1085104
Changes:
 rlinetd (0.9.3-4) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: Use the host architecture pkgconf (closes: #1085104).
 .
   [ Robert Luberda ]
   * Install rlinetd.service file (closes: #1039349).
   * Upgrade format of debian/watch file.
   * debian/control:
     + remove redundant fields: Priority and Rules-Requires-Root;
     + bump Standards-Version to 4.7.3.
Checksums-Sha1:
 995740b446a164840a1071f1b5edf8b41bf1c1a0 2161 rlinetd_0.9.3-4.dsc
 c4d743ff35f4fed6f92a81bbc3d232589c5222b2 20736 rlinetd_0.9.3-4.debian.tar.xz
 898162346829dd40c7ccbc4f55a1b48f8c1be68c 6677 rlinetd_0.9.3-4_amd64.buildinfo
Checksums-Sha256:
 51592d9a431f81083a67087e3e50257f3235beddb5628e4d4abb0e6e7ed51d91 2161 
rlinetd_0.9.3-4.dsc
 5b15b81f19714b214dc4767da966625f69380579f26d4b8fb255f937e9594093 20736 
rlinetd_0.9.3-4.debian.tar.xz
 593a4db2b9ea001e35e508310534f8d713e734c78a133c4e43e454b93f8bce3c 6677 
rlinetd_0.9.3-4_amd64.buildinfo
Files:
 02fd30336b5fbf2e9b9d578b8054531e 2161 net optional rlinetd_0.9.3-4.dsc
 6c2b6a85908b46a0b858817771255134 20736 net optional 
rlinetd_0.9.3-4.debian.tar.xz
 01ec7085e24d48abd64f934b9b3826c2 6677 net optional 
rlinetd_0.9.3-4_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEENeh2+rTTcy6TtNI3Yx3nVTvor9QFAmmueKkACgkQYx3nVTvo
r9TApA//YBsawcM3Upe2k/C+X57/gUxM2VcCV5DEvFC/yNj/dPpVtGe+nZsSPN++
1sXhmKIZIx0XFQg8SspaC4b91Un5DrZLitLhEb+Db75hBwzyIS+gcli+idyJMKIo
Jv0cJeMxUvQ8ZGasILDH4XkrzT8Zf8zFjcAX79p9A+MUBOl3Ka5BFzxlNo/gOwnY
MayJq4mzDpLKnW6MOc9ZGFwwdbaPf76cI38Db7lkgb9Byt1FSHIWgJI3IDFEGonk
rbP5tMF5R5qPK1dO91EZyPiDBfcDX5OKsCVR6lWwp+ILvAOlgKn47YxSshgymg+O
HcPEklJe7KvAhOmsGPoQVpKJWRCXSzmQ6noXe1Sth9Uif5q5z/+42+tw51R5P/TV
DLpSK4y7DoCZNhOfUt0tU39pNvgU0nw6qaeHRfk/nyjv9Sc2hnzjDHo8ellvxbob
fjQLya6LvNPLwf5iexKCLLQbjqhK5IGwVGHHidimn9w16T633N9hhP1Jgl49iu74
lnXKGjChgALhIIp6/CCX7jpQN+vmxBmOIr3lKFxvBFnQWkabfHzQEP7bBe6/NaKV
GeHSvXHgkbwLFDIrjVyIJm0HGSD/wD64mY3vr3t9pjajnLbB7dwuo8qPGu8UXB3L
q+o40zDhiqEi0ksVmG2RBzpne5Hrx+/s71DXD5OCzy/2p7x8Iw4=
=bZMX
-----END PGP SIGNATURE-----

Attachment: pgpH0NdG8s_SH.pgp
Description: PGP signature


--- End Message ---

Reply via email to