Re: Log for attempted build of jformatstring_0.10~20131207-1 on m68k (dist=unstable)
- To: Shuxiong Ye <yeshuxiong@gmail.com>
- Cc: debian-68k@lists.debian.org
- Subject: Re: Log for attempted build of jformatstring_0.10~20131207-1 on m68k (dist=unstable)
- From: Thorsten Glaser <tg@mirbsd.de>
- Date: Sat, 17 Jan 2015 09:26:47 +0000 (UTC)
- Message-id: <[🔎] Pine.BSM.4.64L.1501170924550.11367@herc.mirbsd.org>
- In-reply-to: <CA+OQwf8HZtsiAXXJbANkFfsAXd46dk_JsHqcF+f4WLre1Qk0UQ@mail.gmail.com>
- References: <20150115144728.BBE63BF@ara5.mirbsd.org> <Pine.BSM.4.64L.1501152346350.22679@herc.mirbsd.org> <CA+OQwf8HZtsiAXXJbANkFfsAXd46dk_JsHqcF+f4WLre1Qk0UQ@mail.gmail.com>
Shuxiong Ye dixit:
>I don't have any m68k, and can not reproduce this problem.
Right, that’s what the buildd network is for ;-)
>Could you paste more details about this failure?
All information I have is the buildd log:
http://buildd.debian-ports.org/status/fetch.php?pkg=jformatstring&arch=m68k&ver=0.10%7E20131207-1&stamp=1421333255
If you need more information, you need to modify debian/rules
in your package to emit them in the case of build failure, then
upload to unstable.
However, you can also send packages to test into my general
direction, and I can try to build them manually.
bye,
//mirabilos
--
Yay for having to rewrite other people's Bash scripts because bash
suddenly stopped supporting the bash extensions they make use of
-- Tonnerre Lombard in #nosec
Reply to: