From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110513/004649.html | 91 ++++++++++++++ zarb-ml/mageia-dev/20110513/004650.html | 77 ++++++++++++ zarb-ml/mageia-dev/20110513/004651.html | 99 +++++++++++++++ zarb-ml/mageia-dev/20110513/004652.html | 110 +++++++++++++++++ zarb-ml/mageia-dev/20110513/004653.html | 114 ++++++++++++++++++ zarb-ml/mageia-dev/20110513/004654.html | 112 +++++++++++++++++ zarb-ml/mageia-dev/20110513/004655.html | 84 +++++++++++++ zarb-ml/mageia-dev/20110513/004656.html | 116 ++++++++++++++++++ zarb-ml/mageia-dev/20110513/004657.html | 99 +++++++++++++++ zarb-ml/mageia-dev/20110513/004658.html | 121 +++++++++++++++++++ zarb-ml/mageia-dev/20110513/004659.html | 123 +++++++++++++++++++ zarb-ml/mageia-dev/20110513/004660.html | 141 ++++++++++++++++++++++ zarb-ml/mageia-dev/20110513/004661.html | 93 +++++++++++++++ zarb-ml/mageia-dev/20110513/004662.html | 154 ++++++++++++++++++++++++ zarb-ml/mageia-dev/20110513/004663.html | 68 +++++++++++ zarb-ml/mageia-dev/20110513/004664.html | 72 +++++++++++ zarb-ml/mageia-dev/20110513/004665.html | 78 ++++++++++++ zarb-ml/mageia-dev/20110513/004666.html | 92 ++++++++++++++ zarb-ml/mageia-dev/20110513/004667.html | 98 +++++++++++++++ zarb-ml/mageia-dev/20110513/004668.html | 61 ++++++++++ zarb-ml/mageia-dev/20110513/004669.html | 61 ++++++++++ zarb-ml/mageia-dev/20110513/004670.html | 69 +++++++++++ zarb-ml/mageia-dev/20110513/author.html | 157 ++++++++++++++++++++++++ zarb-ml/mageia-dev/20110513/date.html | 157 ++++++++++++++++++++++++ zarb-ml/mageia-dev/20110513/index.html | 1 + zarb-ml/mageia-dev/20110513/subject.html | 157 ++++++++++++++++++++++++ zarb-ml/mageia-dev/20110513/thread.html | 199 +++++++++++++++++++++++++++++++ 27 files changed, 2804 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110513/004649.html create mode 100644 zarb-ml/mageia-dev/20110513/004650.html create mode 100644 zarb-ml/mageia-dev/20110513/004651.html create mode 100644 zarb-ml/mageia-dev/20110513/004652.html create mode 100644 zarb-ml/mageia-dev/20110513/004653.html create mode 100644 zarb-ml/mageia-dev/20110513/004654.html create mode 100644 zarb-ml/mageia-dev/20110513/004655.html create mode 100644 zarb-ml/mageia-dev/20110513/004656.html create mode 100644 zarb-ml/mageia-dev/20110513/004657.html create mode 100644 zarb-ml/mageia-dev/20110513/004658.html create mode 100644 zarb-ml/mageia-dev/20110513/004659.html create mode 100644 zarb-ml/mageia-dev/20110513/004660.html create mode 100644 zarb-ml/mageia-dev/20110513/004661.html create mode 100644 zarb-ml/mageia-dev/20110513/004662.html create mode 100644 zarb-ml/mageia-dev/20110513/004663.html create mode 100644 zarb-ml/mageia-dev/20110513/004664.html create mode 100644 zarb-ml/mageia-dev/20110513/004665.html create mode 100644 zarb-ml/mageia-dev/20110513/004666.html create mode 100644 zarb-ml/mageia-dev/20110513/004667.html create mode 100644 zarb-ml/mageia-dev/20110513/004668.html create mode 100644 zarb-ml/mageia-dev/20110513/004669.html create mode 100644 zarb-ml/mageia-dev/20110513/004670.html create mode 100644 zarb-ml/mageia-dev/20110513/author.html create mode 100644 zarb-ml/mageia-dev/20110513/date.html create mode 120000 zarb-ml/mageia-dev/20110513/index.html create mode 100644 zarb-ml/mageia-dev/20110513/subject.html create mode 100644 zarb-ml/mageia-dev/20110513/thread.html (limited to 'zarb-ml/mageia-dev/20110513') diff --git a/zarb-ml/mageia-dev/20110513/004649.html b/zarb-ml/mageia-dev/20110513/004649.html new file mode 100644 index 000000000..280d900db --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004649.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] why not disable bytecode interpreter in freetype2 ? + + + + + + + + + +

[Mageia-dev] why not disable bytecode interpreter in freetype2 ?

+ Zé + mmodem00 at gmail.com +
+ Fri May 13 00:39:55 CEST 2011 +

+
+ +
2011/5/12 Dick Gevers <dvgevers at xs4all.nl>:
+> On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about Re:
+> [Mageia-dev] why not disable bytecode interpreter in freetype2 ?:
+>
+>>When someone like me, has this problem of fonts, he cannot even use his
+>>system, he has a real problem. It costed me many uninstalls and installs
+>>and many hours of investigation.
+>>
+>>For that i asked a user friendly solution, is very important for them who
+>>are affected.
+>>
+>>Personnaly, after all, i am able now to set my pc to fit my needs but i
+>>continue to search a solution for other users who will be front of this
+>>problem in the future
+>
+> I can only make one suggestion - which works for me: keep the version one
+> is happy with and put the packages in the urpmi skip.list and you won't get
+> hurt by an upgrade.
+>
+> Cheers,
+> =Dick Gevers=
+>
+
+You always rebuild the freetype2 package, to do soedit the .spec file,
+in the section %prep add this:
+
+perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\*
+#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER  \*/|'
+include/freetype/config/ftoption.h
+
+
+dont forget to also increase Release to avoid conflicts with existant
+freetype2, and then build the package.
+
+-- 
+Zé
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004650.html b/zarb-ml/mageia-dev/20110513/004650.html new file mode 100644 index 000000000..5e1e4f528 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004650.html @@ -0,0 +1,77 @@ + + + + [Mageia-dev] Freeze push request: fglrx 8.850 + + + + + + + + + +

[Mageia-dev] Freeze push request: fglrx 8.850

+ Anssi Hannula + anssi.hannula at iki.fi +
+ Fri May 13 02:40:51 CEST 2011 +

+
+ +
I think the new version 8.85 should be pushed, changes include
+- fixes intel/fglrx switching on PowerXpress
+- fixes some cases of suspend not working
+
+Especially the first change is something that would be nice, since the
+ATI version we have now claims to support it as well but fails to work
+(it tries to mv libraries around manually; not sure how cleanly it fails
+with our alternatives), confusing users.
+
+-- 
+Anssi Hannula
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004651.html b/zarb-ml/mageia-dev/20110513/004651.html new file mode 100644 index 000000000..2688a4d35 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004651.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] why not disable bytecode interpreter in freetype2 ? + + + + + + + + + +

[Mageia-dev] why not disable bytecode interpreter in freetype2 ?

+ Dimitrios Glentadakis + dglent at gmail.com +
+ Fri May 13 05:45:05 CEST 2011 +

+
+ +
Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε:
+> 2011/5/12 Dick Gevers <dvgevers at xs4all.nl>:
+> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about Re:
+> > [Mageia-dev] why not disable bytecode interpreter in freetype2 ?:
+> >
+> >>When someone like me, has this problem of fonts, he cannot even use his
+> >>system, he has a real problem. It costed me many uninstalls and installs
+> >>and many hours of investigation.
+> >>
+> >>For that i asked a user friendly solution, is very important for them who
+> >>are affected.
+> >>
+> >>Personnaly, after all, i am able now to set my pc to fit my needs but i
+> >>continue to search a solution for other users who will be front of this
+> >>problem in the future
+> >
+> > I can only make one suggestion - which works for me: keep the version one
+> > is happy with and put the packages in the urpmi skip.list and you won't get
+> > hurt by an upgrade.
+> >
+> > Cheers,
+> > =Dick Gevers=
+> >
+> 
+> You always rebuild the freetype2 package, to do soedit the .spec file,
+> in the section %prep add this:
+> 
+> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\*
+> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER  \*/|'
+> include/freetype/config/ftoption.h
+> 
+> 
+> dont forget to also increase Release to avoid conflicts with existant
+> freetype2, and then build the package.
+> 
+> 
+
+
+Why do all these things when you can simply add an entry in the font.conf file ?
+
+
+-- 
+Dimitrios Glentadakis
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004652.html b/zarb-ml/mageia-dev/20110513/004652.html new file mode 100644 index 000000000..6c2f33931 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004652.html @@ -0,0 +1,110 @@ + + + + [Mageia-dev] why not disable bytecode interpreter in freetype2 ? + + + + + + + + + +

[Mageia-dev] why not disable bytecode interpreter in freetype2 ?

+ Zé + mmodem00 at gmail.com +
+ Fri May 13 10:54:41 CEST 2011 +

+
+ +
2011/5/13 Dimitrios Glentadakis <dglent at gmail.com>:
+> Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε:
+>> 2011/5/12 Dick Gevers <dvgevers at xs4all.nl>:
+>> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about Re:
+>> > [Mageia-dev] why not disable bytecode interpreter in freetype2 ?:
+>> >
+>> >>When someone like me, has this problem of fonts, he cannot even use his
+>> >>system, he has a real problem. It costed me many uninstalls and installs
+>> >>and many hours of investigation.
+>> >>
+>> >>For that i asked a user friendly solution, is very important for them who
+>> >>are affected.
+>> >>
+>> >>Personnaly, after all, i am able now to set my pc to fit my needs but i
+>> >>continue to search a solution for other users who will be front of this
+>> >>problem in the future
+>> >
+>> > I can only make one suggestion - which works for me: keep the version one
+>> > is happy with and put the packages in the urpmi skip.list and you won't get
+>> > hurt by an upgrade.
+>> >
+>> > Cheers,
+>> > =Dick Gevers=
+>> >
+>>
+>> You always rebuild the freetype2 package, to do soedit the .spec file,
+>> in the section %prep add this:
+>>
+>> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\*
+>> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER  \*/|'
+>> include/freetype/config/ftoption.h
+>>
+>>
+>> dont forget to also increase Release to avoid conflicts with existant
+>> freetype2, and then build the package.
+>>
+>>
+>
+>
+> Why do all these things when you can simply add an entry in the font.conf file ?
+
+Thats a fact, but hat should happen is that freetype2 should have
+bytecode interpreter disabled by default, since so far users prefer
+it.
+
+> --
+> Dimitrios Glentadakis
+>
+
+
+
+-- 
+Zé
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004653.html b/zarb-ml/mageia-dev/20110513/004653.html new file mode 100644 index 000000000..29e24f813 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004653.html @@ -0,0 +1,114 @@ + + + + [Mageia-dev] why not disable bytecode interpreter in freetype2 ? + + + + + + + + + +

[Mageia-dev] why not disable bytecode interpreter in freetype2 ?

+ Zé + mmodem00 at gmail.com +
+ Fri May 13 10:56:51 CEST 2011 +

+
+ +
2011/5/13 Dimitrios Glentadakis <dglent at gmail.com>:
+> Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε:
+>> 2011/5/12 Dick Gevers <dvgevers at xs4all.nl>:
+>> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about Re:
+>> > [Mageia-dev] why not disable bytecode interpreter in freetype2 ?:
+>> >
+>> >>When someone like me, has this problem of fonts, he cannot even use his
+>> >>system, he has a real problem. It costed me many uninstalls and installs
+>> >>and many hours of investigation.
+>> >>
+>> >>For that i asked a user friendly solution, is very important for them who
+>> >>are affected.
+>> >>
+>> >>Personnaly, after all, i am able now to set my pc to fit my needs but i
+>> >>continue to search a solution for other users who will be front of this
+>> >>problem in the future
+>> >
+>> > I can only make one suggestion - which works for me: keep the version one
+>> > is happy with and put the packages in the urpmi skip.list and you won't get
+>> > hurt by an upgrade.
+>> >
+>> > Cheers,
+>> > =Dick Gevers=
+>> >
+>>
+>> You always rebuild the freetype2 package, to do soedit the .spec file,
+>> in the section %prep add this:
+>>
+>> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\*
+>> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER  \*/|'
+>> include/freetype/config/ftoption.h
+>>
+>>
+>> dont forget to also increase Release to avoid conflicts with existant
+>> freetype2, and then build the package.
+>>
+>>
+>
+>
+> Why do all these things when you can simply add an entry in the font.conf file ?
+
+Forgot to refer that even when you set it in .fonts.conf you will
+still have it in some situations, check
+http://www.webmasterkb.com/Uwe/Forum.aspx/opera-linux/2140/disabling-bytecode-interpreter-font-rendering
+
+> --
+> Dimitrios Glentadakis
+>
+
+
+
+-- 
+Zé
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004654.html b/zarb-ml/mageia-dev/20110513/004654.html new file mode 100644 index 000000000..9b85c571a --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004654.html @@ -0,0 +1,112 @@ + + + + [Mageia-dev] why not disable bytecode interpreter in freetype2 ? + + + + + + + + + +

[Mageia-dev] why not disable bytecode interpreter in freetype2 ?

+ Zé + mmodem00 at gmail.com +
+ Fri May 13 11:12:41 CEST 2011 +

+
+ +
2011/5/13 Zé <mmodem00 at gmail.com>:
+> 2011/5/13 Dimitrios Glentadakis <dglent at gmail.com>:
+>> Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε:
+>>> 2011/5/12 Dick Gevers <dvgevers at xs4all.nl>:
+>>> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about Re:
+>>> > [Mageia-dev] why not disable bytecode interpreter in freetype2 ?:
+>>> >
+>>> >>When someone like me, has this problem of fonts, he cannot even use his
+>>> >>system, he has a real problem. It costed me many uninstalls and installs
+>>> >>and many hours of investigation.
+>>> >>
+>>> >>For that i asked a user friendly solution, is very important for them who
+>>> >>are affected.
+>>> >>
+>>> >>Personnaly, after all, i am able now to set my pc to fit my needs but i
+>>> >>continue to search a solution for other users who will be front of this
+>>> >>problem in the future
+>>> >
+>>> > I can only make one suggestion - which works for me: keep the version one
+>>> > is happy with and put the packages in the urpmi skip.list and you won't get
+>>> > hurt by an upgrade.
+>>> >
+>>> > Cheers,
+>>> > =Dick Gevers=
+>>> >
+>>>
+>>> You always rebuild the freetype2 package, to do soedit the .spec file,
+>>> in the section %prep add this:
+>>>
+>>> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\*
+>>> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER  \*/|'
+>>> include/freetype/config/ftoption.h
+>>>
+>>>
+>>> dont forget to also increase Release to avoid conflicts with existant
+>>> freetype2, and then build the package.
+>>>
+>>>
+>>
+>>
+>> Why do all these things when you can simply add an entry in the font.conf file ?
+>
+> Thats a fact, but hat should happen is that freetype2 should have
+> bytecode interpreter disabled by default, since so far users prefer
+> it.
+
+Seams Fedora choosed to finally fix it, it reverted freetype2 with a
+patch to disable bytecode interpreter. ->
+https://bugzilla.redhat.com/show_bug.cgi?id=547532
+
+Why dont we also do the same thing?
+
+Since theres users complaining about it, why not solve it once for all?
+
+-- 
+Zé
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004655.html b/zarb-ml/mageia-dev/20110513/004655.html new file mode 100644 index 000000000..6a3ad58fa --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004655.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] why not disable bytecode interpreter in freetype2 ? + + + + + + + + + +

[Mageia-dev] why not disable bytecode interpreter in freetype2 ?

+ You-Cheng Hsieh + yochenhsieh at gmail.com +
+ Fri May 13 11:51:15 CEST 2011 +

+
+ +
2011/5/13 Zé <mmodem00 at gmail.com>:
+> 2011/5/13 Zé <mmodem00 at gmail.com>:
+>> Thats a fact, but hat should happen is that freetype2 should have
+>> bytecode interpreter disabled by default, since so far users prefer
+>> it.
+> Seams Fedora choosed to finally fix it, it reverted freetype2 with a
+> patch to disable bytecode interpreter. ->
+> https://bugzilla.redhat.com/show_bug.cgi?id=547532
+> Why dont we also do the same thing?
+> Since theres users complaining about it, why not solve it once for all?
+> --
+> Zé
+>
+Hello,
+
+Is this thread asking to _disable_ bytecode interpreter?
+
+Please don't do that. Bacause pdf which embedded with Windows Chinese
+fonts will look like this if you disabled bytecode interpreter:
+http://hyperrate.com/thread.php?tid=680
+
+For years we have to either rebuild freetype, or use plf package.
+Since there's no patent problems now, I beg you, seriously, please do
+not disable bytecode interpreter in freetype.
+
+Sincerely,
+
+You-Cheng Hsieh
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004656.html b/zarb-ml/mageia-dev/20110513/004656.html new file mode 100644 index 000000000..cfdcedafd --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004656.html @@ -0,0 +1,116 @@ + + + + [Mageia-dev] why not disable bytecode interpreter in freetype2 ? + + + + + + + + + +

[Mageia-dev] why not disable bytecode interpreter in freetype2 ?

+ Buchan Milne + bgmilne at staff.telkomsa.net +
+ Fri May 13 12:09:17 CEST 2011 +

+
+ +
On Friday, 13 May 2011 11:12:41 Zé wrote:
+> 2011/5/13 Zé <mmodem00 at gmail.com>:
+> > 2011/5/13 Dimitrios Glentadakis <dglent at gmail.com>:
+> >> Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε:
+> >>> 2011/5/12 Dick Gevers <dvgevers at xs4all.nl>:
+> >>> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about
+
+> >>> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\*
+> >>> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER  \*/|'
+> >>> include/freetype/config/ftoption.h
+> >>> 
+> >>> 
+> >>> dont forget to also increase Release to avoid conflicts with existant
+> >>> freetype2, and then build the package.
+> >> 
+> >> Why do all these things when you can simply add an entry in the
+> >> font.conf file ?
+> > 
+> > Thats a fact, but hat should happen is that freetype2 should have
+> > bytecode interpreter disabled by default, since so far users prefer
+> > it.
+> 
+> Seams Fedora choosed to finally fix it, it reverted freetype2 with a
+> patch to disable bytecode interpreter. ->
+> https://bugzilla.redhat.com/show_bug.cgi?id=547532
+
+No, this is not what is covered in this bug report.
+
+Firstly, here are the non-problems:
+1)The bytecode interpreter *can* make fonts look better, *if* they have 
+hinting in the fonts. Not all ttf fonts have hinting, but AFAIK all the MS 
+fonts *do* have hinting.
+
+So, historically, the recommended approach was to use the PLF freetype *if* 
+you had imported MS fonts (e.g. from a dual-boot Windows installation).
+
+2)The Freetype autohinter was implemented later, and improves things for 
+unhinted fonts, but hinted fonts still looked better with the bytecode 
+interpreter.
+
+
+This is the problem:
+3)If the bytecode interpreter was enabled, auto-hinting was disabled (or, 
+could be, for 'medium' and 'heavy' hinting settings) for unhinted fonts.
+
+The Fedora bug isn't about disabling the bytecode interpreter, but by still 
+allowing auto-hinting for unhinted fonts if the bytecode interpreter.
+
+*This* is the right fix. Your insistence to *disable* the bytecode interpreter 
+(leaving users with *no* options, in case they need hinted fonts) is the wrong 
+fix.
+
+But, thanks for the pointer to the bug, which points to the patches.
+
+> Why dont we also do the same thing?
+> 
+> Since theres users complaining about it, why not solve it once for all?
+
+Regards,
+Buchan
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004657.html b/zarb-ml/mageia-dev/20110513/004657.html new file mode 100644 index 000000000..76b8a5019 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004657.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] Samba update to 3.5.8 + + + + + + + + + +

[Mageia-dev] Samba update to 3.5.8

+ Buchan Milne + bgmilne at staff.telkomsa.net +
+ Fri May 13 12:16:34 CEST 2011 +

+
+ +
I have finally got a bit of time to get busy with Mageia packaging (my first 
+VM was on virtio disk on Mandriva 2010.1/kvm, and there seem to be some 
+corruption problems, I finally got time to reinstall it yesterday).
+
+Since I have just finished samba/samba4 updates in Cooker, I would like to 
+update Cauldron to the same.
+
+Specifically, what we miss between 3.5.5+CVE is:
+
+
+New in 3.5.8:
+o  Fix Winbind crash bug when no DC is available (bug #7730).
+o  Fix finding users on domain members (bug #7743).
+o  Fix memory leaks in Winbind (bug #7879).
+o  Fix printing with Windows 7 clients (bug #7567).
+
+New in 3.5.6:
+  o Fix smbd panic on invalid NetBIOS session request (bug #7698).
+  o Fix smbd crash caused by "%D" in "printer admin" (bug #7541).
+  o Fix crash bug with invalid SPNEGO token (bug #7694).
+  o Fix Winbind internal error (bug #7636).
+
+Unfortunately, "samba features", if absent, are usually "samba bugs", such as 
+printing with Windows 7 clients etc.
+
+If this is viable, I will try and commit updates to the following in svn 
+between now and 15h00 UTC:
+
+-tdb 1.2.9 (done)
+-ldb 1.1.0 (import)
+-samba-3.5.8
+-samba4alpha15 (alpha11 was imported about 2 days before I finished alpha15 in 
+Mandriva)
+
+Please let me know if I should go ahead. tdb should be pushed in the meantime 
+in this case.
+
+Regards,
+Buchan
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004658.html b/zarb-ml/mageia-dev/20110513/004658.html new file mode 100644 index 000000000..d5239312b --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004658.html @@ -0,0 +1,121 @@ + + + + [Mageia-dev] Samba update to 3.5.8 + + + + + + + + + +

[Mageia-dev] Samba update to 3.5.8

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Fri May 13 12:28:45 CEST 2011 +

+
+ +
'Twas brillig, and Buchan Milne at 13/05/11 11:16 did gyre and gimble:
+> I have finally got a bit of time to get busy with Mageia packaging (my first 
+> VM was on virtio disk on Mandriva 2010.1/kvm, and there seem to be some 
+> corruption problems, I finally got time to reinstall it yesterday).
+> 
+> Since I have just finished samba/samba4 updates in Cooker, I would like to 
+> update Cauldron to the same.
+> 
+> Specifically, what we miss between 3.5.5+CVE is:
+> 
+> 
+> New in 3.5.8:
+> o  Fix Winbind crash bug when no DC is available (bug #7730).
+> o  Fix finding users on domain members (bug #7743).
+> o  Fix memory leaks in Winbind (bug #7879).
+> o  Fix printing with Windows 7 clients (bug #7567).
+> 
+> New in 3.5.6:
+>   o Fix smbd panic on invalid NetBIOS session request (bug #7698).
+>   o Fix smbd crash caused by "%D" in "printer admin" (bug #7541).
+>   o Fix crash bug with invalid SPNEGO token (bug #7694).
+>   o Fix Winbind internal error (bug #7636).
+> 
+> Unfortunately, "samba features", if absent, are usually "samba bugs", such as 
+> printing with Windows 7 clients etc.
+> 
+> If this is viable, I will try and commit updates to the following in svn 
+> between now and 15h00 UTC:
+> 
+> -tdb 1.2.9 (done)
+> -ldb 1.1.0 (import)
+> -samba-3.5.8
+> -samba4alpha15 (alpha11 was imported about 2 days before I finished alpha15 in 
+> Mandriva)
+> 
+> Please let me know if I should go ahead. tdb should be pushed in the meantime 
+> in this case.
+
+While this is very late in the cycle, the changes to samba look like
+bugfixes to me and the samba4alpha package is likely one we can push
+through the freeze anyway due to it's nature.
+
+So IMO the only question is the tdb and ldb. Are these just bug fixes
+too? (as ldb is an import it's less of an issue - is it just needed for
+samba4?)
+
+Col
+
+
+-- 
+
+Colin Guthrie
+mageia(at)colin.guthr.ie
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited [http://www.tribalogic.net/]
+Open Source:
+  Mageia Contributor [http://www.mageia.org/]
+  PulseAudio Hacker [http://www.pulseaudio.org/]
+  Trac Hacker [http://trac.edgewall.org/]
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004659.html b/zarb-ml/mageia-dev/20110513/004659.html new file mode 100644 index 000000000..9c56623a2 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004659.html @@ -0,0 +1,123 @@ + + + + [Mageia-dev] Samba update to 3.5.8 + + + + + + + + + +

[Mageia-dev] Samba update to 3.5.8

+ Buchan Milne + bgmilne at staff.telkomsa.net +
+ Fri May 13 13:08:31 CEST 2011 +

+
+ +
On Friday, 13 May 2011 12:28:45 Colin Guthrie wrote:
+> 'Twas brillig, and Buchan Milne at 13/05/11 11:16 did gyre and gimble:
+> > I have finally got a bit of time to get busy with Mageia packaging (my
+> > first VM was on virtio disk on Mandriva 2010.1/kvm, and there seem to be
+> > some corruption problems, I finally got time to reinstall it yesterday).
+> > 
+> > Since I have just finished samba/samba4 updates in Cooker, I would like
+> > to update Cauldron to the same.
+> > 
+> > Specifically, what we miss between 3.5.5+CVE is:
+> > 
+> > 
+> > New in 3.5.8:
+> > o  Fix Winbind crash bug when no DC is available (bug #7730).
+> > o  Fix finding users on domain members (bug #7743).
+> > o  Fix memory leaks in Winbind (bug #7879).
+> > o  Fix printing with Windows 7 clients (bug #7567).
+> > 
+> > New in 3.5.6:
+> >   o Fix smbd panic on invalid NetBIOS session request (bug #7698).
+> >   o Fix smbd crash caused by "%D" in "printer admin" (bug #7541).
+> >   o Fix crash bug with invalid SPNEGO token (bug #7694).
+> >   o Fix Winbind internal error (bug #7636).
+> > 
+> > Unfortunately, "samba features", if absent, are usually "samba bugs",
+> > such as printing with Windows 7 clients etc.
+> > 
+> > If this is viable, I will try and commit updates to the following in svn
+> > between now and 15h00 UTC:
+> > 
+> > -tdb 1.2.9 (done)
+> > -ldb 1.1.0 (import)
+
+I could probably submit this now, but it (build)requires tdb-1.2.9. Its other 
+requirement, fixed package names/provides for talloc, has just finished 
+building.
+
+> > -samba-3.5.8
+> > -samba4alpha15 (alpha11 was imported about 2 days before I finished
+> > alpha15 in Mandriva)
+> > 
+> > Please let me know if I should go ahead. tdb should be pushed in the
+> > meantime in this case.
+> 
+> While this is very late in the cycle, the changes to samba look like
+> bugfixes to me and the samba4alpha package is likely one we can push
+> through the freeze anyway due to it's nature.
+> 
+> So IMO the only question is the tdb and ldb. Are these just bug fixes
+> too? (as ldb is an import it's less of an issue - is it just needed for
+> samba4?)
+
+Both samba3 and samba4 require newer versions of tdb, and ldb, I've switched 
+to using standalone versions of all the common libraries 
+(talloc,tdb,tevent,ldb) now that they actually seem to be released before 
+versions of samba3/samba4 that need them.
+
+(By default, without the libraries, both versions of samba would build static-
+only copies, or you can choose to build shared libraries, but it ends up being 
+more convoluted having them in one or the other of samba3 or samba4).
+
+Regards,
+Buchan
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004660.html b/zarb-ml/mageia-dev/20110513/004660.html new file mode 100644 index 000000000..3b7e4968b --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004660.html @@ -0,0 +1,141 @@ + + + + [Mageia-dev] why not disable bytecode interpreter in freetype2 ? + + + + + + + + + +

[Mageia-dev] why not disable bytecode interpreter in freetype2 ?

+ Zé + mmodem00 at gmail.com +
+ Fri May 13 17:28:24 CEST 2011 +

+
+ +
2011/5/13 Buchan Milne <bgmilne at staff.telkomsa.net>:
+> On Friday, 13 May 2011 11:12:41 Zé wrote:
+>> 2011/5/13 Zé <mmodem00 at gmail.com>:
+>> > 2011/5/13 Dimitrios Glentadakis <dglent at gmail.com>:
+>> >> Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε:
+>> >>> 2011/5/12 Dick Gevers <dvgevers at xs4all.nl>:
+>> >>> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote about
+>
+>> >>> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\*
+>> >>> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER  \*/|'
+>> >>> include/freetype/config/ftoption.h
+>> >>>
+>> >>>
+>> >>> dont forget to also increase Release to avoid conflicts with existant
+>> >>> freetype2, and then build the package.
+>> >>
+>> >> Why do all these things when you can simply add an entry in the
+>> >> font.conf file ?
+>> >
+>> > Thats a fact, but hat should happen is that freetype2 should have
+>> > bytecode interpreter disabled by default, since so far users prefer
+>> > it.
+>>
+>> Seams Fedora choosed to finally fix it, it reverted freetype2 with a
+>> patch to disable bytecode interpreter. ->
+>> https://bugzilla.redhat.com/show_bug.cgi?id=547532
+>
+> No, this is not what is covered in this bug report.
+
+Yes, correct i miss understood what as the bug report about.
+
+> Firstly, here are the non-problems:
+> 1)The bytecode interpreter *can* make fonts look better, *if* they have
+> hinting in the fonts. Not all ttf fonts have hinting, but AFAIK all the MS
+> fonts *do* have hinting.
+>
+> So, historically, the recommended approach was to use the PLF freetype *if*
+> you had imported MS fonts (e.g. from a dual-boot Windows installation).
+Well i always avoid using PLF freetype and for what i have read in
+ML's all the users that answered to it said that also avoid PLF
+freetype.
+
+So far for hat i have seen, all users prefered like fonts were
+rendered wen patents were still valid...
+
+> 2)The Freetype autohinter was implemented later, and improves things for
+> unhinted fonts, but hinted fonts still looked better with the bytecode
+> interpreter.
+>
+>
+> This is the problem:
+> 3)If the bytecode interpreter was enabled, auto-hinting was disabled (or,
+> could be, for 'medium' and 'heavy' hinting settings) for unhinted fonts.
+>
+> The Fedora bug isn't about disabling the bytecode interpreter, but by still
+> allowing auto-hinting for unhinted fonts if the bytecode interpreter.
+>
+> *This* is the right fix. Your insistence to *disable* the bytecode interpreter
+> (leaving users with *no* options, in case they need hinted fonts) is the wrong
+> fix.
+Well this way users cant also set to have autohint, seams theres
+always some app failing.
+
+Why not having it disabled by default? users will always be able to
+set their preferences about using or not autohint, but that way
+ensures that all fonts are better rended.
+All this came up after patents end in wich showed users how fonts
+appear poor rended, until that point i didnt saw any complains about
+fonts, and this is what should be fixed.
+
+> But, thanks for the pointer to the bug, which points to the patches.
+>
+>> Why dont we also do the same thing?
+>>
+>> Since theres users complaining about it, why not solve it once for all?
+>
+> Regards,
+> Buchan
+>
+
+
+
+-- 
+Zé
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004661.html b/zarb-ml/mageia-dev/20110513/004661.html new file mode 100644 index 000000000..66065f6e2 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004661.html @@ -0,0 +1,93 @@ + + + + [Mageia-dev] why not disable bytecode interpreter in freetype2 ? + + + + + + + + + +

[Mageia-dev] why not disable bytecode interpreter in freetype2 ?

+ Ahmad Samir + ahmadsamir3891 at gmail.com +
+ Fri May 13 17:45:26 CEST 2011 +

+
+ +
On 13 May 2011 12:09, Buchan Milne <bgmilne at staff.telkomsa.net> wrote:
+>
+> No, this is not what is covered in this bug report.
+>
+> Firstly, here are the non-problems:
+> 1)The bytecode interpreter *can* make fonts look better, *if* they have
+> hinting in the fonts. Not all ttf fonts have hinting, but AFAIK all the MS
+> fonts *do* have hinting.
+>
+> So, historically, the recommended approach was to use the PLF freetype *if*
+> you had imported MS fonts (e.g. from a dual-boot Windows installation).
+>
+> 2)The Freetype autohinter was implemented later, and improves things for
+> unhinted fonts, but hinted fonts still looked better with the bytecode
+> interpreter.
+>
+>
+> This is the problem:
+> 3)If the bytecode interpreter was enabled, auto-hinting was disabled (or,
+> could be, for 'medium' and 'heavy' hinting settings) for unhinted fonts.
+>
+> The Fedora bug isn't about disabling the bytecode interpreter, but by still
+> allowing auto-hinting for unhinted fonts if the bytecode interpreter.
+>
+> *This* is the right fix. Your insistence to *disable* the bytecode interpreter
+> (leaving users with *no* options, in case they need hinted fonts) is the wrong
+> fix.
+>
+> But, thanks for the pointer to the bug, which points to the patches.
+
+Anssi has already added that patch to the Mageia freetype2 package
+about 2-3 months ago.
+
+[...]
+
+-- 
+Ahmad Samir
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004662.html b/zarb-ml/mageia-dev/20110513/004662.html new file mode 100644 index 000000000..40d5d24bb --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004662.html @@ -0,0 +1,154 @@ + + + + [Mageia-dev] why not disable bytecode interpreter in freetype2 ? + + + + + + + + + +

[Mageia-dev] why not disable bytecode interpreter in freetype2 ?

+ Buchan Milne + bgmilne at staff.telkomsa.net +
+ Fri May 13 17:46:38 CEST 2011 +

+
+ +
On Friday, 13 May 2011 17:28:24 Zé wrote:
+> 2011/5/13 Buchan Milne <bgmilne at staff.telkomsa.net>:
+> > On Friday, 13 May 2011 11:12:41 Zé wrote:
+> >> 2011/5/13 Zé <mmodem00 at gmail.com>:
+> >> > 2011/5/13 Dimitrios Glentadakis <dglent at gmail.com>:
+> >> >> Στις Παρασκευή 13 Μάιος 2011 00:39:55 Zé γράψατε:
+> >> >>> 2011/5/12 Dick Gevers <dvgevers at xs4all.nl>:
+> >> >>> > On Thu, 12 May 2011 13:20:39 +0200, Dimitrios Glentadakis wrote
+> >> >>> > about
+> >> >>> 
+> >> >>> perl -pi -e 's|#define TT_CONFIG_OPTION_BYTECODE_INTERPRETER|/\*
+> >> >>> #define TT_CONFIG_OPTION_BYTECODE_INTERPRETER  \*/|'
+> >> >>> include/freetype/config/ftoption.h
+> >> >>> 
+> >> >>> 
+> >> >>> dont forget to also increase Release to avoid conflicts with
+> >> >>> existant freetype2, and then build the package.
+> >> >> 
+> >> >> Why do all these things when you can simply add an entry in the
+> >> >> font.conf file ?
+> >> > 
+> >> > Thats a fact, but hat should happen is that freetype2 should have
+> >> > bytecode interpreter disabled by default, since so far users prefer
+> >> > it.
+> >> 
+> >> Seams Fedora choosed to finally fix it, it reverted freetype2 with a
+> >> patch to disable bytecode interpreter. ->
+> >> https://bugzilla.redhat.com/show_bug.cgi?id=547532
+> > 
+> > No, this is not what is covered in this bug report.
+> 
+> Yes, correct i miss understood what as the bug report about.
+> 
+> > Firstly, here are the non-problems:
+> > 1)The bytecode interpreter *can* make fonts look better, *if* they have
+> > hinting in the fonts. Not all ttf fonts have hinting, but AFAIK all the
+> > MS fonts *do* have hinting.
+> > 
+> > So, historically, the recommended approach was to use the PLF freetype
+> > *if* you had imported MS fonts (e.g. from a dual-boot Windows
+> > installation).
+> 
+> Well i always avoid using PLF freetype and for what i have read in
+> ML's all the users that answered to it said that also avoid PLF
+> freetype.
+> 
+> So far for hat i have seen, all users prefered like fonts were
+> rendered wen patents were still valid...
+
+Were *all* these users using *hinted* fonts? I think they weren't using hinted 
+fonts at all.
+
+> > 2)The Freetype autohinter was implemented later, and improves things for
+> > unhinted fonts, but hinted fonts still looked better with the bytecode
+> > interpreter.
+> > 
+> > 
+> > This is the problem:
+> > 3)If the bytecode interpreter was enabled, auto-hinting was disabled (or,
+> > could be, for 'medium' and 'heavy' hinting settings) for unhinted fonts.
+> > 
+> > The Fedora bug isn't about disabling the bytecode interpreter, but by
+> > still allowing auto-hinting for unhinted fonts if the bytecode
+> > interpreter.
+> > 
+> > *This* is the right fix. Your insistence to *disable* the bytecode
+> > interpreter (leaving users with *no* options, in case they need hinted
+> > fonts) is the wrong fix.
+> 
+> Well this way users cant also set to have autohint, seams theres
+> always some app failing.
+
+?
+
+We need to apply the patch that enables the autohinter for unhinted fonts, 
+even if the bytecode interpreter is enabled, that is available from the bug 
+report for which you provided the link.
+
+> Why not having it disabled by default?
+
+So, you haven't read what I wrote in (3)?
+
+> users will always be able to
+> set their preferences about using or not autohint, but that way
+> ensures that all fonts are better rended.
+
+No, you ignore the case where some hinted fonts are almost unusable without 
+the bytecode interpreter, and others where they are rendered better.
+
+> All this came up after patents end in wich showed users how fonts
+> appear poor rended, until that point i didnt saw any complains about
+> fonts, and this is what should be fixed.
+
+You contradict yourself ... and you can't make blanket statements of "how 
+fonts appear poor rended", as it depends on the font (and whether it is hinted 
+or not).
+
+Regards,
+Buchan
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004663.html b/zarb-ml/mageia-dev/20110513/004663.html new file mode 100644 index 000000000..a40f10d66 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004663.html @@ -0,0 +1,68 @@ + + + + [Mageia-dev] Freeze push request: fglrx 8.850 + + + + + + + + + +

[Mageia-dev] Freeze push request: fglrx 8.850

+ Michael scherer + misc at zarb.org +
+ Fri May 13 17:48:39 CEST 2011 +

+
+ +
On Fri, May 13, 2011 at 03:40:51AM +0300, Anssi Hannula wrote:
+> I think the new version 8.85 should be pushed, changes include
+> - fixes intel/fglrx switching on PowerXpress
+> - fixes some cases of suspend not working
+> 
+> Especially the first change is something that would be nice, since the
+> ATI version we have now claims to support it as well but fails to work
+> (it tries to mv libraries around manually; not sure how cleanly it fails
+> with our alternatives), confusing users.
+
+done
+-- 
+Michael Scherer
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004664.html b/zarb-ml/mageia-dev/20110513/004664.html new file mode 100644 index 000000000..431afd481 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004664.html @@ -0,0 +1,72 @@ + + + + [Mageia-dev] Problem with update notification + + + + + + + + + +

[Mageia-dev] Problem with update notification

+ Thibaut FRANCOIS + thibautf at gmail.com +
+ Fri May 13 19:47:49 CEST 2011 +

+
+ +
Hello,
+
+I updated my desktop computer from mandriva 2010.2 to mageia cauldron.
+Everything works fine, except one thing :
+when the "update notification" is red on my taskbar, I click on, but instead
+of launching mageiaupdate, there is only a new medias scan (the indicator is
+orange) and finally the indicator became red again.
+
+Am I alone with this problem ?
+
+Regards,
+Thibaut
+PS : I'm using KDE
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20110513/72d1f080/attachment.html>
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004665.html b/zarb-ml/mageia-dev/20110513/004665.html new file mode 100644 index 000000000..265e4d93f --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004665.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] Problem with update notification + + + + + + + + + +

[Mageia-dev] Problem with update notification

+ Ahmad Samir + ahmadsamir3891 at gmail.com +
+ Fri May 13 19:55:46 CEST 2011 +

+
+ +
On 13 May 2011 19:47, Thibaut FRANCOIS <thibautf at gmail.com> wrote:
+> Hello,
+>
+> I updated my desktop computer from mandriva 2010.2 to mageia cauldron.
+> Everything works fine, except one thing :
+> when the "update notification" is red on my taskbar, I click on, but instead
+> of launching mageiaupdate, there is only a new medias scan (the indicator is
+> orange) and finally the indicator became red again.
+>
+> Am I alone with this problem ?
+>
+> Regards,
+> Thibaut
+> PS : I'm using KDE
+>
+
+You probably still have mdkonline; you need mgaonline which has only
+been available less than an hour ago, and it should automatically
+obsolete mdkonline when you update your system.
+
+-- 
+Ahmad Samir
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004666.html b/zarb-ml/mageia-dev/20110513/004666.html new file mode 100644 index 000000000..141c3f610 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004666.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] Problem with update notification + + + + + + + + + +

[Mageia-dev] Problem with update notification

+ Thibaut FRANCOIS + thibautf at gmail.com +
+ Fri May 13 20:09:37 CEST 2011 +

+
+ +
2011/5/13 Ahmad Samir <ahmadsamir3891 at gmail.com>
+
+> On 13 May 2011 19:47, Thibaut FRANCOIS <thibautf at gmail.com> wrote:
+> > Hello,
+> >
+> > I updated my desktop computer from mandriva 2010.2 to mageia cauldron.
+> > Everything works fine, except one thing :
+> > when the "update notification" is red on my taskbar, I click on, but
+> instead
+> > of launching mageiaupdate, there is only a new medias scan (the indicator
+> is
+> > orange) and finally the indicator became red again.
+> >
+> > Am I alone with this problem ?
+> >
+> > Regards,
+> > Thibaut
+> > PS : I'm using KDE
+> >
+>
+> You probably still have mdkonline; you need mgaonline which has only
+> been available less than an hour ago, and it should automatically
+> obsolete mdkonline when you update your system.
+>
+> --
+> Ahmad Samir
+>
+
+Right, mdkonline is installed on my systme. I'm waiting the update with
+mgaonline and I will verify the notification after.
+Thanks
+
+Thibaut
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20110513/a694503f/attachment.html>
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004667.html b/zarb-ml/mageia-dev/20110513/004667.html new file mode 100644 index 000000000..cf78f64ed --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004667.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] Problem with update notification + + + + + + + + + +

[Mageia-dev] Problem with update notification

+ Ahmad Samir + ahmadsamir3891 at gmail.com +
+ Fri May 13 20:59:25 CEST 2011 +

+
+ +
On 13 May 2011 20:09, Thibaut FRANCOIS <thibautf at gmail.com> wrote:
+>
+>
+> 2011/5/13 Ahmad Samir <ahmadsamir3891 at gmail.com>
+>>
+>> On 13 May 2011 19:47, Thibaut FRANCOIS <thibautf at gmail.com> wrote:
+>> > Hello,
+>> >
+>> > I updated my desktop computer from mandriva 2010.2 to mageia cauldron.
+>> > Everything works fine, except one thing :
+>> > when the "update notification" is red on my taskbar, I click on, but
+>> > instead
+>> > of launching mageiaupdate, there is only a new medias scan (the
+>> > indicator is
+>> > orange) and finally the indicator became red again.
+>> >
+>> > Am I alone with this problem ?
+>> >
+>> > Regards,
+>> > Thibaut
+>> > PS : I'm using KDE
+>> >
+>>
+>> You probably still have mdkonline; you need mgaonline which has only
+>> been available less than an hour ago, and it should automatically
+>> obsolete mdkonline when you update your system.
+>>
+>> --
+>> Ahmad Samir
+>
+> Right, mdkonline is installed on my systme. I'm waiting the update with
+> mgaonline and I will verify the notification after.
+> Thanks
+>
+> Thibaut
+>
+
+(Please always post plain text emails when posting to public mailing
+lists, this is the preferred format).
+
+-- 
+Ahmad Samir
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004668.html b/zarb-ml/mageia-dev/20110513/004668.html new file mode 100644 index 000000000..1c1c1c1a6 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004668.html @@ -0,0 +1,61 @@ + + + + [Mageia-dev] Freeze push request: wine + + + + + + + + + +

[Mageia-dev] Freeze push request: wine

+ Ahmad Samir + ahmadsamir3891 at gmail.com +
+ Fri May 13 22:11:24 CEST 2011 +

+
+ +
Please submit wine, this updates it to 1.3.20, with the usual plethora
+of bug fixes that comes with a new version of wine.
+
+-- 
+Ahmad Samir
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004669.html b/zarb-ml/mageia-dev/20110513/004669.html new file mode 100644 index 000000000..0b6f9ae3b --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004669.html @@ -0,0 +1,61 @@ + + + + [Mageia-dev] Freeze push request: flash-player-plugin + + + + + + + + + +

[Mageia-dev] Freeze push request: flash-player-plugin

+ Anssi Hannula + anssi.hannula at iki.fi +
+ Fri May 13 23:45:47 CEST 2011 +

+
+ +
This is an upgrade to flash player 10.3, which we always need the latest
+version of (security etc).
+
+-- 
+Anssi Hannula
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/004670.html b/zarb-ml/mageia-dev/20110513/004670.html new file mode 100644 index 000000000..22022b348 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/004670.html @@ -0,0 +1,69 @@ + + + + [Mageia-dev] Freeze push request: flash-player-plugin + + + + + + + + + +

[Mageia-dev] Freeze push request: flash-player-plugin

+ Anne nicolas + ennael at mageia.org +
+ Fri May 13 23:49:26 CEST 2011 +

+
+ +
2011/5/13 Anssi Hannula <anssi.hannula at iki.fi>:
+> This is an upgrade to flash player 10.3, which we always need the latest
+> version of (security etc).
+
+done
+
+>
+> --
+> Anssi Hannula
+>
+
+
+
+-- 
+Anne
+http://www.mageia.org
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/20110513/author.html b/zarb-ml/mageia-dev/20110513/author.html new file mode 100644 index 000000000..fe54ee878 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/author.html @@ -0,0 +1,157 @@ + + + + The Mageia-dev 13 May 2011 Archive by author + + + + + +

13 May 2011 Archives by author

+ +

Starting: Fri May 13 00:39:55 CEST 2011
+ Ending: Fri May 13 23:49:26 CEST 2011
+ Messages: 22

+

+

+ Last message date: + Fri May 13 23:49:26 CEST 2011
+ Archived on: Fri May 13 23:49:32 CEST 2011 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-dev/20110513/date.html b/zarb-ml/mageia-dev/20110513/date.html new file mode 100644 index 000000000..cb31e4bad --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/date.html @@ -0,0 +1,157 @@ + + + + The Mageia-dev 13 May 2011 Archive by date + + + + + +

13 May 2011 Archives by date

+ +

Starting: Fri May 13 00:39:55 CEST 2011
+ Ending: Fri May 13 23:49:26 CEST 2011
+ Messages: 22

+

+

+ Last message date: + Fri May 13 23:49:26 CEST 2011
+ Archived on: Fri May 13 23:49:32 CEST 2011 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-dev/20110513/index.html b/zarb-ml/mageia-dev/20110513/index.html new file mode 120000 index 000000000..db4b46f72 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/index.html @@ -0,0 +1 @@ +thread.html \ No newline at end of file diff --git a/zarb-ml/mageia-dev/20110513/subject.html b/zarb-ml/mageia-dev/20110513/subject.html new file mode 100644 index 000000000..642fb4703 --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/subject.html @@ -0,0 +1,157 @@ + + + + The Mageia-dev 13 May 2011 Archive by subject + + + + + +

13 May 2011 Archives by subject

+ +

Starting: Fri May 13 00:39:55 CEST 2011
+ Ending: Fri May 13 23:49:26 CEST 2011
+ Messages: 22

+

+

+ Last message date: + Fri May 13 23:49:26 CEST 2011
+ Archived on: Fri May 13 23:49:32 CEST 2011 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-dev/20110513/thread.html b/zarb-ml/mageia-dev/20110513/thread.html new file mode 100644 index 000000000..de5d5c1fa --- /dev/null +++ b/zarb-ml/mageia-dev/20110513/thread.html @@ -0,0 +1,199 @@ + + + + The Mageia-dev 13 May 2011 Archive by thread + + + + + +

13 May 2011 Archives by thread

+ +

Starting: Fri May 13 00:39:55 CEST 2011
+ Ending: Fri May 13 23:49:26 CEST 2011
+ Messages: 22

+

+

+ Last message date: + Fri May 13 23:49:26 CEST 2011
+ Archived on: Fri May 13 23:49:32 CEST 2011 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + -- cgit v1.2.1