diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20121105')
14 files changed, 628 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment-0001.html new file mode 100644 index 000000000..fad5bcf08 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment-0001.html @@ -0,0 +1,122 @@ +Hi,<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Nov 4, 2012 at 4:29 AM, andre999 <span dir="ltr"><<a href="mailto:andre999mga@laposte.net" target="_blank">andre999mga@laposte.net</a>></span> wrote:<br> + +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jehan Pagès a écrit :<br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +Hi,<br> +<br><div class="im"> +On Sat, Nov 3, 2012 at 11:11 PM, PhilippeDidier<br></div><div><div class="h5"> +<<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@laposte.net</a> <mailto:<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@<u></u>laposte.net</a>>> wrote:<br> + + +<br> + Jehan Pagès a écrit :<br> + > Hi,<br> + ><br> + > I noticed we propose only the Jack2 package, but no Jack1. Yet<br> + Jack2 is<br> + > simply another implementation in C++ of the Jack protocol, and not a<br> + > newer version (as the official website also states clearly:<br> + > <a href="http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2" target="_blank">http://trac.jackaudio.org/<u></u>wiki/Q_differenc_jack1_jack2</a> ).<br> + ><br> + > Plus I had a very annoying bug with Ardour when using Jack2, and<br> + people<br> + > on Ardour mailing list told me it was a known issue with Jack2 (both<br> + > Ardour and Jack2 were installed from the Mageia 2 packages). I<br> + compiled<br> + > Jack1, and it indeed fixed the issue.<br> + ><br> + > So I am thinking on proposing a spec for Jack1.<br> + ><br> + > But then I have questions:<br> + ><br> + > 1/ How should I name this package? The jack2 package is named<br> + "jackit"<br> + > and I have no idea where you got that from (I guess this is a shorter<br> + > name for "Jack Audio Connection Kit", but should we really change<br> + > package names this way?<br> + > It is not that long). The official alternative<br> + > name of Jack2 is "jackdmp" (see README here:<br> + > <a href="https://github.com/jackaudio/jack2" target="_blank">https://github.com/jackaudio/<u></u>jack2</a> ). I saw nowhere else this<br> + "jackit"<br> + > naming.<br> + ><br> + We inherit this from Mandrake : in the early years of Mandrake a jack<br> + package already existed but it had nothing to do with JACK (Jack Audio<br> + Connexion Kit) : it was a console frontend for cd rippers, still<br> + provided in Mageia...<br> +<br> + When JACK was imported into Mandrake it had to be given an other name...<br> + so jackit !!!<br> + There was a tonic controversy on Mandrake forum about this in 2003 or<br> + 2004 year.<br> + Mandrake and then Mandriva and and then Mageia are the only<br> + distributions calling JACK package "jackit" ....<br> + > So I am questioning the naming of this existing package, and<br> + would like<br> + > to propose some rename along with a new name for a Jack1 package.<br> + > Maybe simply "jack1" and "jack2"? Or "jack" and "jackdmp"?<br> + ><br> + > 2/ How should the virtual dependency be named?<br> + > The existing "jackit" spec provides a "jackit-devel" and a<br> + "libjack-devel".<br> + ><br> + > I think that none of the names are really fit IMO. First jackit<br> + for the<br> + > same reason as before (I don't see where this name comes from), also<br> + > libjack (and the -devel suffix) because this kit is not *only* a<br> + library<br> + > (there are also the jackd daemon, tools, etc.).<br> + ><br> + > I propose simply "jack" as virtual package name.<br> + ><br> + > How does this sound?<br> + > Thanks.<br> + ><br> + > Jehan<br> + Not simple because of this context ...<br> + If you want to call JACK jack you need to remove first the existing jack<br> + from the repo, and to modify the spec for every package requiring jackit<br> + now, to make them require jack if it is the new package name for JACK .<br> +<br> + Post Scriptum : Reading this I don't know if my explanation is clear<br> + enough ...<br> + A key to understand what I wrote :<br> + "jack" is the name of a package (whatever its content is)<br> + "jackit" is the name of a package<br> + "JACK" is the recursive acronym (Jack Audio Connexion Kit) of the<br> + software you are talking about<br> +<br> +<br> +Ok I understood the deal.<br> +I would personally prefer even a longer package name like<br> +jack-audio-connection-kit. Mageia would gain from having clearer naming.<br> +Especially if we add the Jack1 alternative.<br> +<br> +Now if this is a big deal, and it generates a controversy again, it is<br> +not that a big deal. The question thus is: how do I call Jack1 package<br> +then? And can I say that this new package "Provides: jackit" so that it<br> +works as an alternative to Jack2 (for instance for Ardour)?<br> +Thanks.<br> +<br> +Jehan<br> +</div></div></blockquote> +<br> +why not give jack1 the name :<br> + "jack1 - the Jack Audio Connection Kit 1"<br> +and modify the description to include :<br> + "This is the original C implementation of the Jack Audio Connection Kit protocol (JACK). It is under active development concurrently with jackit (JACK2)"<br> +<br></blockquote><div><br>I'll do this like this, then, and propose a SPEC to my mentor, maybe today.<br><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> + + +It might also be a good idea to modify the jackit description to indicate that it is concurrent to jack1 as well.<br> +And maybe rename it to jack2, if it is not too complicated ?<br> +<br></blockquote><div><br>I guess the maintainer of this package will have to do this. I'll search for his email.<br>Thanks all.<br><br>Jehan<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> + + +We could always use provides to accommodate packages requiring JACK.<br> +<br> +Just some suggestions ...<span class="HOEnZb"><font color="#888888"><br> +<br> +-- <br> +André<br> +</font></span></blockquote></div><br></div> diff --git a/zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment.html b/zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment.html new file mode 100644 index 000000000..fad5bcf08 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/35eded3e/attachment.html @@ -0,0 +1,122 @@ +Hi,<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Nov 4, 2012 at 4:29 AM, andre999 <span dir="ltr"><<a href="mailto:andre999mga@laposte.net" target="_blank">andre999mga@laposte.net</a>></span> wrote:<br> + +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Jehan Pagès a écrit :<br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +Hi,<br> +<br><div class="im"> +On Sat, Nov 3, 2012 at 11:11 PM, PhilippeDidier<br></div><div><div class="h5"> +<<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@laposte.net</a> <mailto:<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@<u></u>laposte.net</a>>> wrote:<br> + + +<br> + Jehan Pagès a écrit :<br> + > Hi,<br> + ><br> + > I noticed we propose only the Jack2 package, but no Jack1. Yet<br> + Jack2 is<br> + > simply another implementation in C++ of the Jack protocol, and not a<br> + > newer version (as the official website also states clearly:<br> + > <a href="http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2" target="_blank">http://trac.jackaudio.org/<u></u>wiki/Q_differenc_jack1_jack2</a> ).<br> + ><br> + > Plus I had a very annoying bug with Ardour when using Jack2, and<br> + people<br> + > on Ardour mailing list told me it was a known issue with Jack2 (both<br> + > Ardour and Jack2 were installed from the Mageia 2 packages). I<br> + compiled<br> + > Jack1, and it indeed fixed the issue.<br> + ><br> + > So I am thinking on proposing a spec for Jack1.<br> + ><br> + > But then I have questions:<br> + ><br> + > 1/ How should I name this package? The jack2 package is named<br> + "jackit"<br> + > and I have no idea where you got that from (I guess this is a shorter<br> + > name for "Jack Audio Connection Kit", but should we really change<br> + > package names this way?<br> + > It is not that long). The official alternative<br> + > name of Jack2 is "jackdmp" (see README here:<br> + > <a href="https://github.com/jackaudio/jack2" target="_blank">https://github.com/jackaudio/<u></u>jack2</a> ). I saw nowhere else this<br> + "jackit"<br> + > naming.<br> + ><br> + We inherit this from Mandrake : in the early years of Mandrake a jack<br> + package already existed but it had nothing to do with JACK (Jack Audio<br> + Connexion Kit) : it was a console frontend for cd rippers, still<br> + provided in Mageia...<br> +<br> + When JACK was imported into Mandrake it had to be given an other name...<br> + so jackit !!!<br> + There was a tonic controversy on Mandrake forum about this in 2003 or<br> + 2004 year.<br> + Mandrake and then Mandriva and and then Mageia are the only<br> + distributions calling JACK package "jackit" ....<br> + > So I am questioning the naming of this existing package, and<br> + would like<br> + > to propose some rename along with a new name for a Jack1 package.<br> + > Maybe simply "jack1" and "jack2"? Or "jack" and "jackdmp"?<br> + ><br> + > 2/ How should the virtual dependency be named?<br> + > The existing "jackit" spec provides a "jackit-devel" and a<br> + "libjack-devel".<br> + ><br> + > I think that none of the names are really fit IMO. First jackit<br> + for the<br> + > same reason as before (I don't see where this name comes from), also<br> + > libjack (and the -devel suffix) because this kit is not *only* a<br> + library<br> + > (there are also the jackd daemon, tools, etc.).<br> + ><br> + > I propose simply "jack" as virtual package name.<br> + ><br> + > How does this sound?<br> + > Thanks.<br> + ><br> + > Jehan<br> + Not simple because of this context ...<br> + If you want to call JACK jack you need to remove first the existing jack<br> + from the repo, and to modify the spec for every package requiring jackit<br> + now, to make them require jack if it is the new package name for JACK .<br> +<br> + Post Scriptum : Reading this I don't know if my explanation is clear<br> + enough ...<br> + A key to understand what I wrote :<br> + "jack" is the name of a package (whatever its content is)<br> + "jackit" is the name of a package<br> + "JACK" is the recursive acronym (Jack Audio Connexion Kit) of the<br> + software you are talking about<br> +<br> +<br> +Ok I understood the deal.<br> +I would personally prefer even a longer package name like<br> +jack-audio-connection-kit. Mageia would gain from having clearer naming.<br> +Especially if we add the Jack1 alternative.<br> +<br> +Now if this is a big deal, and it generates a controversy again, it is<br> +not that a big deal. The question thus is: how do I call Jack1 package<br> +then? And can I say that this new package "Provides: jackit" so that it<br> +works as an alternative to Jack2 (for instance for Ardour)?<br> +Thanks.<br> +<br> +Jehan<br> +</div></div></blockquote> +<br> +why not give jack1 the name :<br> + "jack1 - the Jack Audio Connection Kit 1"<br> +and modify the description to include :<br> + "This is the original C implementation of the Jack Audio Connection Kit protocol (JACK). It is under active development concurrently with jackit (JACK2)"<br> +<br></blockquote><div><br>I'll do this like this, then, and propose a SPEC to my mentor, maybe today.<br><br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> + + +It might also be a good idea to modify the jackit description to indicate that it is concurrent to jack1 as well.<br> +And maybe rename it to jack2, if it is not too complicated ?<br> +<br></blockquote><div><br>I guess the maintainer of this package will have to do this. I'll search for his email.<br>Thanks all.<br><br>Jehan<br> <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> + + +We could always use provides to accommodate packages requiring JACK.<br> +<br> +Just some suggestions ...<span class="HOEnZb"><font color="#888888"><br> +<br> +-- <br> +André<br> +</font></span></blockquote></div><br></div> diff --git a/zarb-ml/mageia-dev/attachments/20121105/9bf89ccc/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121105/9bf89ccc/attachment-0001.asc new file mode 100644 index 000000000..4a190d61b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/9bf89ccc/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQmBVYT1rWTfpocyQRAnZ+AJwPiJ89SLQwNMo981oP+5Sc81iVQQCgqvq/ +BJWvhFcI7pY8QxxpSE7XM5Y= +=iBY5 +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121105/9bf89ccc/attachment.asc b/zarb-ml/mageia-dev/attachments/20121105/9bf89ccc/attachment.asc new file mode 100644 index 000000000..4a190d61b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/9bf89ccc/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQmBVYT1rWTfpocyQRAnZ+AJwPiJ89SLQwNMo981oP+5Sc81iVQQCgqvq/ +BJWvhFcI7pY8QxxpSE7XM5Y= +=iBY5 +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121105/a67215aa/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121105/a67215aa/attachment-0001.html new file mode 100644 index 000000000..fabf837f3 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/a67215aa/attachment-0001.html @@ -0,0 +1,27 @@ +then please push rpmlint-mageia-policy into infra. Thanks.<br><div class="gmail_extra"><br><br><div class="gmail_quote">2012/11/5 Thomas Backlund <span dir="ltr"><<a href="mailto:tmb@mageia.org" target="_blank">tmb@mageia.org</a>></span><br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">04.11.2012 19:13, Funda Wang skrev:<div class="im"><br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +We already have the similar problem in the period of mandriva, packages<br> +with same names but different archs won't be deleted from repository.<br> +Maybe somebody could check youri's code to fix this problem.<br> +<br> +As for the deps list, I think this page shows them all:<br> +<a href="http://check.mageia.org/cauldron/missing.html" target="_blank">http://check.mageia.org/<u></u>cauldron/missing.html</a><br> +<br> +And, there are some packages cannot be uploaded due to rpmlint polciy<br> +for filenames, which I cannot deal with :( Personally, I don't think we<br> +should check package file list for restricted filenames.<br> +<br> +</blockquote> +<br></div> +Actually checking file lists is good as it catches some packaging bugs..<br> +<br> +If you need new exceptions, add them to the rpmlint-mageia-policy<br> +package, and notify sysadmins of the need and we'll update it on<br> +build infra.<br> +<br> +--<br> +Thomas<br> +<br> +<br> +</blockquote></div><br></div> diff --git a/zarb-ml/mageia-dev/attachments/20121105/a67215aa/attachment.html b/zarb-ml/mageia-dev/attachments/20121105/a67215aa/attachment.html new file mode 100644 index 000000000..fabf837f3 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/a67215aa/attachment.html @@ -0,0 +1,27 @@ +then please push rpmlint-mageia-policy into infra. Thanks.<br><div class="gmail_extra"><br><br><div class="gmail_quote">2012/11/5 Thomas Backlund <span dir="ltr"><<a href="mailto:tmb@mageia.org" target="_blank">tmb@mageia.org</a>></span><br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">04.11.2012 19:13, Funda Wang skrev:<div class="im"><br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +We already have the similar problem in the period of mandriva, packages<br> +with same names but different archs won't be deleted from repository.<br> +Maybe somebody could check youri's code to fix this problem.<br> +<br> +As for the deps list, I think this page shows them all:<br> +<a href="http://check.mageia.org/cauldron/missing.html" target="_blank">http://check.mageia.org/<u></u>cauldron/missing.html</a><br> +<br> +And, there are some packages cannot be uploaded due to rpmlint polciy<br> +for filenames, which I cannot deal with :( Personally, I don't think we<br> +should check package file list for restricted filenames.<br> +<br> +</blockquote> +<br></div> +Actually checking file lists is good as it catches some packaging bugs..<br> +<br> +If you need new exceptions, add them to the rpmlint-mageia-policy<br> +package, and notify sysadmins of the need and we'll update it on<br> +build infra.<br> +<br> +--<br> +Thomas<br> +<br> +<br> +</blockquote></div><br></div> diff --git a/zarb-ml/mageia-dev/attachments/20121105/c34b3d05/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121105/c34b3d05/attachment-0001.html new file mode 100644 index 000000000..d9fb4b96c --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/c34b3d05/attachment-0001.html @@ -0,0 +1,45 @@ +<div>We already have the similar problem in the period of mandriva, packages with same names but different archs won't be deleted from repository. Maybe somebody could check youri's code to fix this problem.<br></div> +<div><br></div><div>As for the deps list, I think this page shows them all:</div><div><a href="http://check.mageia.org/cauldron/missing.html">http://check.mageia.org/cauldron/missing.html</a></div><div><br></div><div>And, there are some packages cannot be uploaded due to rpmlint polciy for filenames, which I cannot deal with :( Personally, I don't think we should check package file list for restricted filenames.</div> +<div><br></div><div>Regards.</div><div><br></div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2012/11/4 PhilippeDidier <span dir="ltr"><<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@laposte.net</a>></span><br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br> +To Funda<br> +<br> +I'm always impressed by the huge work you do for Mageia...<br> +<br> +There's a little problem with ruby updates in Cauldron : as shikamaru is<br> +always the official maintainer you may not be advertised of this :<br> +<a href="http://check.mageia.org/cauldron/shikamaru/dependencies.html" target="_blank">http://check.mageia.org/cauldron/shikamaru/dependencies.html</a><br> +<br> +indeed, in cauldron repository we have coexisting ruby-*-doc packages as<br> +if the last update, with noarch suffix, has not obsoleted the last old<br> +version of some doc rpm which didn't have the noarch suffix:<br> +for instance<br> +ruby-BlueCloth-doc-2.2.0-3.mga3 remains besides<br> +ruby-BlueCloth-doc-2.2.0-4.mga3.noarch<br> +<br> +Perhaps sysadmin will have to remove some ruby-*-doc rpm if they<br> +don't explicitely have mga3.noarch extension<br> +<br> +here is a list of few examples of rpm that have to be removed in 586<br> +and x86_64 repositories :<br> +ruby-atk-doc-1.0.3-1.mga2<br> +ruby-BlueCloth-doc-2.2.0-3.mga3<br> +ruby-curb-doc-0.7.15-1.mga1<br> +ruby-eventmachine-doc-0.12.10-3.mga1<br> +<br> +we can explore the whole repo or simply use<br> +<a href="http://check.mageia.org/cauldron/shikamaru/dependencies.html" target="_blank">http://check.mageia.org/cauldron/shikamaru/dependencies.html</a><br> +to get the list<br> +<br> +Same for some other non doc rpms<br> +ruby-em-http-request-0.3.0-1.mga1 remains besides<br> +ruby-em-http-request-1.0.3-2.mga3.noarch<br> +<br> +Hope this will help to decrease the number of "broken dependancies" (at<br> +least 60 will be resolved...)<br> +<br> +Regards to Funda and sysadmins<br> +<br> +Philippe<br> +<br> +</blockquote></div><br></div> diff --git a/zarb-ml/mageia-dev/attachments/20121105/c34b3d05/attachment.html b/zarb-ml/mageia-dev/attachments/20121105/c34b3d05/attachment.html new file mode 100644 index 000000000..d9fb4b96c --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/c34b3d05/attachment.html @@ -0,0 +1,45 @@ +<div>We already have the similar problem in the period of mandriva, packages with same names but different archs won't be deleted from repository. Maybe somebody could check youri's code to fix this problem.<br></div> +<div><br></div><div>As for the deps list, I think this page shows them all:</div><div><a href="http://check.mageia.org/cauldron/missing.html">http://check.mageia.org/cauldron/missing.html</a></div><div><br></div><div>And, there are some packages cannot be uploaded due to rpmlint polciy for filenames, which I cannot deal with :( Personally, I don't think we should check package file list for restricted filenames.</div> +<div><br></div><div>Regards.</div><div><br></div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2012/11/4 PhilippeDidier <span dir="ltr"><<a href="mailto:philippedidier@laposte.net" target="_blank">philippedidier@laposte.net</a>></span><br> +<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi<br> +To Funda<br> +<br> +I'm always impressed by the huge work you do for Mageia...<br> +<br> +There's a little problem with ruby updates in Cauldron : as shikamaru is<br> +always the official maintainer you may not be advertised of this :<br> +<a href="http://check.mageia.org/cauldron/shikamaru/dependencies.html" target="_blank">http://check.mageia.org/cauldron/shikamaru/dependencies.html</a><br> +<br> +indeed, in cauldron repository we have coexisting ruby-*-doc packages as<br> +if the last update, with noarch suffix, has not obsoleted the last old<br> +version of some doc rpm which didn't have the noarch suffix:<br> +for instance<br> +ruby-BlueCloth-doc-2.2.0-3.mga3 remains besides<br> +ruby-BlueCloth-doc-2.2.0-4.mga3.noarch<br> +<br> +Perhaps sysadmin will have to remove some ruby-*-doc rpm if they<br> +don't explicitely have mga3.noarch extension<br> +<br> +here is a list of few examples of rpm that have to be removed in 586<br> +and x86_64 repositories :<br> +ruby-atk-doc-1.0.3-1.mga2<br> +ruby-BlueCloth-doc-2.2.0-3.mga3<br> +ruby-curb-doc-0.7.15-1.mga1<br> +ruby-eventmachine-doc-0.12.10-3.mga1<br> +<br> +we can explore the whole repo or simply use<br> +<a href="http://check.mageia.org/cauldron/shikamaru/dependencies.html" target="_blank">http://check.mageia.org/cauldron/shikamaru/dependencies.html</a><br> +to get the list<br> +<br> +Same for some other non doc rpms<br> +ruby-em-http-request-0.3.0-1.mga1 remains besides<br> +ruby-em-http-request-1.0.3-2.mga3.noarch<br> +<br> +Hope this will help to decrease the number of "broken dependancies" (at<br> +least 60 will be resolved...)<br> +<br> +Regards to Funda and sysadmins<br> +<br> +Philippe<br> +<br> +</blockquote></div><br></div> diff --git a/zarb-ml/mageia-dev/attachments/20121105/d0495393/attachment-0001.mht b/zarb-ml/mageia-dev/attachments/20121105/d0495393/attachment-0001.mht new file mode 100644 index 000000000..cca189682 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/d0495393/attachment-0001.mht @@ -0,0 +1,99 @@ +[From nobody Mon Nov 5 18:58:57 2012 +Return-Path: <distributor-list-bounces@gnome.org> +X-Original-To: list-gnome@vitters.nl +Delivered-To: list-gnome@vitters.nl +Received: from menubar.gnome.org (menubar.gnome.org [209.132.180.169]) + by bkor.dhs.org (Postfix) with ESMTP id 99565500371 + for <list-gnome@vitters.nl>; Mon, 5 Nov 2012 16:43:08 +0100 (CET) +Received: from menubar.gnome.org (localhost.localdomain [127.0.0.1]) + by menubar.gnome.org (Postfix) with ESMTP id D24EF75081D; + Mon, 5 Nov 2012 15:43:07 +0000 (UTC) +X-Original-To: distributor-list@gnome.org +Delivered-To: distributor-list@gnome.org +Received: from localhost (localhost.localdomain [127.0.0.1]) + by menubar.gnome.org (Postfix) with ESMTP id 5B5477504E2; + Mon, 5 Nov 2012 15:43:04 +0000 (UTC) +X-Virus-Scanned: by amavisd-new at gnome.org +X-Spam-Flag: NO +X-Spam-Score: -2.7 +X-Spam-Level: +X-Spam-Status: No, score=-2.7 tagged_above=-999 required=2 + tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, + DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, + SPF_PASS=-0.001] autolearn=ham +Received: from menubar.gnome.org ([127.0.0.1]) + by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id 10OvP6bVdjPE; Mon, 5 Nov 2012 15:43:01 +0000 (UTC) +Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com + [209.85.216.47]) + by menubar.gnome.org (Postfix) with ESMTP id 1E0697501D4; + Mon, 5 Nov 2012 15:43:00 +0000 (UTC) +Received: by mail-qa0-f47.google.com with SMTP id t11so417431qaa.6 + for <multiple recipients>; Mon, 05 Nov 2012 07:42:59 -0800 (PST) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; + h=mime-version:date:message-id:subject:from:to:cc:content-type; + bh=2vANqCFSEA5xxD7prVZYVClbkH9eDunkyovslNTbtS0=; + b=S7s3wnY191eJFSmKbp30qwA+m8QdW57j/ReJhQ3m38KhTFCR0acHTyBWzjnbMU5UwN + 7f8o109Mi1wEpwShO+tjzXuVs9H69ncZGNS8Z/dk/S1jAEbRU+edHMcZQkziuihiQzv9 + 6hNp3iOZNAt98pezJJUfIM/xQYcvyGDp1UYAZm/yGV7N2awNpQT6KdsZE6Hv9RHE4Dc0 + RdVElwVw2rmZjDx3WcZNar886e1BpdaTzLuw9iyTKVDtD8wuxo5gwwUmbhmpq1EeugbY + yW+pdGq+GfxDSQ1+nYk18pP3+mn+eDo3Z3fvhjpaC03i7EoQom2+NiP6CaFRLIudpBLq + Iu5A== +MIME-Version: 1.0 +Received: by 10.229.201.216 with SMTP id fb24mr3475527qcb.89.1352130179435; + Mon, 05 Nov 2012 07:42:59 -0800 (PST) +Received: by 10.49.76.10 with HTTP; Mon, 5 Nov 2012 07:42:59 -0800 (PST) +Date: Mon, 5 Nov 2012 10:42:59 -0500 +Message-ID: <CAFwd_vDmzG4JzOitajUrhWMviACw8mS9GkDUyvHDaiDXKE945Q@mail.gmail.com> +Subject: fallback mode +From: Matthias Clasen <matthias.clasen@gmail.com> +To: distributor-list@gnome.org +Cc: GNOME release team <release-team@gnome.org> +X-BeenThere: distributor-list@gnome.org +X-Mailman-Version: 2.1.14 +Precedence: list +List-Id: Discussion and collaboration list for distributors of GNOME + <distributor-list.gnome.org> +List-Unsubscribe: <https://mail.gnome.org/mailman/options/distributor-list>, + <mailto:distributor-list-request@gnome.org?subject=unsubscribe> +List-Archive: <https://mail.gnome.org/archives/distributor-list/> +List-Post: <mailto:distributor-list@gnome.org> +List-Help: <mailto:distributor-list-request@gnome.org?subject=help> +List-Subscribe: <https://mail.gnome.org/mailman/listinfo/distributor-list>, + <mailto:distributor-list-request@gnome.org?subject=subscribe> +Content-Type: text/plain; charset="us-ascii" +Content-Transfer-Encoding: 7bit +Errors-To: distributor-list-bounces@gnome.org +Sender: distributor-list-bounces@gnome.org + +I'm writing to inform you that the release team discussed +https://live.gnome.org/ThreePointSeven/Features/DropOrFixFallbackMode +yesterday. We've come to the conclusion that we can't maintain +fallback mode in reasonable quality, and are better off dropping it. + +We're now working on organizing this so that it does not create more +fallout than necessary. As part of this, I'm reaching out to our +distributors to see what parts they care about. We haven't worked out +a detailed plan for 3.8 tasks yet, but the feature page should give +you a good idea about what things will be part of the 3.8 plan: + +- remove the 'forced fallback' ui in control-center + +- unify 'gnome can't run' and 'failwhale' UX + +- move background rendering entirely into gnome-shell; this is most +likely to cause some problems for other environments that reuse g-s-d +for background rendering. Splitting off the desktop-rendering +functionality from nautilus is a separate issue, and does not +necessarily have to happen for 3.8. + +Please watch the feature page for more details, as we work them out, +and please contact us with your concerns. Lets work together and +minimize the pain of this transition. + +Matthias, for the release team +_______________________________________________ +distributor-list mailing list +distributor-list@gnome.org +https://mail.gnome.org/mailman/listinfo/distributor-list +]
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20121105/d0495393/attachment.mht b/zarb-ml/mageia-dev/attachments/20121105/d0495393/attachment.mht new file mode 100644 index 000000000..82483daec --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/d0495393/attachment.mht @@ -0,0 +1,99 @@ +[From nobody Mon Nov 5 18:58:56 2012 +Return-Path: <distributor-list-bounces@gnome.org> +X-Original-To: list-gnome@vitters.nl +Delivered-To: list-gnome@vitters.nl +Received: from menubar.gnome.org (menubar.gnome.org [209.132.180.169]) + by bkor.dhs.org (Postfix) with ESMTP id 99565500371 + for <list-gnome@vitters.nl>; Mon, 5 Nov 2012 16:43:08 +0100 (CET) +Received: from menubar.gnome.org (localhost.localdomain [127.0.0.1]) + by menubar.gnome.org (Postfix) with ESMTP id D24EF75081D; + Mon, 5 Nov 2012 15:43:07 +0000 (UTC) +X-Original-To: distributor-list@gnome.org +Delivered-To: distributor-list@gnome.org +Received: from localhost (localhost.localdomain [127.0.0.1]) + by menubar.gnome.org (Postfix) with ESMTP id 5B5477504E2; + Mon, 5 Nov 2012 15:43:04 +0000 (UTC) +X-Virus-Scanned: by amavisd-new at gnome.org +X-Spam-Flag: NO +X-Spam-Score: -2.7 +X-Spam-Level: +X-Spam-Status: No, score=-2.7 tagged_above=-999 required=2 + tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, + DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, + SPF_PASS=-0.001] autolearn=ham +Received: from menubar.gnome.org ([127.0.0.1]) + by localhost (menubar.gnome.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id 10OvP6bVdjPE; Mon, 5 Nov 2012 15:43:01 +0000 (UTC) +Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com + [209.85.216.47]) + by menubar.gnome.org (Postfix) with ESMTP id 1E0697501D4; + Mon, 5 Nov 2012 15:43:00 +0000 (UTC) +Received: by mail-qa0-f47.google.com with SMTP id t11so417431qaa.6 + for <multiple recipients>; Mon, 05 Nov 2012 07:42:59 -0800 (PST) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; + h=mime-version:date:message-id:subject:from:to:cc:content-type; + bh=2vANqCFSEA5xxD7prVZYVClbkH9eDunkyovslNTbtS0=; + b=S7s3wnY191eJFSmKbp30qwA+m8QdW57j/ReJhQ3m38KhTFCR0acHTyBWzjnbMU5UwN + 7f8o109Mi1wEpwShO+tjzXuVs9H69ncZGNS8Z/dk/S1jAEbRU+edHMcZQkziuihiQzv9 + 6hNp3iOZNAt98pezJJUfIM/xQYcvyGDp1UYAZm/yGV7N2awNpQT6KdsZE6Hv9RHE4Dc0 + RdVElwVw2rmZjDx3WcZNar886e1BpdaTzLuw9iyTKVDtD8wuxo5gwwUmbhmpq1EeugbY + yW+pdGq+GfxDSQ1+nYk18pP3+mn+eDo3Z3fvhjpaC03i7EoQom2+NiP6CaFRLIudpBLq + Iu5A== +MIME-Version: 1.0 +Received: by 10.229.201.216 with SMTP id fb24mr3475527qcb.89.1352130179435; + Mon, 05 Nov 2012 07:42:59 -0800 (PST) +Received: by 10.49.76.10 with HTTP; Mon, 5 Nov 2012 07:42:59 -0800 (PST) +Date: Mon, 5 Nov 2012 10:42:59 -0500 +Message-ID: <CAFwd_vDmzG4JzOitajUrhWMviACw8mS9GkDUyvHDaiDXKE945Q@mail.gmail.com> +Subject: fallback mode +From: Matthias Clasen <matthias.clasen@gmail.com> +To: distributor-list@gnome.org +Cc: GNOME release team <release-team@gnome.org> +X-BeenThere: distributor-list@gnome.org +X-Mailman-Version: 2.1.14 +Precedence: list +List-Id: Discussion and collaboration list for distributors of GNOME + <distributor-list.gnome.org> +List-Unsubscribe: <https://mail.gnome.org/mailman/options/distributor-list>, + <mailto:distributor-list-request@gnome.org?subject=unsubscribe> +List-Archive: <https://mail.gnome.org/archives/distributor-list/> +List-Post: <mailto:distributor-list@gnome.org> +List-Help: <mailto:distributor-list-request@gnome.org?subject=help> +List-Subscribe: <https://mail.gnome.org/mailman/listinfo/distributor-list>, + <mailto:distributor-list-request@gnome.org?subject=subscribe> +Content-Type: text/plain; charset="us-ascii" +Content-Transfer-Encoding: 7bit +Errors-To: distributor-list-bounces@gnome.org +Sender: distributor-list-bounces@gnome.org + +I'm writing to inform you that the release team discussed +https://live.gnome.org/ThreePointSeven/Features/DropOrFixFallbackMode +yesterday. We've come to the conclusion that we can't maintain +fallback mode in reasonable quality, and are better off dropping it. + +We're now working on organizing this so that it does not create more +fallout than necessary. As part of this, I'm reaching out to our +distributors to see what parts they care about. We haven't worked out +a detailed plan for 3.8 tasks yet, but the feature page should give +you a good idea about what things will be part of the 3.8 plan: + +- remove the 'forced fallback' ui in control-center + +- unify 'gnome can't run' and 'failwhale' UX + +- move background rendering entirely into gnome-shell; this is most +likely to cause some problems for other environments that reuse g-s-d +for background rendering. Splitting off the desktop-rendering +functionality from nautilus is a separate issue, and does not +necessarily have to happen for 3.8. + +Please watch the feature page for more details, as we work them out, +and please contact us with your concerns. Lets work together and +minimize the pain of this transition. + +Matthias, for the release team +_______________________________________________ +distributor-list mailing list +distributor-list@gnome.org +https://mail.gnome.org/mailman/listinfo/distributor-list +]
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20121105/d9f12acb/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121105/d9f12acb/attachment-0001.asc new file mode 100644 index 000000000..c65e5ca0b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/d9f12acb/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQl8LmT1rWTfpocyQRAoR6AJ9es/JZbx9aS0iXC7Kbz8RQM/te/ACgvr9K +2KkC9GS+32F1hxxlS0Qxj4Y= +=J7Iy +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121105/d9f12acb/attachment.asc b/zarb-ml/mageia-dev/attachments/20121105/d9f12acb/attachment.asc new file mode 100644 index 000000000..c65e5ca0b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/d9f12acb/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQl8LmT1rWTfpocyQRAoR6AJ9es/JZbx9aS0iXC7Kbz8RQM/te/ACgvr9K +2KkC9GS+32F1hxxlS0Qxj4Y= +=J7Iy +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121105/ec39c5a1/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20121105/ec39c5a1/attachment-0001.asc new file mode 100644 index 000000000..3d4edb531 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/ec39c5a1/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQlwyNT1rWTfpocyQRAitkAKCL+4lnBjhTTeZpQCUYroYyaHow/ACfZEy/ +yDTgaoOlEdysi1hXecK6vig= +=G4ak +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20121105/ec39c5a1/attachment.asc b/zarb-ml/mageia-dev/attachments/20121105/ec39c5a1/attachment.asc new file mode 100644 index 000000000..3d4edb531 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20121105/ec39c5a1/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBQlwyNT1rWTfpocyQRAitkAKCL+4lnBjhTTeZpQCUYroYyaHow/ACfZEy/ +yDTgaoOlEdysi1hXecK6vig= +=G4ak +-----END PGP SIGNATURE----- |