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

Bug#648775: marked as done (transition: mono 2.10)

Your message dated Fri, 03 Feb 2012 22:11:32 +0000
with message-id <1328307092.2771.2.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#648775: Mono 2.10 Transition has started (was Re: Bug#648775: transition: mono 2.10)
has caused the Debian Bug report #648775,
regarding transition: mono 2.10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
648775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648775
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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.

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.

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 
    
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,

-- 
Iain Lane                                  [ iain@orangesquash.org.uk ]
Debian Developer                                   [ laney@debian.org ]
Ubuntu Developer                                   [ laney@ubuntu.com ]
PhD student                                       [ ial@cs.nott.ac.uk ]

[0] http://release.debian.org/transitions/html/mono.html
[0.5] http://wiki.debian.org/Teams/DebianMonoGroup/Mono210Transition
[1] http://alioth.debian.org/~jtaylor-guest/logs/
[2] http://wiki.debian.org/Teams/DebianMonoGroup/Mono210TransitionTODO

--- End Message ---
--- Begin Message --- 
On Mon, 2012-01-30 at 12:57 +0000, Adam D. Barratt wrote:
> On 16.01.2012 06:33, Mirco Bauer wrote:
> > Alright, I have uploaded Mono 2.10.5-2 and cli-common 0.8 to
> > unstable. This officially starts the Mono 2.10 transition in Debian
> 
> I mentioned most of the below on #debian-release over the weekend, but 
> thought it might be easier to document it in the transition bug as well. 
>  From a base of this morning's britney result, with a bunch of urgents 
> and a force-hint applied, the end result of attempting to get the 
> transition done now appears to be that the following packages have 
> issues:
[...]
> * s390:
>    - libvirtuoso5.5-cil
>      - virtuoso-opensource needs to stop building CIL packages on s390; 
> #657781

Jo's NMU for this is still pending, so this is indeed broken for a short
time.  In the meantime:

      mono |   2.10.5-2 |       testing | source

I think we can call this done, and let the slides be basically
truthful. ;-)

Regards,

Adam

--- End Message ---
Reply to: