libgdiplus 2.6.7 in F13 - any objections?
by Christian Krause
Hi,
In order to fix a security problem in libgdiplus (
https://bugzilla.redhat.com/show_bug.cgi?id=626821 ) it is necessary to
push out an update in F13.
Since F13 will be updated sooner or later to mono 2.6.7 as well, I was
wondering whether it would be possible to push out libgdiplus 2.6.7
(with the security fix) solely first and leave the rest of the mono
stack at 2.6.4 for now. I've roughly checked the commit logs for
libgdiplus and it really doesn't look like that there were any
incompatible (API) changes.
IMHO only programs using WinForms are actually using libgdiplus and a
short test with some example programs did not reveal any issue of using
libgdiplus-2.6.7 with mono 2.6.4.
Any comments or ideas whether this is possible? ;-)
Thanks!
Best regards,
Christian
13 years, 8 months
Heads up - mono 2.6.7 on it's way
by Paul F. Johnson
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"
13 years, 8 months
Internal compiler error
by Christopher Brown
Hi folks,
List is a bit quiet so though this might be nice - something for the
weekend! Actually, I'm just hoping someone with a bit more brain-fu
can nail this one down.
I am attempting to compile opendental from:
https://70.90.133.65:23793/svn/opendental/opendental7.1
and am getting the following error:
Internal compiler error at
/home/chris/Projects/OpenDental71/OpenDentBusiness/Data
Interface/ProcedureCodes.cs(469,36):: exception caught while emitting
MethodBuilder [ProcedureCodes::ResetADAdescriptions]
Think I'm just missing a dependency but any input greatly appreciated.
--
Christopher Brown
13 years, 8 months
Re: Out of action for a while & mono heads up
by Christian Krause
Hi Paul,
On 08/04/2010 10:22 AM, Paul Johnson wrote:
> Onto something else, mono 2.8 is due out in September so Novell are
> going to be releasing a 2.7 release candidate/test candidate series at
> some point either late this week or early next. Please remember that the
> 2.8 branch will not have any support at all for .NET 1.1. If you are
> maintaining anything which relies on the 1.1 framework, please contact
> either the upstream people for fixes or be prepared for breakages galore.
Since F14 will be shipped only one month later than mono 2.8, I'd like
to suggest not to update mono in the F14 branch to 2.8 or any release
candidates for now. If the mono release would be delayed we would end up
with some probably instable pre-release in F14.
Updating rawhide with the release candidates or the final mono 2.8 is
for sure a good thing to report any problems to upstream early.
If it turns out that the final 2.8 is quite stable and none of the major
mono-based packages rely on .NET 1.1 we can always reconsidering the
decision on the mailing list later on and update it in F14 as well.
Paul, do you agree?
Best regards,
Christian
13 years, 8 months
