Your message dated Wed, 22 Jun 2022 16:34:01 +0000
with message-id <e1o43in-0001d0...@fasolo.debian.org>
and subject line Bug#1012494: fixed in gdb 12.1-1
has caused the Debian Bug report #1012494,
regarding gdb: FTBFS on ppc family: No rule to make target 'info' in 
build/default/sim/ppc
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.)


-- 
1012494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdb
Version: 11.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-powe...@lists.debian.org
User: debian-powe...@lists.debian.org
Usertags: ppc64el powerpc ppc64

gdb 11 is not migrating to testing because the ppc64el build is missing:

> make[3]: Leaving directory '/<<PKGBUILDDIR>>/build/default/gnulib'
> Doing info in sim
> make[3]: Entering directory '/<<PKGBUILDDIR>>/build/default/sim'
> Making info in ppc
> make[4]: Entering directory '/<<PKGBUILDDIR>>/build/default/sim/ppc'
> make[4]: *** No rule to make target 'info'.  Stop.
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/build/default/sim/ppc'
> make[3]: *** [Makefile:1271: info-recursive] Error 1
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/build/default/sim'
> make[2]: *** [Makefile:8088: info-sim] Error 1
> make[2]: Leaving directory '/<<PKGBUILDDIR>>/build/default'
> make[1]: *** [Makefile:984: do-info] Error 2
> make[1]: Leaving directory '/<<PKGBUILDDIR>>/build/default'
> make: *** [debian/rules:233: stamps/build-default] Error 2
— 
https://buildd.debian.org/status/fetch.php?pkg=gdb&arch=ppc64el&ver=11.2-1&stamp=1651406483&raw=0

The non-release architectures powerpc and ppc64 seem to have the same bug.

If there's no obvious nice solution, it might be possible to mitigate
this by only enabling the texinfo documentation when asked to build
Architecture: all packages, which in practice get built on an x86 buildd?

    smcv

--- End Message ---
--- Begin Message ---
Source: gdb
Source-Version: 12.1-1
Done: Héctor Orón Martínez <zu...@debian.org>

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

Debian distribution maintenance software
pp.
Héctor Orón Martínez <zu...@debian.org> (supplier of updated gdb 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: Wed, 22 Jun 2022 18:10:19 +0200
Source: gdb
Architecture: source
Version: 12.1-1
Distribution: unstable
Urgency: medium
Maintainer: Héctor Orón Martínez <zu...@debian.org>
Changed-By: Héctor Orón Martínez <zu...@debian.org>
Closes: 1001561 1012494
Changes:
 gdb (12.1-1) unstable; urgency=medium
 .
   * Remove and thank Riku Voipio for past contributions
     (Closes: #1001561)
   * Bump standards version, no changes
   * New upstream release.
     (Closes: #1012494)
   * debian/patches: refresh, merged upstream gdb_bsd support
Checksums-Sha1:
 e30f1872598e87999abb22c1a842f8f40594fd9a 2855 gdb_12.1-1.dsc
 0bde03844c88fce5c8d3000fa419f53076a019cb 22940352 gdb_12.1.orig.tar.xz
 bc9f4dc85fce7a25f4e43b51758200f580d983ec 195 gdb_12.1.orig.tar.xz.asc
 bc861e20a667aca081e0ddc13eb966e7a1097905 286420 gdb_12.1-1.debian.tar.xz
 3fcee6747e28b3334f6ea4ed78b52750465671b1 10001 gdb_12.1-1_source.buildinfo
Checksums-Sha256:
 f5d6d76793a7e2678c8a02d7c51983408e58acac8d4f724e9e17c1faf1da3010 2855 
gdb_12.1-1.dsc
 8e439ae59180f07b8408c55af7762aadf3832d644808fc2ce31ad5caa30dc98a 22940352 
gdb_12.1.orig.tar.xz
 94a6fd40d0875155a1ce904071f6c23d4e33a77d10a6640821ae14df1b2495a7 195 
gdb_12.1.orig.tar.xz.asc
 4bbcc98c93a910910fa775a32a4947f2add0df31545bc372c4f1adf9ddcc191f 286420 
gdb_12.1-1.debian.tar.xz
 15893ab95b42088ddc188d7ff940d487936395c0430f609c2456ad2cf189fb1a 10001 
gdb_12.1-1_source.buildinfo
Files:
 7d0c04d451282bb639454a7213f04e87 2855 devel optional gdb_12.1-1.dsc
 2ba8d242d5556328902e7468294c062e 22940352 devel optional gdb_12.1.orig.tar.xz
 14ee505e98d0fe830594f7ac51051375 195 devel optional gdb_12.1.orig.tar.xz.asc
 9f913d93fcc70d2294b043b825738ec1 286420 devel optional gdb_12.1-1.debian.tar.xz
 036c8030859dcf3c003cfeaacafffd65 10001 devel optional 
gdb_12.1-1_source.buildinfo

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

iQIzBAEBCgAdFiEE6Q8IiVReeMgqnedOryKDqnbirHsFAmKzP18ACgkQryKDqnbi
rHtbPg/9F4C9eOLWwjtKQq3F/4Q0DU2QGIxcRoMw0eXP7vrvv+mJpxMlFUR7rTJh
duRfDEXahKX2zha6kB5Exdr7WlCrt8k8jJjqmdPE1XFPYuiQVH5lkGaWUErPDdMz
F9rdoRNl8vo2sF2Mf/xIHnRL3rq8D0FjXBhuEkroUsKB584ezpCMokL6C1/0jQqA
Yw+LdV4hvYA5ysfECwttf8QAtD9lz2o5M1B7vpqFwXEiP0krpuK4FNI4+WNqGEIT
Wsv1BpgZwp+jf/AMXrXV3Q0x0EblOMiNND5GXyqzxpO1J51kWhWUIfcA7l+vewGX
A8eE6Q4j2EnDqJ2yvnYa9WUeKfo6USi9i2BbioCbsfT3LM5LHMZD55wdOgt52+6T
AUqdXHChIOUcHRirIzg5fV9s+Cjw7x5Whs8gOAihlwnZImH0kh6jjHGBs+HKc9L9
p9ZOISbJ+mUHAeUSy81uqf0IbWJpBXMU08CPoi/RG28ZUDv9rBfMdeldIJzyer6R
NKMYKKKbYR/dPLAitDCKLv6kfrf90muVeQAZ0JncOLb6HUAVkBzlblnN/jC9ta3y
0xDiz8vy3kiTCCAdVBM41UtVKZEZ3wtZ3O/NhwJxRaB4zbuyOBxzPSuhyfg2R5ce
4rfFsytlGX6EAo9jWsw4uclWuZZGKrPZ3WiDjELUrldiwpJb6NU=
=rU9T
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to