[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#954520: marked as done (yiyantang: FTBFS: setty.c:31:10: fatal error: stropts.h: No such file or directory)



Your message dated Sun, 05 Apr 2020 00:49:32 +0000
with message-id <E1jKtTg-000HLD-VQ@fasolo.debian.org>
and subject line Bug#954520: fixed in yiyantang 0.7.0-6
has caused the Debian Bug report #954520,
regarding yiyantang: FTBFS: setty.c:31:10: fatal error: stropts.h: No such file or directory
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 owner@bugs.debian.org
immediately.)


-- 
954520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954520
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: yiyantang
Version: 0.7.0-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely due to the upgrade to glibc 2.30. 
>From https://lists.gnu.org/archive/html/info-gnu/2019-08/msg00000.html:
> * The obsolete and never-implemented XSI STREAMS header files <stropts.h>
>   and <sys/stropts.h> have been removed.

Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include     -DG_LOG_DOMAIN=\"yyt\"     -I../intl -I../intl  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -c setty.c
> setty.c:31:10: fatal error: stropts.h: No such file or directory
>    31 | #include <stropts.h>
>       |          ^~~~~~~~~~~
> compilation terminated.
> make[3]: *** [Makefile:201: setty.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/03/21/yiyantang_0.7.0-5_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

--- End Message ---
--- Begin Message ---
Source: yiyantang
Source-Version: 0.7.0-6
Done: Sudip Mukherjee <sudipm.mukherjee@gmail.com>

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

Debian distribution maintenance software
pp.
Sudip Mukherjee <sudipm.mukherjee@gmail.com> (supplier of updated yiyantang 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Sun, 05 Apr 2020 00:15:30 +0100
Source: yiyantang
Architecture: source
Version: 0.7.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Closes: 954520
Changes:
 yiyantang (0.7.0-6) unstable; urgency=medium
 .
   * QA upload.
   * Update Standards-Version to 4.5.0
   * Fix FTBFS. (Closes: #954520)
   * Update compat level to 12.
     - Remove dependency on autotools_dev.
     - configure without using autoreconf.
   * Add version in d/watch.
   * Add Vcs link to salsa.
Checksums-Sha1:
 11c7c7a3b4bafbd043c9c0e1e79f6a61cd6f34a2 1814 yiyantang_0.7.0-6.dsc
 34b268e48f6b4896f71b796353664120b6b6edf1 3696 yiyantang_0.7.0-6.debian.tar.xz
 bc28179fb6e9c2604ddc0e97e04c98e4287bd8f4 5806 yiyantang_0.7.0-6_amd64.buildinfo
Checksums-Sha256:
 6fb1ff431709e782dc77b9ef874724b8474330d95ddc5c27d013fd55bae19d6a 1814 yiyantang_0.7.0-6.dsc
 d16729ab03933f732742c1c09773265c875902cd6a5f029756aa548fc760f71f 3696 yiyantang_0.7.0-6.debian.tar.xz
 d912106e3c37a5548d1a7c8550b7848589b2530b2b948bd46ceb1eeeebcf15ca 5806 yiyantang_0.7.0-6_amd64.buildinfo
Files:
 264d697b986b85e5ade72f2159b69fee 1814 text optional yiyantang_0.7.0-6.dsc
 fe55d15074d676b9b166a122fff99980 3696 text optional yiyantang_0.7.0-6.debian.tar.xz
 083caac7a423d4d1bdd5382b9ad54fbd 5806 text optional yiyantang_0.7.0-6_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl6JJH0ACgkQwpPntGGC
Ws6hNA//cbMGvspK2Ytp5lvydKfeMXsYjq2K4pCezHith+HsQnkb1JVT+SAdVx7D
5L6olTtW8fv3GwEfo3UDD02ag3jVcP55tZK4WERPI1k+INiskW+pruqzMu97tIiM
VaiA4JtEF/36QarY8+ZaYEZ42/MK6VAU26x+8rDZXSZYr2NvaarsS+zb2zkvFkXm
s4REkMPm9dwTuPDX2XdvTQSrwkmTd3Wmzzi1hQc6J3REcFTFpHkUMk2YOALCqfAE
9MipLCCfUIoHYmMlwmpTEfnNcDGQSNYM49bHegChiD3f6h9oQteTjHnaHiBLwaF2
nKK96Kmbvw5ctyvpLp7GMKcjn/w7YoQ62fSULHepkJjHN7xayIwqsoIErTyAc23E
DNZLwSfXlRwsMyG791yZ+6MudimKEAapCwDw81lrHVbIlq/ezkJ6TlgvWVRLreaB
A1tmnn2yekyToAMYsvVs+bK9YZfpLD6Delt8WCjJRmdHS2oHdIvI3uIYFX0Txzvn
R+DlMZsLn8MBCM4ELIcJe5jy/SQxe9WkN79q2zWMkfeP+4dQlk/fDekpJQ3HOEn0
iS3lvZs0EiAf8kkZs5cgEPAIW1jwRFgxZvfHvYPrg62uy8nsrSe70z5i2kVJ39Mt
rzQOoFktLKQE56T1Q/pk9tLBQHVqwwm9DTXKsRALCsfPCoROsqs=
=5OZz
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: