Bug#984275: openmw is marked for autoremoval from testing

This bug is resolved with the release of OpenMW 0.47 which is waiting in the wings for approval and upload: https://salsa.debian.org/games-team/openmw It relies on: * recastnavigation being uploaded to Debian: https://mentors.debian.net/package/recastnavigation/ * MyGUI 3.4 being uploaded to

Bug#961536: openmw FTBFS with openscenegraph 3.6.5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Sebastian, On 2020-06-11 at 20:28, sramac...@debian.org wrote: > Hi Bret > > The build on mipsel failed: > https://buildd.debian.org/status/fetch.php?pkg=openmw=mipsel=0.46.0-1=1591883193=0 > > It's missing -latomic. But I'm wondiering if it

Bug#961536: openmw FTBFS with openscenegraph 3.6.5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Sebastian, On 2020-06-11 at 09:11, sramac...@debian.org wrote: > Hi bret > > On 2020-06-09 18:28:02 +0200, bret curtis wrote: > > OpenMW 0.46 has been released and I've uploaded it here, it just > > someone kind and just

Bug#961536: openmw FTBFS with openscenegraph 3.6.5

OpenMW 0.46 has been released and I've uploaded it here, it just someone kind and just to review and upload. :) https://salsa.debian.org/games-team/openmw Once uploaded and built, this bug should be closed. Cheers, Bret

Bug#961536: openmw FTBFS with openscenegraph 3.6.5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 That's a pity but give a few more days and 0.46 will be released. No point in patching and going through this whole process again, I'll make sure everything is ready to go to to upload. Cheers, Bret -BEGIN PGP SIGNATURE- Version: FlowCrypt

Bug#958917: openmw: random crashes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, yes this is a known issue and someone needs to trigger a rebuild once OSG 3.6.5 gets out of experimental. This is related to bug #945875 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945875 Again, this is pretty urgent because it also

Bug#945875: openmw: Crash when saving

On Fri, 27 Mar 2020 at 09:29, Alberto Luaces wrote: > > On 27/3/20 8:26, Bret Curtis wrote: > > The best way forward in resolving this bug is to get OpenSceneGraph > > package bumped to 3.6.5 right away. This requires the help of Alberto > > Fernández, it's packa

Bug#945875: openmw: Crash when saving

On Sun, 22 Dec 2019 11:01:55 +0100 Mel Collins wrote: > I also recently encountered this. > > It appears that there's been an update which reverts to the earlier > version of OpenSceneGraph, but at the time of writing it's still > awaiting a release, according to the package tracker: > >

Bug#914537: openmw: segfault at start

Thanks Fred! We're tracking it upstream. Will keep this bug posted with results. https://gitlab.com/OpenMW/openmw/issues/4737 Cheers, Bret

Bug#885401: openmw uninstallable

://qa.debian.org/cgi-bin/vcswatch?package=wildmidi <-- this has nothing to with OpenMW but is a new upstream release that I maintain. :) Cheers, Bret On Thu, Dec 28, 2017 at 5:49 PM, Markus Koschany <a...@debian.org> wrote: > On Thu, 28 Dec 2017 12:47:01 +0100 bret curtis <psi...@g

Bug#885401: openmw uninstallable

Hello Bret, There are two things going on here. One is that libopenscenegraph needs to be rebuilt since that specific (version) gdal package (so many dependencies down) is no longer available. Look at the apt output, OSG depends on gdal-abi. The second problem is that openmw on Debian is two

Bug#871299: libmyguiengine3debian1v5: requires rebuild against GCC 7 and symbols/shlibs bump

Hello, I've hopefully addressed the issues brought up and made an additional commit/push. Can you review and see if this is correct and ready for upload? I have no access. Cheers, Bret On Mon, Sep 25, 2017 at 11:31 AM, Simon McVittie wrote: > On Mon, 07 Aug 2017 at 15:47:16

Bug#850021: openmw: FTBFS on armhf: error: 'GL_AMBIENT' was not declared in this scope

Known issue, please read this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838792 Summation: OSG is being built with libGLESv2 and not with libGL on armhf, OpenMW doesn't support GLESv2, nor GLESv1. If we 'fix' the build issue, OpenMW will run, but you only see a black screen. OSG is

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

Hello everyone, this is a follow-up email because while the bug was closed and OpenMW compiles (and runs) on armhf, what is rendered to the screen via OSG-3.4 is everything but pretty. The short term solution is to disable building OpenMW on armhf and rebuild any builds still online. I have more

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

With the attached patch to OSG, I can get it to compile on armhf with GLESv1 (libgles1-mesa-dev). It disables GLESv2 however, I got an error while they were both enabled. I installed the resulting packages on my RPi2 without a problem and got OpenMW to compile on there as well. Was there a

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

On Wed, Sep 28, 2016 at 9:34 AM, Alberto Luaces <alua...@udc.es> wrote: > Andreas Beckmann writes: > >> On 2016-09-27 12:12, bret curtis wrote: >>> To put it simply, upstream (OpenMW) has no plans to support GLESv2 at >>> this time. Since OSG-3.4 f

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

Hello, To put it simply, upstream (OpenMW) has no plans to support GLESv2 at this time. Since OSG-3.4 for armhf is compiled only for GLESv2, this complicates things drastically and at this point I'm in over my head. If we try to switch out with , we clear up the above error but then it fails

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

We know what the problem is and are working on it. Please see the following: https://anonscm.debian.org/cgit/pkg-osg/openscenegraph-3.4.git/commit/?id=fa5b1385d2b82f3fec9cc6094fb3db498a36a9e3 OSG-3.4 had the same problem until this was commited, now the package builds and OpenMW was unblocked.

Bug#834251: openmw: FTBFS with GCC 6

We're aware of the problem and version 0.39 has been waiting in the upload queue for ages now awaiting someone to upload it. [1] With the 0.39 release, it no longer uses unordered maps. We're also about to make another release (0.40) shortly... we're just short in people willing to upload our

Bug#756066: [libopenal1] Unable to install amd64 next to i386 library

Please do, Scott has been busy lately so I've (and OpenAL-Soft) have been in purgatory for a few days now. Thank you for helping out! Cheers, Bret On Mon, Jul 28, 2014 at 11:20 AM, Simon McVittie s...@debian.org wrote: severity 756066 serious found 756066 openal-soft/1:1.15.1-2 notfound

Bug#755846: libroar2: no multiarch possible

Hey there... an openal-soft maintainer here (who also works closely with openal-soft upstream), On Fri, Jul 25, 2014 at 3:20 PM, Philipp Schafft l...@lion.leolix.org wrote: reflum, On Fri, 2014-07-25 at 09:47 +0100, Simon McVittie wrote: affects 755846 libopenal1 thanks I will have a look