Bug#649718: FTBFS: cat(EPIPE) | (SIGABRT) GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guild snarf-check-and-output-texi

[Thorsten Glaser]

Adam D. Barratt dixit:

Also, failures on non-release architectures are severity important, not

No disagreement from me.

archive might even be lower.  Please do not file m68k-specific bugs as
RC; thanks.

Tell that reportbug. I chose severity FTBFS.

(In the future I’ll try to remember to manually edit that
field before sending the mail.)

bye,
//mirabilos
-- 
  “Having a smoking section in a restaurant is like having
  a peeing section in a swimming pool.”
-- Edward Burr



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#649718: FTBFS: cat(EPIPE) | (SIGABRT) GUILE_AUTO_COMPILE=0 ../meta/uninstalled-env guild snarf-check-and-output-texi

[Adam D. Barratt]

severity 649718 important
thanks

On Wed, 2011-11-23 at 11:44 +, Thorsten Glaser wrote:
 Package: guile-2.0
 Version: 2.0.3+1-2
 Severity: serious
 Justification: fails to build from source (but built successfully in the past)
 
 Hi,
 
 guile-2.0 no longer builds; it aborts somewhere in the middle.
[...]
 -- System Information:
 Debian Release: wheezy/sid
   APT prefers unreleased
   APT policy: (500, 'unreleased'), (500, 'unstable')
 Architecture: m68k

https://buildd.debian.org/status/logs.php?pkg=guile-2.0 quite clearly
shows that the package *does* build on several architectures, and a
little further investigation shows that it has never built on the other
architectures so the failures do not constitute a regression.

Also, failures on non-release architectures are severity important, not
RC.  Arguably failures on architectures which aren't in the Debian
archive might even be lower.  Please do not file m68k-specific bugs as
RC; thanks.

Regards,

Adam




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org