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

Bug#648775: transition: mono 2.10



block 648775 by 649339
thanks

On 2011-11-14 23:42, Iain Lane wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> [ re-filing as a bug per jcristau ]
> 
> We'd like to start the Mono transition[0,0.5] soon.
> 

Hi,

Sorry for the delay in getting back to you.  As far as I can tell, the
mono transition shares packages with the vtk8.5 transition, but we will
let you know when we can stat this.

If you haven't already done so, please head to [1] (or [2]) to verify
the list of affected source packages.


> The packages have been aged in experimental for some time now, and this
> transition has also taken place in Another Place with no notable
> badness.
> 

Sounds good.  :)

> Following the RT's request for a dry run (Model 3 in [0.5]), Julian
> Taylor did a test rebuild[1] of all rdepends and to the best of our
> knowledge we have resolved the outstanding issues so that all that
> should be required are no-change rebuilds or uploads from experimental
> to unstable, as well as one removal of a package not yet ported
> (dlr-languages).
> 
> Roughly, the plan will be
> 
>   * Upload all of mono & cli-common from experimental to unstable
>   * Upload build tools (nant)
>   * Remove mono-debugger
>   * Get LO bindings disabled
>   * No-change rebuild / binNMU all applications against the 4.0
>     profile
>   * No-change rebuild / binNMU all libraries against the 4.0 profile, in
>     leaf-first order 
> 

Do you have a list/table of the ~30 binNMUable packages that tells us
which of them are libs and which are not?  Alternatively can we just go
by "dependency level" from the transition tracker package (starting with
the bottom/level 10)?

> The reason for this ordering is because 4.0 executables can load 2.0
> libraries but not vice-versa. A great deal of packages are pure managed
> code, so arch:all and will therefore require sourceful uploads.
> 
> You can see the results of our testing at [2].
> 
> Please let us know when we can go ahead.
> 
> Cheers,
> on behalf of the Debian Mono Group,
> 

~Niels

[1] http://release.debian.org/transitions/html/mono.html

[2] http://release.debian.org/transitions/export/packages.yaml




Reply to: