Please sync wesnoth-1.8 1:1.8.3-1 (universe) from Debian unstable (main)

Bug #603206 reported by Alexander Kowalski
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
wesnoth-1.8 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: wesnoth-1.8

Please sync wesnoth-1.8 1:1.8.3-1 (universe) from Debian unstable (main).

This is a new maintenance release for wesnoth-1.8 which fixes some bugs.

Changelog:
 wesnoth-1.8 (1:1.8.3-1) unstable; urgency=low

   * New upstream release
   * Really enable DEB_BUILD_OPTIONS="parallel=X" in debian/rules.
   * unpatch after cleaning, not before.
   * Have its own configure target.
   * Put make depends on build where it belongs.

 -- Gerfried Fuchs <email address hidden> Tue, 06 Jul 2010 17:42:53 +0200

There are no Ubuntu-specific changes to this package and I can confirm that building and running the package works on maverick amd64.

Tags: sync
Revision history for this message
Alexander Kowalski (alexanderk167-deactivatedaccount) wrote :

build log

Revision history for this message
Rhonda D'Vine (rhonda) wrote : Re: [Bug 603206] [NEW] Please sync wesnoth-1.8 1:1.8.3-1 (universe) from Debian unstable (main)

 Hi!

 First of all, thanks for being faster than myself. ;)

* Alexander Kowalski <email address hidden> [2010-07-08 17:21:04 CEST]:
> Please sync wesnoth-1.8 1:1.8.3-1 (universe) from Debian unstable
> (main).
>
> This is a new maintenance release for wesnoth-1.8 which fixes some bugs.

 Right.

> As it seems there are problems with using this version in a multiplayer
> game together with the current one in maverick, I think it should be
> updated. There are no Ubuntu-specific changes to this package and I can
> confirm that building and running the package from sid works on maverick
> amd64.

 I don't understand this comment. What problems do you see there?
Upstream works explicitly to _not_ have any troubled along that lines in
their stable releases and I am not aware of any - can you base this
remark on something, because it makes it sound like there are some.

 Would be really interested to know about them, from both a packager
point of view but also from my involvment with upstream.

 Thanks in advance,
Rhonda
--
"Lediglich 11 Prozent der Arbeitgeber sind der Meinung, dass jeder
Mensch auch ein Privatleben haben sollte."
        -- http://www.karriere.at/artikel/884/

Revision history for this message
Alexander Kowalski (alexanderk167-deactivatedaccount) wrote :

Some days ago, I played a game on the multiplayer server against someone using 1.8.3 (and some others with 1.8.2) and the chat was flooded with out of sync errors about five times. They were related to some differences in units and I think there were also some strange things with the HP. I don't know if the different versions caused this (maybe someone just tried to cheat), but as it was the 1.8.2 versions which were out of sync, I thought that could be the problem. If that's not the case, I'm sorry for the mistake.

Revision history for this message
Rhonda D'Vine (rhonda) wrote : Re: [Bug 603206] Re: Please sync wesnoth-1.8 1:1.8.3-1 (universe) from Debian unstable (main)

 Hi!

* Alexander Kowalski <email address hidden> [2010-07-09 13:31:14 CEST]:
> Some days ago, I played a game on the multiplayer server against someone
> using 1.8.3 (and some others with 1.8.2) and the chat was flooded with
> out of sync errors about five times. They were related to some
> differences in units and I think there were also some strange things
> with the HP. I don't know if the different versions caused this (maybe
> someone just tried to cheat), but as it was the 1.8.2 versions which
> were out of sync, I thought that could be the problem. If that's not the
> case, I'm sorry for the mistake.

 It is much more likely that the OOS was related to something else like
a broken addon. It would be great if you could file that (including the
savegame) as a seperate bug - but it is highly unlikely that it was
related to 1.8.2 vs 1.8.3, I just asked upstream explicitly about it and
got confirmed that they carefully checked the commits.

 Also, the upstream changelog is pretty verbose this time about the
changes that have been made so you can check against that, too.

 So in case you have something to base it on please submit it for
investigation because if that would really be the case it has to get
addressed explicitly and be fixed/reverted in another update. Upstream
isn't aware of such an issue though, and like written, explicitly work
on avoiding such issues.

 Thanks,
Rhonda
--
"Lediglich 11 Prozent der Arbeitgeber sind der Meinung, dass jeder
Mensch auch ein Privatleben haben sollte."
        -- http://www.karriere.at/artikel/884/

Revision history for this message
Alexander Kowalski (alexanderk167-deactivatedaccount) wrote :

The first OOS was because of the checksum of an Orcish Grunt, but after the second (which I can't remember any more) I selected "Ignore All", so I don't know about the other errors. Unfortunately I also don't have a savegame (searched the wesnoth directory, but couldn't find one of that game), so I can't help with more information than that. However, if I encounter something like that again, I'll keep track of it.

Revision history for this message
Alexander Kowalski (alexanderk167-deactivatedaccount) wrote :
Revision history for this message
Rhonda D'Vine (rhonda) wrote :

 Hi again!

* Alexander Kowalski <email address hidden> [2010-07-09 14:58:11 CEST]:
> Probably that's it:
> http://forum.wesnoth.org/viewtopic.php?f=19&t=25274&start=645

 Thanks for digging it up and reassuring that it doesn't seem to be an
issue in wesnoth itself. :)

 Enjoy!
Rhonda

description: updated
Revision history for this message
Rhonda D'Vine (rhonda) wrote :

ACK the sync request

Changed in wesnoth-1.8 (Ubuntu):
status: New → Confirmed
status: Confirmed → New
status: New → Confirmed
Revision history for this message
Jonathan Riddell (jr) wrote :

[Updating] wesnoth-1.8 (1:1.8.2-1 [Ubuntu] < 1:1.8.3-1 [Debian])
 * Trying to add wesnoth-1.8...
2010-07-14 10:08:00 INFO - <wesnoth-1.8_1.8.3-1.dsc: downloading from http://ftp.debian.org/debian/>
2010-07-14 10:08:00 INFO - <wesnoth-1.8_1.8.3-1.diff.gz: downloading from http://ftp.debian.org/debian/>
2010-07-14 10:08:00 INFO - <wesnoth-1.8_1.8.3.orig.tar.gz: downloading from http://ftp.debian.org/debian/>
I: wesnoth-1.8 [universe] -> wesnoth-1.8-data_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-core_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-dbg_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-music_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-server_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-tools_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-httt_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-tsg_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-trow_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-ttb_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-ei_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-utbs_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-did_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-nr_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-sof_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-sotbe_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-l_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-aoi_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-thot_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-low_1:1.8.2-1 [universe].
I: wesnoth-1.8 [universe] -> wesnoth-1.8-dm_1:1.8.2-1 [universe].

Changed in wesnoth-1.8 (Ubuntu):
status: Confirmed → 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.