Thank you again. It does seem that my package mix-up was the culprit somehow.
Unfortunately I don't have more time to look into the issue - I just posted the bug report thinking this was a issue everyone would have when downloading the amd64 package. It seems I was wrong but the intentions were good :) On 7 May 2015 at 18:29, Bernhard Übelacker <bernha...@vr-web.de> wrote: > Hello Alex, > > One last question: did you try to install the amd64 version specifically? >> I'm not sure how the multi-arch support works these days. If not, would it >> be easy for you to try to do it? >> > Yes, my tests were done on my regular amd64 desktop installation. > That was with widelands_18-3+b1_amd64.deb. > > > Thank you for taking the time to look into the issue! I wish I could >> downgrade the libboost packages needed to compile the source code to see >> if >> the build would have the bug or not. They are not in the dependencies but >> are on the build-deps: >> https://packages.debian.org/source/jessie/widelands >> >> I am actually running Squeeze with some packages from Stretch. >> >> I did a manual build from the source code and the game runs fine, with >> these exact packages you listed for me. I am still suspecting the problem >> to be libboost (check the bug report I mentioned earlier for why) even >> though I can't be sure. I guess I should probably close the bug if we >> cannot reproduce it, since it could be due to my weird package mix? >> > > For the fun of it I tried to really reproduce the situation (qemu-VM): > - installed Squeeze LTS with LXDE > - added Stretch sources.list > > But I was not able to cleanly install widelands via apt. > Trying to manually installing via dpkg led also to some (for me) > unresolvable dependencies (without doing nearly half of the dist-upgrade). > Therefore I am short before thinking that now your package system is in an > inconsistent state. > > > > Unfortunately I got myself into a sort of a deadlock with that and > > need to reinstall the system from scratch. > > As I think you also did a libc-upgrade (2.11.3-4+deb6u5 to 2.19-18 ?) > I cannot say how a downgrade of it has to be done. > Probably a dist-upgrade to Jessie or Stretch could work ... > (But for this to work the package system needs to be consistent - you have > checked what "apt-get install -f" proposes?) > > --------- > > At least, the problem this report was opened for seems to be a result of > the package mix of Squeeze and Stretch. > > Kind regards, > Bernhard >
