Sync gforth 0.7.0+ds1-7 (universe) from Debian unstable (main)

Bug #1050482 reported by Logan Rosen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gforth (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Please sync gforth 0.7.0+ds1-7 (universe) from Debian unstable (main)

Changelog entries since current quantal version 0.7.0+ds1-6:

gforth (0.7.0+ds1-7) unstable; urgency=low

  * Apply an upstream patch to fix a FTBFS; Closes: #672616
    - add the 11-static-newline patch to define the system newline
      string as static
    - temporarily build-depend on the GForth interpreter to be able to
      rebuild the kernel images properly after applying the patch
    - stash and restore the generated files affected by the patch

 -- Peter Pentchev <email address hidden> Tue, 04 Sep 2012 17:52:59 +0300

Revision history for this message
Bryce Harrington (bryce) wrote :

Can confirm that the gforth currently in the archive fails to build:

  http://paste.ubuntu.com/1203589/

Whereas gforth_0.7.0+ds1-7.dsc does build.

  http://paste.ubuntu.com/1203595/

Our buildd's use an older gcc than 4.7, which sounds like the minimum version to trigger the bug, so this hasn't been breaking our actual package builds. But eliminating the FTBFS within quantal is probably worth it. +1

Revision history for this message
Bryce Harrington (bryce) wrote :

gforth (0.7.0+ds1-7) unstable; urgency=low

  * Apply an upstream patch to fix a FTBFS; Closes: #672616
    - add the 11-static-newline patch to define the system newline
      string as static
    - temporarily build-depend on the GForth interpreter to be able to
      rebuild the kernel images properly after applying the patch
    - stash and restore the generated files affected by the patch

Date: 2012-09-11 22:18:18.210801+00:00
Changed-By: Peter Pentchev <email address hidden>
Signed-By: Bryce Harrington <email address hidden>
https://launchpad.net/ubuntu/quantal/+source/gforth/0.7.0+ds1-7

Changed in gforth (Ubuntu):
importance: Undecided → High
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.