Your message dated Fri, 2 Nov 2012 19:00:15 -0700
with message-id
<caczd_tachxe5hpz9fcygnm2d_iss0yygnjh2gh4d0zacbnc...@mail.gmail.com>
and subject line Re: Bug#692070: Issue solved
has caused the Debian Bug report #692070,
regarding wesnoth-1.10-core: does not start, wants libpython2.5.so.1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
692070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wesnoth-1.10-core
Version: 1:1.10.4-1
Severity: grave
Justification: renders package unusable
Good evening guys,
I can't start wesnoth any more, it gives this output:
***
oxi:|home/harald > wesnoth
wesnoth: error while loading shared libraries: libpython2.5.so.1.0:
cannot open shared object file: No such file or directory
***
After I installed the python2.5 package, it finds the library, but again
does not start. The output is:
***
oxi:|home/harald > wesnoth
wesnoth: error while loading shared libraries:
libboost_iostreams-gcc42-mt-1_34_1.so.1.34.1: cannot open shared object
file: No such file or directory
***
I run an up-to-date "testing" system, wesnoth-1.10-core is the only
"experimental" package. wesnoth-1.10-core and wesnoth-1.10-data are the
only packages installed from the program. I experience the same problem
with the 1.10.3 version in testing, and even compiled the game from
sources (via apt). The same output.
It is possible that this incident is connected to a complete update to
actual "testing", first time for some months.
Please don't hesitate to ask for more info.
Thanks a lot!
Harald
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages wesnoth-1.10-core depends on:
ii libboost-iostreams1.49.0 1.49.0-3.1
ii libboost-program-options1.49.0 1.49.0-3.1
ii libboost-regex1.49.0 1.49.0-3.1
ii libboost-system1.49.0 1.49.0-3.1
ii libc6 2.13-35
ii libcairo2 1.12.2-2
ii libdbus-1-3 1.6.8-1
ii libfontconfig1 2.9.0-7
ii libfribidi0 0.19.2-3
ii libgcc1 1:4.7.1-7
ii libglib2.0-0 2.33.12+really2.32.4-2
ii libgomp1 4.7.1-7
ii libice6 2:1.0.8-2
ii libpango1.0-0 1.30.0-1
ii libsdl-image1.2 1.2.12-2
ii libsdl-mixer1.2 1.2.12-3
ii libsdl-net1.2 1.2.8-2
ii libsdl-ttf2.0-0 2.0.11-2
ii libsdl1.2debian 1.2.15-5
ii libsm6 2:1.2.1-2
ii libstdc++6 4.7.1-7
ii libx11-6 2:1.5.0-1
ii libxext6 2:1.3.1-2
ii wesnoth-1.10-data 1:1.10.4-1
wesnoth-1.10-core recommends no packages.
Versions of packages wesnoth-1.10-core suggests:
pn wesnoth <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Nov 2, 2012 at 1:59 PM, Harald Tlatlik <har...@gehirnspen.de> wrote:
> Dear Vincent,
>
> thanks to your hint it's working again. I had a years-old
> manual installation in my local tree which I could not remember at all.
> For some reasons I don't know it was "re-activated" during my system
> actualisation.
Maybe you (inadvertently) changed the precedence of the dirs in your
$PATH? I've no idea otherwise.
> Once more, thanks for helping so fast. How can I close this thread?
No problem, glad I could help!
I've closed this bug report for you. For your future reference, you
can easily close a bug report by sending a message to
######-d...@bugs.debian.org.
Regards,
Vincent
--- End Message ---
