Hi,
* PJ Weisberg [2010-11-23 06:06:37 CET]:
> There was a 1.9.1-1 when I made the earlier report. I've since
> upgraded to 1.9.2-1. In order to do so, I had to install
> wesnoth-1.8-core. :-)
Right - just stating that it won't be needed for the next upgrade
because I fixed it in my codebase
There was a 1.9.1-1 when I made the earlier report. I've since
upgraded to 1.9.2-1. In order to do so, I had to install
wesnoth-1.8-core. :-)
(I didn't upgrade immediately because I was in the middle of a
campaign and other games have trained me not to upgrade when I still
care about my save fi
* PJ Weisberg [2010-11-20 23:10:17 CET]:
> From 1:1.9.1-1 to 1:1.9.2-1.
There is no 1:1.9.1-1 anymore since a while already in the pool.
Rhonda
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
>From 1:1.9.1-1 to 1:1.9.2-1.
* PJ Weisberg [2010-11-20 11:59:13 CET]:
> Actually, drop #3 from that workaround. Upgrading wesnoth-1.9-core *also*
> requires wesnoth-1.8-core to be installed. :-/
Upgrading from what to what? Actually, no, it won't. That's why this
bugreport is marked as pending, the fix has been applied to
Actually, drop #3 from that workaround. Upgrading wesnoth-1.9-core *also*
requires wesnoth-1.8-core to be installed. :-/
As a temporary workaround, until the postinst script gets fixed, you can:
1. Install wesnoth-1.8-core
2. Install wesnoth-1.9-core
3. Uninstall wesnoth-1.8-core
The Wesnoth1.9 postinst configuration script is set up to abort if
Wesnoth isn't already configured, so installing a version that does
s
Package: wesnoth-1.9
Version: 1:1.9.1-1
Severity: normal
Yes, I was very suspicious when I opened up the postinst script to try to
figure out why it failed. It says "if [ $? != 0 ]; then" in a couple of
places, but $? can NEVER be != to 0, because the 'set -e' at the top would
cause the script to
8 matches
Mail list logo
