Your message dated Tue, 30 Jul 2024 13:35:10 +0000
with message-id <e1syn0q-006ltq...@fasolo.debian.org>
and subject line Bug#1077591: fixed in gnumach 2:1.8+git20240714-3
has caused the Debian Bug report #1077591,
regarding gnumach FTBFS with stage1 profile
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 ow...@bugs.debian.org
immediately.)


-- 
1077591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnumach
Version: 2:1.8+git20240714-1
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

Hi Samuel et al,

you recently asked me to look into your proposed change
e9d733e62a47ce2ce8bc2101cad21647ce5ae81c to rebootstrap.git. Thanks for
your contribution and your patience with me. I looked into integrating
it and your change affects the glibc build. Unfortunately, rebootstrap
doesn't get that far currently. It fails building gnumach stage1.

Hence I logged into exodar (thanks for providing a working porter box)
and attempted natively building a gnumach stage1. This is how it looked:

| (sid_hurd-i386-dchroot)helmutg@exodar:~/gnumach-1.8+git20240714$ 
dpkg-buildpackage -Pstage1
| dpkg-buildpackage: info: source package gnumach
| dpkg-buildpackage: info: source version 2:1.8+git20240714-1
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by Samuel Thibault 
<sthiba...@debian.org>
| dpkg-buildpackage: info: host architecture hurd-i386
|  dpkg-source --before-build .
|  debian/rules clean
| dh_testdir
| rm -f debian/control.stamp
| rm -f machine
| rm -rf build build-xen build-pae build-smp build-dbg build-xen-dbg 
build-pae-dbg build-smp-dbg 
/home/helmutg/gnumach-1.8+git20240714/debian/tmp-udeb 
/home/helmutg/gnumach-1.8+git20240714/debian/tmp-xen-udeb 
/home/helmutg/gnumach-1.8+git20240714/debian/tmp-xen 
/home/helmutg/gnumach-1.8+git20240714/debian/tmp-pae 
/home/helmutg/gnumach-1.8+git20240714/debian/tmp-smp 
/home/helmutg/gnumach-1.8+git20240714/debian/tmp-dbg 
/home/helmutg/gnumach-1.8+git20240714/debian/tmp-xen-dbg 
/home/helmutg/gnumach-1.8+git20240714/debian/tmp-pae-dbg 
/home/helmutg/gnumach-1.8+git20240714/debian/tmp-smp-dbg
| # Clean up autogenerated cruft
| rm -rf autom4te.cache build-aux
| rm -f aclocal.m4 config.h.in configure INSTALL Makefile.in
| rm -f doc/mach.info* doc/stamp-vti doc/version.texi
| find -name '*~' -o -name '*.rej' -o -name '*.orig' | xargs rm -f
| rm -f debian/gnumach-image-*.preinst
| rm -f debian/gnumach-image-*.prerm
| rm -f debian/gnumach-image-*.postinst
| rm -f debian/gnumach-image-*.postrm
| rm -rf /home/helmutg/gnumach-1.8+git20240714/.parallel
| dh_clean
| /usr/bin/make -C build install-data \
|         DESTDIR=/home/helmutg/gnumach-1.8+git20240714/debian/tmp
| make[1]: *** build: No such file or directory.  Stop.
| make: *** [debian/rules:215: clean] Error 2
| dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2
| (sid_hurd-i386-dchroot)helmutg@exodar:~/gnumach-1.8+git20240714$

This is also how the failure from rebootstrap looks like.

I looked into debian/rules and was a bit confused by the inconsistent
indenting of make-level ifs. The culprit seems to be the ifeq on line
219. It resides inside the clean target specification and the true-ish
branch contains the install target, but the false-ish branch does not
and therefore the make install-data is appended to the clean target.

I attempted adding "install: build" after the matching else on line 295,
but that would merely insert a configure run before failing in the same
way.

Can I defer this problem to you and then resume applying your glibc
patch once I can actually verify it inside rebootstrap?

Related to that given that you are entitled to commit to Debian's glibc
packaging, did you also commit your change there? The rebootstrap patch
policy is that every upstream change must be accompanied with an
"upstreaming effort reference" (e.g. bug report, upstream commit, ...)
and the glibc packaging is an upstream to rebootstrap.

Helmut

--- End Message ---
--- Begin Message ---
Source: gnumach
Source-Version: 2:1.8+git20240714-3
Done: Samuel Thibault <sthiba...@debian.org>

We believe that the bug you reported is fixed in the latest version of
gnumach, 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 1077...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Samuel Thibault <sthiba...@debian.org> (supplier of updated gnumach 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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Tue, 30 Jul 2024 11:28:41 +0200
Source: gnumach
Architecture: source
Version: 2:1.8+git20240714-3
Distribution: unstable
Urgency: medium
Maintainer: GNU Hurd Maintainers <debian-hurd@lists.debian.org>
Changed-By: Samuel Thibault <sthiba...@debian.org>
Closes: 1077591
Changes:
 gnumach (2:1.8+git20240714-3) unstable; urgency=medium
 .
   * rules: Fix stage1 build (Closes: Bug#1077591)
   * rules: Fix cleaning build-up and build-up-dbg.
Checksums-Sha1:
 765f030a9b787fd01a5ff79ccbeab4ed4b3ab5cd 5568 gnumach_1.8+git20240714-3.dsc
 5f5738159f061d4d5e6df94128215f82cbc1e5ab 29712 
gnumach_1.8+git20240714-3.debian.tar.xz
 5794c867def3533d0636362a97c7d11d41cc8c94 9843 
gnumach_1.8+git20240714-3_source.buildinfo
Checksums-Sha256:
 75836644329e85ff9f1c81603dabf91b7aace321625ebca7cca71a1d19f24688 5568 
gnumach_1.8+git20240714-3.dsc
 3367f1773d02725a92f9bd4942ad64487a86fbfd99f1d1bad35416ae061cfc6c 29712 
gnumach_1.8+git20240714-3.debian.tar.xz
 51d13e73d0c1840cfa3b1fab9d29b3fbfceac3693b98dbc0f9da34bd129fee98 9843 
gnumach_1.8+git20240714-3_source.buildinfo
Files:
 01c6733a5e946545a06ff256271d6097 5568 kernel optional 
gnumach_1.8+git20240714-3.dsc
 d5f08824b06c8cda34c42ca12b3010dc 29712 kernel optional 
gnumach_1.8+git20240714-3.debian.tar.xz
 060d1263cdeb4911635f5b55bb38da29 9843 kernel optional 
gnumach_1.8+git20240714-3_source.buildinfo

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

iQIzBAEBCgAdFiEEZTSF1IMOAGwT71n/aHTOWK4tfj8FAmao6S0ACgkQaHTOWK4t
fj8dYg/+JgWmTTZxfQEyeFnPE2ClMMavePueJ+xENMknxpqRfQDY15aR8giJiUTx
pcGmOFwmKzT2iekON9pzf+OWkxVAGeMrd6XfRpYc2pYVzHP4khKQ4vtzk0+q5lOa
S1lcN6BbqmWR65zzeviKQ0UF+C3dX36m34HVcdammrwODeCiH63Ycv6UBrhA454P
HI9AUI9UTGlzZPVvFc5HEsU00FWCvziScuLqZbU2sT+yX0z6E3Foj53oHvZOM98Y
DnZ73goF0L6yl3E8amSFEfwQuIF1LVbfAjbROx+nT8c0XSqUL2tq4hFGisjgr46q
iI7Bd0w5d2/WyAnNa7uYGt9bihDq5If9zvvbC2D8soRcY3qZj/AO8yH4v0NgOn0u
pfdmHmEsSDjjy8vUASBd8ELvc/JIboU1WGDe2D53fJVo6LHMicbF8rR1BKPiFL8c
lRnpGmXfkeZOIyBB/z/yHtlYYKnW5PQasU9AtxCFipuznftf+aRqJ+JyyH93Ji7a
vKEEgjGgQlec/RKZWG1ZcJH9W5vIoC01+FztM+dce7wyc2bVVIViC8Dv+XpKAiAI
/zVFNSKs29LjiBRyEIHLy6oTXUgUpGOp6j0lUddiVNsgGKwp+e5qFYmFOYMrRlPB
FgM1ZU58tHWBvYR6U0Y819L25BQ3AuTdjbV8kKZwfzUwmQ1i1to=
=714i
-----END PGP SIGNATURE-----

Attachment: pgpqh27x8O_ou.pgp
Description: PGP signature


--- End Message ---

Reply via email to