Bug#704044: Bug#705010: mygui: Please upgrade OGRE dependency to 1.8 or greater

[Manuel A. Fernandez Montecelo]

2013/4/8 Scott Howard <showard314 at gmail.com>:
>> 2013/4/8 Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>:
>>> 2013/4/8 Scott Howard <showard314 at gmail.com>:
>>>> Thanks for the heads up, the package is ready for ogre 1.8 so a simple
>>>> binNMU should build it against the new library.
>>>
>>> I am not sure that having a generic "-dev" is useful for this library
>>> and perhaps I will remove it completely.
>>>
>>> For several releases now people had to modify their projects to adapt
>>> it to new versions of OGRE, upstream doesn't pay much attention to
>>> backward-compatibility (or ignore it on purpose).
>>>
>>> So you might need to change Build-Depend for libogre-1.8-dev or
>>> whatever is appropriate.
>
> Hi Manuel,
> I want to clarify the transition schedule so I know what you want us
> depending packages to build against:
>
> after Wheezy release:
> libogre-dev will be removed
> libogre1.7-devremoved
> libogre1.9-dev added
> libogre1.8-dev will be version 1.8.1 (I guess binNMU depending
> packages that depend on libogre1.8.0?)
>
> prior to jesse release:
> libogre1.8-dev removed

That's the general idea, yes.

The final set of packages depends on what OGRE devs decide to do and
what's available at the time of the next freeze.  Maybe 1.8 is also
removed, maybe even 1.9 is removed if 2.0 is available and all the
other Debian packages can be built against it...

As you know, in general it's better idea that Debian releases have
only versions supported by upstream, and to have only as few versions
of the same basic package as necessary.


> so after wheezy, no more libogre-dev and depending packages should
> build against one of the librogre1.*-dev
> but prior to jessie, all packages will migrate over to libogre1.9-dev

Again yes -- if possible at all.


> If this is true, I can build mygui against libogre1.8-dev. I'm going
> to be away from keyboard for a bit, if you need to do an NMU please go
> ahead with a low-threshold. If it's still outstanding when I get back,
> then I'll just take care of it.

Don't worry too much, there's no urgency nor need for NMU.  I
submitted the bug to inform involved maintainers, to serve as reminder
and to keep track of the status linked to the request from boost
maintainers.

Since mygui is only in unstable and will not be shipped with wheezy,
you can do it at any moment, not necessary to wait for the freeze.
But there's plenty of time.  Other packages depending on 1.7 have to
wait for the freeze and probably will need quite more time after that.


Cheers and thanks.
--
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>