Please sync wesnoth 1:1.4.7-3 (universe) from Debian unstable (main).

Bug #307966 reported by Dara Adib
4
Affects Status Importance Assigned to Milestone
wesnoth (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: wesnoth

Please sync wesnoth 1:1.4.7-3 (universe) from Debian unstable (main).

Note: 1:1.4.7-3 and 1:1.4.7-1 are identical; 1:1.4.7-3 reverts the change made in 1:1.4.7-2

Debian Changelog since current jaunty version 1:1.4.6-1:

wesnoth (1:1.4.7-3) unstable; urgency=low
   * Revert change in last revision - it would impose a compatibility issue.
     Will be fixed with first release candidate of 1.6.

wesnoth (1:1.4.7-2) unstable; urgency=low
   * Fetch upstream revision 28805 to allow recruit more than 99 castle tiles
     away (LP: #256345). Have fun, Toni!

wesnoth (1:1.4.7-1) unstable; urgency=low
   * New stable upstream release, bugfixes and translation updates, fixing:
     - gcc 4.4 FTBFS (closes: #505957)

Upstream Changelog since Wesnoth 1.4.6:

Version 1.4.7:
 * campaigns:
   * Descent into Darkness
     * fixed bats crashing through the ice in 'Beginning of Revenge' (bug
  #12685)
   * Heir to the Throne:
     * Added an idle animation for L2 Princess.
 * graphics:
   * new or updated unit frames: Gryphon Rider, Gryphon Master
 * language and i18n:
   * updated translations: Danish, Finnish, Hungarian, Italian
 * miscellaneous and bug fixes:
   * replace a #elif without condition with #else (debian patch #505957)
   * fixed campaign replays (bug #12005)
   * start-of-scenario saves are properly marked as such

Dara Adib (daradib)
Changed in wesnoth:
importance: Undecided → Wishlist
Revision history for this message
Daniel Holbach (dholbach) wrote :

We're not in Debian Import Freeze yet and the version in Ubuntu is unmodified, so it will be automatically synced anyway.

https://wiki.ubuntu.com/JauntyReleaseSchedule
https://wiki.ubuntu.com/SyncRequestProcess

Revision history for this message
Daniel Holbach (dholbach) wrote : ACK of sync request

ACKed.

Revision history for this message
Steve Langasek (vorlon) wrote :

Not sure why this was acked given that it was already autosynced. Nothing to do here.

Changed in wesnoth:
status: New → Fix Released
Revision history for this message
Dara Adib (daradib) wrote :

When it was acked (14 hours ago) it had not yet been autosynced (10 hours ago).

Thanks Daniel Holbach.

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.