MD 2.2 for f12

[Paul F. Johnson]

Hi,

Has anyone any objections to me pushing MD 2.2 with the plugins to f12?
If people are happy, I'll do it tonight.

There have been no stability issues with the 2.2 release that I've seen
or reported via BZ.

TTFN

Paul
-- 
Biggles was quietly reading his favourite book when Algy burst through
the door. Distracted for a moment, Biggles surveyed what had happened
and turned a page. "Algy old man" he said, clearing his throat, "use the
handle next time..." - Taken from "Biggles combs his Hair"

Agree, please push MD 2.2 for f12...thanks

Mauricio

El 09-03-2010, a las 4:24, Paul <paul(a)all-the-johnsons.co.uk&gt; escribió:

>  Hi,
>
>  Has anyone any objections to me pushing MD 2.2 with the plugins to  
>  f12?
>  If people are happy, I'll do it tonight.
>
>  There have been no stability issues with the 2.2 release that I've  
>  seen
>  or reported via BZ.
>
>  TTFN
>
>  Paul
>  -- 
>  Biggles was quietly reading his favourite book when Algy burst through
>  the door. Distracted for a moment, Biggles surveyed what had happened
>  and turned a page. "Algy old man" he said, clearing his throat, "use  
>  the
>  handle next time..." - Taken from "Biggles combs his Hair"
>  _______________________________________________
>  mono mailing list
>  mono(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/mono

[Christopher Brown]

On 9 March 2010 07:24, Paul <paul(a)all-the-johnsons.co.uk&gt; wrote:
>  Hi,
>
>  Has anyone any objections to me pushing MD 2.2 with the plugins to f12?
>  If people are happy, I'll do it tonight.
>
>  There have been no stability issues with the 2.2 release that I've seen
>  or reported via BZ. 
Thanks for giving the list a heads-up Paul - sounds good.

-- 
Christopher Brown

[Christian Krause]

Hi Paul,

On 03/09/2010 08:24 AM, Paul wrote:
>  Has anyone any objections to me pushing MD 2.2 with the plugins to
> f12?
>  If people are happy, I'll do it tonight.
>  
>  There have been no stability issues with the 2.2 release that I've seen
>  or reported via BZ. 
No objections from my side.

Are you going to push MD including all updates in one update (and so I
assume you'll use a buildroot override)?


Since there is still this open issue with the broken update path:

>  Broken packages in fedora-12-x86_64:
>
>      monodevelop-debugger-mdb-2.1.0-1.fc12.i686  requires 
mono(MonoDevelop.Debugger)
= 0:2.1.0.0
>      monodevelop-debugger-mdb-2.1.0-1.fc12.i686  requires
mono(MonoDevelop.Core) = 0:2.1.0.0
>      monodevelop-debugger-mdb-2.1.0-1.fc12.i686  requires
mono(MonoDevelop.AspNet) = 0:2.1.0.0

I would like to solve this at the same time as well. I'm currently still
talking with Michael Schwendt about the final solution, but most likely
we'll add an arch-specific Requires to monodevelop-debugger-mdb's devel
package:
>    Requires: monodevelop-debugger-mdb-devel%{?_isa} =
> %{version}-%{release} 
Please can you give me a heads-up before you finally build
monodevelop-debugger-mdb so that we can shortly talk about this bug fix?


Best regards,
Christian

[Paul F. Johnson]

Hi,

>  Are you going to push MD including all updates in one update (and so
> I
>  assume you'll use a buildroot override)? 
MD first then everything else when it's happy.

>  > Broken packages in fedora-12-x86_64:
>  >
>  >     monodevelop-debugger-mdb-2.1.0-1.fc12.i686  requires
>  mono(MonoDevelop.Debugger) = 0:2.1.0.0
>  >     monodevelop-debugger-mdb-2.1.0-1.fc12.i686  requires
>  mono(MonoDevelop.Core) = 0:2.1.0.0
>  >     monodevelop-debugger-mdb-2.1.0-1.fc12.i686  requires
>  mono(MonoDevelop.AspNet) = 0:2.1.0.0
>  
>  I would like to solve this at the same time as well. I'm currently still
>  talking with Michael Schwendt about the final solution, but most likely
>  we'll add an arch-specific Requires to monodevelop-debugger-mdb's devel
>  package:
>  >   Requires: monodevelop-debugger-mdb-devel%{?_isa} = %{version}-%{release} 
I have a feeling md-debugger-mdb 2.2-1 should fix these problems. I've
not had any reports regarding a problem with this. 

>  Please can you give me a heads-up before you finally build
>  monodevelop-debugger-mdb so that we can shortly talk about this bug fix? 
No problems.

TTFN

Paul
-- 
Biggles was quietly reading his favourite book when Algy burst through
the door. Distracted for a moment, Biggles surveyed what had happened
and turned a page. "Algy old man" he said, clearing his throat, "use the
handle next time..." - Taken from "Biggles combs his Hair"

[Christian Krause]

Hi Paul,

On 03/09/2010 09:48 PM, Paul wrote:
> > Are you going to push MD including all updates in one update (and
> so I
> > assume you'll use a buildroot override)?
>  
>  MD first then everything else when it's happy. 
But will a single update of MD not break the dependencies of the already
installed plugins? If this is the case, you should really use a
buildroot override...

> >> Broken packages in fedora-12-x86_64:
> >>
> >>     monodevelop-debugger-mdb-2.1.0-1.fc12.i686  requires
> > mono(MonoDevelop.Debugger) = 0:2.1.0.0
> >>     monodevelop-debugger-mdb-2.1.0-1.fc12.i686  requires
> > mono(MonoDevelop.Core) = 0:2.1.0.0
> >>     monodevelop-debugger-mdb-2.1.0-1.fc12.i686  requires
> > mono(MonoDevelop.AspNet) = 0:2.1.0.0
> >
> > I would like to solve this at the same time as well. I'm currently still
> > talking with Michael Schwendt about the final solution, but most likely
> > we'll add an arch-specific Requires to monodevelop-debugger-mdb's devel
> > package:
> >>   Requires: monodevelop-debugger-mdb-devel%{?_isa} = %{version}-%{release}
>  
>  I have a feeling md-debugger-mdb 2.2-1 should fix these problems. I've
>  not had any reports regarding a problem with this.  
No, most likely not. The problem is actually a multiarch issue caused by
the fact how the "mash" script (which fills the x86_64 repo) works and
the fact that in F12 we had previously only an x86 version of this
package but beginning with F13 (or even the desired update of MD in F12)
we'll have x86 and x86_64 versions.

These fact causes the following sitation:

F12: md-debugger-mdb and the -devel package are copied from the x86
directory into the x86_64 repo (since all -devel packages are copied and
the -devel will pull in the base package as dependency)

F13 (or later the update in F12):
- md-debugger-mdb-devel (x86 and x86_64) are in the x86_64 repo
- since the dependency of the devel package to its base package is in
both cases satisfied by md-debugger-mdb (x86_64), the x86 package is not
copied into the x86_64 package

Now assume, an x86_64 F12 user has installed md-debugger-mdb(x86). If he
tries to update to F13 (or does the desired MD update),
md-debugger-mdb(x86) will not be updated (there is no update available,
since there is only the x86_64 package in the x86_64 repo) and so it
will be an orphan with broken dependencies to the old MD.

I'm still discussing the best solution with Michael... ;-)


Best regards,
Christian

[Christian Krause]

Hi Paul,

On 03/09/2010 09:48 PM, Paul wrote:
>  Hi,
>  
> > Are you going to push MD including all updates in one update (and so I
> > assume you'll use a buildroot override)?
>  
>  MD first then everything else when it's happy. 
This won't work well: The problem is, that you once you push MD into
stable, the people who have monodevelop-debugger-mdb installed can't use
"yum update" anymore, since there will be a broken dependency
(md-debugger-mdb will require the old md). On the other hand, you can't
build md-debugger-mdb against the new MD since it is not yet in
updates-stable and so it is not in the buildroot.

Just do right now on a fully updated F-12 system:
- install md-debugger-mdb:
yum install monodevelop-debugger-mdb
- try to upgrade
yum update --enablerepo updates-testing monodevelop

---------------------------------
--> Running transaction check
--> Processing Dependency: mono(MonoDevelop.AspNet) = 2.1.0.0 for
package: monodevelop-debugger-mdb-2.1.0-1.fc12.i686
--> Processing Dependency: mono(MonoDevelop.Core) = 2.1.0.0 for package:
monodevelop-debugger-mdb-2.1.0-1.fc12.i686
--> Processing Dependency: mono(MonoDevelop.Debugger) = 2.1.0.0 for
package: monodevelop-debugger-mdb-2.1.0-1.fc12.i686
---> Package monodevelop.i686 0:2.2-1.fc12 set to be updated
--> Finished Dependency Resolution
monodevelop-debugger-mdb-2.1.0-1.fc12.i686 from installed has depsolving
problems
  --> Missing Dependency: mono(MonoDevelop.Debugger) = 2.1.0.0 is needed
by package monodevelop-debugger-mdb-2.1.0-1.fc12.i686 (installed)
monodevelop-debugger-mdb-2.1.0-1.fc12.i686 from installed has depsolving
problems
  --> Missing Dependency: mono(MonoDevelop.Core) = 2.1.0.0 is needed by
package monodevelop-debugger-mdb-2.1.0-1.fc12.i686 (installed)
monodevelop-debugger-mdb-2.1.0-1.fc12.i686 from installed has depsolving
problems
  --> Missing Dependency: mono(MonoDevelop.AspNet) = 2.1.0.0 is needed
by package monodevelop-debugger-mdb-2.1.0-1.fc12.i686 (installed)
Error: Missing Dependency: mono(MonoDevelop.Debugger) = 2.1.0.0 is
needed by package monodevelop-debugger-mdb-2.1.0-1.fc12.i686 (installed)
Error: Missing Dependency: mono(MonoDevelop.Core) = 2.1.0.0 is needed by
package monodevelop-debugger-mdb-2.1.0-1.fc12.i686 (installed)
Error: Missing Dependency: mono(MonoDevelop.AspNet) = 2.1.0.0 is needed
by package monodevelop-debugger-mdb-2.1.0-1.fc12.i686 (installed)
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
                        package-cleanup --dupes
                        rpm -Va --nofiles --nodigest
---------------------------------

Since this may break other updates for some users who are not
experienced enough to deal with "--skip-broken", you can't push MD alone.

Please request a buildroot overrride for MD, then build md-debugger-mdb
and then add the newly built md-debugger-mdb to the md bodhi update.

Regarding the problem with the broken update path F12->F13, I suggest to
try the following:

- please add
Requires: monodevelop-debugger-mdb-devel%{?_isa} = %{version}-%{release}
to the spec file of md-debugger-mdb
- after it got built and pushed to updates-testing we have to verify
whether the mash scripts have correctly picked up the x86 package...


Best regards,
Christian

[Christian Krause]

Hi All,

On 03/09/2010 08:24 AM, Paul wrote:
>  Has anyone any objections to me pushing MD 2.2 with the plugins to
> f12?
>  If people are happy, I'll do it tonight.
>  
>  There have been no stability issues with the 2.2 release that I've seen
>  or reported via BZ. 
The update of MD 2.2 including some dependencies has been pushed to
updates-testing:

https://admin.fedoraproject.org/updates/monodevelop-debugger-mdb-2.2-1.fc...

Once it hits the mirrors in a couple of days, it would be great if you
could test it a little bit and give some feedback in bodhi. ;-)


Best regards,
Christian