4:48 p.m.
Hi,
At the end of next week, Novell will be releasing the new version of
mono (2.6.7).
I'm currently building it for rawhide (well, the release candidate). The
new version fixes lots of bugs and is generally a damned sight faster
than previous versions.
Also being built : libgdiplus, xsp, mod_mono and mono-tools
Mono package maintainers do not need to recompile other apps against it.
2.6.7 is the last (unless there is a 2.6.7.1) of the 2.6 branch. From
2.8, support for .NET 1.1 will be dropped. If anyone still has an app
which uses the 1.1 framework, it'll die in the 2.8 branching. I suggest
either contacting upstream for .NET 2.0 framework patches, fixing it
yourself or retiring it from rawhide.
Failing that, it may be possible to create a -compat package, but I
don't know the mileage in that or even if it's worth it.
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"
6:48 p.m.
Hi Paul,
On 07/10/2010 11:48 PM, Paul wrote:
At the end of next week, Novell will be releasing the new version of
mono (2.6.7).
I'm currently building it for rawhide (well, the release candidate). The
Ok, sounds good. However, I'd like to suggest to wait for the official
release before adding it to RAWHIDE... would this be ok?
Just as a heads-up: I'm seeing strange build problems on x86-64: it is
not even possible to rebuild the mono package for rawhide and F13. I'm
debugging the problem with dgilmore, mmcgrath and nirik and it looks
like that the build machines with RHEL6 can't successfully build mono
anymore since mcs.exe just gets stuck waiting for a futex.
I'll keep you updated.
new version fixes lots of bugs and is generally a damned sight
faster
than previous versions.
Also being built : libgdiplus, xsp, mod_mono and mono-tools
Mono package maintainers do not need to recompile other apps against it.
2.6.7 is the last (unless there is a 2.6.7.1) of the 2.6 branch.
From
2.8, support for .NET 1.1 will be dropped. If anyone still has an app
which uses the 1.1 framework, it'll die in the 2.8 branching. I suggest
either contacting upstream for .NET 2.0 framework patches, fixing it
yourself or retiring it from rawhide.
But this will only be important once we updated to mono 2.8, correct?
Best regards,
Christian
2:36 a.m.
Hi,
> At the end of next week, Novell will be releasing the new
version of
> mono (2.6.7).
> I'm currently building it for rawhide (well, the release candidate). The
The official release will be at the end of this week. The version
currently out there from the Novell preview pages is what will be
released all barring something catastrophic happening
Just as a heads-up: I'm seeing strange build problems on x86-64:
it is
not even possible to rebuild the mono package for rawhide and F13. I'm
debugging the problem with dgilmore, mmcgrath and nirik and it looks
like that the build machines with RHEL6 can't successfully build mono
anymore since mcs.exe just gets stuck waiting for a futex.
I've not seen anything reported on BZ over this. If it's mcs that's
borking, it'll be the 1.1 stuff which is causing the issue. Can a simple
winform/gtksharp test case targeting 2.0 not be generated and built
using gmcs to see if the problem is mcs or something else?
I'll keep you updated.
Please do.
> 2.6.7 is the last (unless there is a 2.6.7.1) of the 2.6 branch.
From
> 2.8, support for .NET 1.1 will be dropped. If anyone still has an app
> which uses the 1.1 framework, it'll die in the 2.8 branching. I suggest
> either contacting upstream for .NET 2.0 framework patches, fixing it
> yourself or retiring it from rawhide.
But this will only be important once we updated to mono 2.8, correct?
Correct. I think that'll be a Christmas present though ;-)
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"
3:38 p.m.
Hi Paul,
On 07/13/2010 09:36 AM, Paul wrote:
>> At the end of next week, Novell will be releasing the new
version of
>> mono (2.6.7).
>> I'm currently building it for rawhide (well, the release candidate). The
The official release will be at the end of this week. The version
currently out there from the Novell preview pages is what will be
released all barring something catastrophic happening
from CVS mono/devel/mono.spec
--------------------
* Tue Jul 13 2010 Paul F. Johnson <paul(a)all-the-johnsons.co.uk> 2.6.7-1
- Update to 2.6.7 release candidate 1
--------------------
I'm honestly a little bit disappointed that you have ignored my request
-----------------------------
> Ok, sounds good. However, I'd like to suggest to wait for the
official
> release before adding it to RAWHIDE... would this be ok?
-----------------------------
to wait for the official 2.6.7 release - your recent commit violates
the packaging guidelines in two ways:
1. Source0: URL is wrong - so it is not clear
where the new tarball was downloaded from:
spectool -g mono.spec
--2010-07-15 21:44:33--
http://ftp.novell.com/pub/mono/sources/mono/mono-2.6.7.tar.bz2
Resolving ftp.novell.com... 130.57.1.88
Connecting to ftp.novell.com|130.57.1.88|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2010-07-15 21:44:34 ERROR 404: Not Found.
2. No indication of the pre-release. Other packagers may have the
impression that this is already the final release (just by looking at
NVR and the source tarball). The packaging guidelines require a very
specific release tag for pre-releases packages:
http://fedoraproject.org/wiki/Packaging:NamingGuidelines#Pre-Release_pack...
Especially not indicating pre-releases have already caused issues which
were very hard to find (patch for final release was missing, but nothing
indicated a pre-release tarball - see
http://cvs.fedoraproject.org/viewvc/rpms/mono/F-10/mono.spec?view=log).
Please note, that it took me quite some time to get the mono packages in
a decent shape so that at least some very basic requirements
like:
- correct URL/Source0: URLs
- source files matches upstream
are met and I will not accept that the same mistakes are done again.
Since you have already built the new mono we can't correct the Release,
but at least you should correct the Source0 URL. Once the final mono
2.6.7 comes out, we should ensure that we update the package accordingly
again.
In the future, please let us discuss decisions like updating to a
pre-release.
Best regards,
Christian
3:57 p.m.
Hi,
On 07/13/2010 01:48 AM, Christian Krause wrote:
Just as a heads-up: I'm seeing strange build problems on x86-64:
it is
not even possible to rebuild the mono package for rawhide and F13. I'm
debugging the problem with dgilmore, mmcgrath and nirik and it looks
like that the build machines with RHEL6 can't successfully build mono
anymore since mcs.exe just gets stuck waiting for a futex.
I'll keep you updated.
Unfortunately the debugging was more complicated than expected since a
couple of other issues (yum/python problems on RHEL 6 beta etc.)
prevented a proper debugging.
That's why I think it would be better just to update F13 to mono 2.6.7
as well. It is a bug-fix release for 2.6.x anyway and so I believe
that's the right way to go. ;-)
Best regards,
Christian
1:54 a.m.
Hi,
That's why I think it would be better just to update F13 to mono
2.6.7
as well. It is a bug-fix release for 2.6.x anyway and so I believe
that's the right way to go. ;-)
Give it a few more weeks - I'm seeing some odd regressions in 2.6.7
which I'm trying to get to the bottom of.
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"
5:02 p.m.
Hi Paul,
On 07/28/2010 08:54 AM, Paul wrote:
> That's why I think it would be better just to update F13 to
mono 2.6.7
> as well. It is a bug-fix release for 2.6.x anyway and so I believe
> that's the right way to go. ;-)
Give it a few more weeks - I'm seeing some odd regressions in 2.6.7
which I'm trying to get to the bottom of.
Sure, there is no need to rush. What's the specific problem? Please can
you explain a little bit what kind of regressions have occurred?
Best regards,
Christian
3:06 a.m.
Hi Christian,
Give it a few more weeks - I'm seeing some odd regressions in
2.6.7
> which I'm trying to get to the bottom of.
Sure, there is no need to rush. What's the specific problem? Please can
you explain a little bit what kind of regressions have occurred?
I'm getting some weird stuff with MWF and database connections. I think
I've found the cause of the MWF problem, but the database one I'm trying to
patch before the 2.7 release.
TTFN
Paul
5:01 p.m.
Hi Paul,
On 08/05/2010 10:06 AM, Paul Johnson wrote:
> Give it a few more weeks - I'm seeing some odd
regressions in 2.6.7
> which I'm trying to get to the bottom of.
Sure, there is no need to rush. What's the specific problem? Please can
you explain a little bit what kind of regressions have occurred?
I'm getting some weird stuff with MWF and database connections. I think
I've found the cause of the MWF problem, but the database one I'm trying
to patch before the 2.7 release.
Are these issues still present and will they block moving to mono 2.6.7
in F13? If yes, please can you be more specific about the problem?
2.6.7 is supposed to be a bug fix release for mono 2.6.x and I don't
want to wait too long until we'll give it to the masses (which probably
suffer already from bugs in 2.6.4 which are actually fixed in 2.6.7).
Best regards,
Christian
5000
days inactive
5045
days old
8 comments
2 participants
participants (2)
-
Christian Krause -
Paul F. Johnson