[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#795125: transition: libassimp3 -> libassimp3v5



On 08/19/2015 09:48 AM, Simon McVittie wrote:
> On Mon, 10 Aug 2015 at 21:34:24 +0200, IOhannes m zmoelnig wrote:
>> I have uploaded "assimp_3.1.1~dfsg-4" to "experimental".
> ...
>> Please schedule binNMUs for the above mentioned packages on all architectures.
> 
> Packages in unstable are not binNMU'd against dependencies from
> experimental, and this transition is mostly about what happens in
> unstable.

yes sure.
i've uploaded to experimental in order to clear the NEW status.
my mail / this bug is mostly about coordinating the upload to unstable +
binNMU.
(i'm in the lucky position that my libs haven't needed transitions yet;
so i'm a bit of a newbie here...)

> 
> assimp does not appear to have any C++ dependencies other than libstdc++,
> and the current policy is that the v5 transitions can be started for any
> package whose dependencies have started their transitions, so please upload
> either 3.0 or 3.1.1 to unstable with the libassimp3v5 package name.
> Upload whichever version you consider to be lower-risk.

great.
in this case i will upload 3.1.1 to unstable.

mvsadr
IOhannes

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: