diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20120628')
14 files changed, 688 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20120628/01fac143/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20120628/01fac143/attachment-0001.html new file mode 100644 index 000000000..3fcd4e151 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/01fac143/attachment-0001.html @@ -0,0 +1,25 @@ +<br><br><div class="gmail_quote">2012/6/28 Olav Vitters <span dir="ltr"><<a href="mailto:olav@vitters.nl" target="_blank">olav@vitters.nl</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +<div class="im">On Wed, Jun 27, 2012 at 01:38:03AM +0200, <a href="mailto:n54@gmx.com">n54@gmx.com</a> wrote:<br> +> I have got an idea to fix this bug with a new drak tool (DrakSpell?).<br> +> It would be an assistant with a list of all available languages with<br> +> all their variants to select and install. And the trick: it will<br> +> install a package (like hunspell-en) and remove (rm -f) the unselected<br> +> dicts (en_CA, en_GB ...).<br> +<br> +</div>How would you be able to select a previously not selected language?<br> +<br> +Maybe package differently:<br> + /usr/real/spell/something<br> +and then have links from<br> + /usr/spell/something<br> +to the real languages?<br> +<br> +Then you could remove and add languages as you please, plus RPM would be<br> +more or less happy? Think you can teach it to ignore symlinks with ghost<br> +maybe?<br> +<span class="HOEnZb"><font color="#888888"><br> +--<br> +Regards,<br> +Olav<br> +</font></span></blockquote></div><br>I filled a bug in KDe bug tracker<br><a href="https://bugs.kde.org/show_bug.cgi?id=302689">https://bugs.kde.org/show_bug.cgi?id=302689</a><br clear="all"><br>-- <br><div>Dimitrios Glentadakis</div> +<br> diff --git a/zarb-ml/mageia-dev/attachments/20120628/01fac143/attachment.html b/zarb-ml/mageia-dev/attachments/20120628/01fac143/attachment.html new file mode 100644 index 000000000..3fcd4e151 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/01fac143/attachment.html @@ -0,0 +1,25 @@ +<br><br><div class="gmail_quote">2012/6/28 Olav Vitters <span dir="ltr"><<a href="mailto:olav@vitters.nl" target="_blank">olav@vitters.nl</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> +<div class="im">On Wed, Jun 27, 2012 at 01:38:03AM +0200, <a href="mailto:n54@gmx.com">n54@gmx.com</a> wrote:<br> +> I have got an idea to fix this bug with a new drak tool (DrakSpell?).<br> +> It would be an assistant with a list of all available languages with<br> +> all their variants to select and install. And the trick: it will<br> +> install a package (like hunspell-en) and remove (rm -f) the unselected<br> +> dicts (en_CA, en_GB ...).<br> +<br> +</div>How would you be able to select a previously not selected language?<br> +<br> +Maybe package differently:<br> + /usr/real/spell/something<br> +and then have links from<br> + /usr/spell/something<br> +to the real languages?<br> +<br> +Then you could remove and add languages as you please, plus RPM would be<br> +more or less happy? Think you can teach it to ignore symlinks with ghost<br> +maybe?<br> +<span class="HOEnZb"><font color="#888888"><br> +--<br> +Regards,<br> +Olav<br> +</font></span></blockquote></div><br>I filled a bug in KDe bug tracker<br><a href="https://bugs.kde.org/show_bug.cgi?id=302689">https://bugs.kde.org/show_bug.cgi?id=302689</a><br clear="all"><br>-- <br><div>Dimitrios Glentadakis</div> +<br> diff --git a/zarb-ml/mageia-dev/attachments/20120628/0cd598a7/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20120628/0cd598a7/attachment-0001.asc new file mode 100644 index 000000000..7aa380886 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/0cd598a7/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBP67rBT1rWTfpocyQRAughAKCNNWB4Jf1LO0Q0z5lcjHn6I53F2QCggBv7 +e+A6DvD3VSpme/E3GP/HwR0= +=A1D3 +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20120628/0cd598a7/attachment.asc b/zarb-ml/mageia-dev/attachments/20120628/0cd598a7/attachment.asc new file mode 100644 index 000000000..7aa380886 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/0cd598a7/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBP67rBT1rWTfpocyQRAughAKCNNWB4Jf1LO0Q0z5lcjHn6I53F2QCggBv7 +e+A6DvD3VSpme/E3GP/HwR0= +=A1D3 +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20120628/1340ac53/attachment-0001.mht b/zarb-ml/mageia-dev/attachments/20120628/1340ac53/attachment-0001.mht new file mode 100644 index 000000000..96573e8cf --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/1340ac53/attachment-0001.mht @@ -0,0 +1,81 @@ +[From nobody Thu Jun 28 10:54:49 2012 +Return-Path: <desktop-devel-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 0AD645002AC + for <list-gnome@vitters.nl>; Mon, 25 Jun 2012 15:45:27 +0200 (CEST) +Received: from menubar.gnome.org (localhost.localdomain [127.0.0.1]) + by menubar.gnome.org (Postfix) with ESMTP id C75FA75043A; + Mon, 25 Jun 2012 13:45:25 +0000 (UTC) +X-Original-To: desktop-devel-list@gnome.org +Delivered-To: desktop-devel-list@gnome.org +Received: from localhost (localhost.localdomain [127.0.0.1]) + by menubar.gnome.org (Postfix) with ESMTP id 5809E750120 + for <desktop-devel-list@gnome.org>; + Mon, 25 Jun 2012 13:45:19 +0000 (UTC) +X-Virus-Scanned: by amavisd-new at gnome.org +X-Spam-Flag: NO +X-Spam-Score: -2.601 +X-Spam-Level: +X-Spam-Status: No, score=-2.601 tagged_above=-999 required=2 + tests=[BAYES_00=-1.9, 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 XVsfYTlh1sTb for <desktop-devel-list@gnome.org>; + Mon, 25 Jun 2012 13:45:15 +0000 (UTC) +Received: from smtp4.mundo-r.com (smtp3.mundo-r.com [212.51.32.191]) + by menubar.gnome.org (Postfix) with ESMTP id 962AA750103 + for <desktop-devel-list@gnome.org>; + Mon, 25 Jun 2012 13:45:05 +0000 (UTC) +X-IronPort-Anti-Spam-Filtered: true +X-IronPort-Anti-Spam-Result: AlkGAE5q6E9bdWOb/2dsb2JhbABEFoMrghmwRoEHgkKBCwIFIQIRAkwNCAEBiAcEB5dYjkGSL4EgjwOBEgOVLoESjm+Cew +X-IronPort-AV: E=Sophos;i="4.77,472,1336341600"; d="scan'208";a="923946298" +Received: from fanzine.igalia.com ([91.117.99.155]) + by smtp4.mundo-r.com with ESMTP; 25 Jun 2012 15:45:03 +0200 +Received: from c-98-217-239-60.hsd1.nh.comcast.net ([98.217.239.60] + helo=[192.168.35.105]) by fanzine.igalia.com with esmtpsa + (Cipher TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim) + id 1Sj9bD-0003F4-FA + for <desktop-devel-list@gnome.org>; Mon, 25 Jun 2012 15:45:03 +0200 +Message-ID: <4FE86B54.70306@igalia.com> +Date: Mon, 25 Jun 2012 09:44:52 -0400 +From: Joanmarie Diggs <jdiggs@igalia.com> +User-Agent: Mozilla/5.0 (X11; Linux x86_64; + rv:13.0) Gecko/20120615 Thunderbird/13.0.1 +MIME-Version: 1.0 +To: desktop-devel-list <desktop-devel-list@gnome.org> +Subject: [PROPOSAL] GNOME Goal for 3.8: No more Python 2 +X-Enigmail-Version: 1.4.2 +X-BeenThere: desktop-devel-list@gnome.org +X-Mailman-Version: 2.1.14 +Precedence: list +List-Id: GNOME Desktop Development List <desktop-devel-list.gnome.org> +List-Unsubscribe: <https://mail.gnome.org/mailman/options/desktop-devel-list>, + <mailto:desktop-devel-list-request@gnome.org?subject=unsubscribe> +List-Archive: <https://mail.gnome.org/archives/desktop-devel-list/> +List-Post: <mailto:desktop-devel-list@gnome.org> +List-Help: <mailto:desktop-devel-list-request@gnome.org?subject=help> +List-Subscribe: <https://mail.gnome.org/mailman/listinfo/desktop-devel-list>, + <mailto:desktop-devel-list-request@gnome.org?subject=subscribe> +Content-Type: text/plain; charset="us-ascii" +Content-Transfer-Encoding: 7bit +Errors-To: desktop-devel-list-bounces@gnome.org +Sender: desktop-devel-list-bounces@gnome.org + +As per earlier discussions, I am proposing that we target GNOME 3.8 as +our first all Python 3 release. + +Frederic Peters already did the list of modules impacted: +http://people.gnome.org/~fpeters/reports/python3.html + +Are there any reasons why we should not do this? + +Take care. +--joanie +_______________________________________________ +desktop-devel-list mailing list +desktop-devel-list@gnome.org +https://mail.gnome.org/mailman/listinfo/desktop-devel-list +]
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20120628/1340ac53/attachment.mht b/zarb-ml/mageia-dev/attachments/20120628/1340ac53/attachment.mht new file mode 100644 index 000000000..eb1cd27a3 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/1340ac53/attachment.mht @@ -0,0 +1,81 @@ +[From nobody Thu Jun 28 09:29:54 2012 +Return-Path: <desktop-devel-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 0AD645002AC + for <list-gnome@vitters.nl>; Mon, 25 Jun 2012 15:45:27 +0200 (CEST) +Received: from menubar.gnome.org (localhost.localdomain [127.0.0.1]) + by menubar.gnome.org (Postfix) with ESMTP id C75FA75043A; + Mon, 25 Jun 2012 13:45:25 +0000 (UTC) +X-Original-To: desktop-devel-list@gnome.org +Delivered-To: desktop-devel-list@gnome.org +Received: from localhost (localhost.localdomain [127.0.0.1]) + by menubar.gnome.org (Postfix) with ESMTP id 5809E750120 + for <desktop-devel-list@gnome.org>; + Mon, 25 Jun 2012 13:45:19 +0000 (UTC) +X-Virus-Scanned: by amavisd-new at gnome.org +X-Spam-Flag: NO +X-Spam-Score: -2.601 +X-Spam-Level: +X-Spam-Status: No, score=-2.601 tagged_above=-999 required=2 + tests=[BAYES_00=-1.9, 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 XVsfYTlh1sTb for <desktop-devel-list@gnome.org>; + Mon, 25 Jun 2012 13:45:15 +0000 (UTC) +Received: from smtp4.mundo-r.com (smtp3.mundo-r.com [212.51.32.191]) + by menubar.gnome.org (Postfix) with ESMTP id 962AA750103 + for <desktop-devel-list@gnome.org>; + Mon, 25 Jun 2012 13:45:05 +0000 (UTC) +X-IronPort-Anti-Spam-Filtered: true +X-IronPort-Anti-Spam-Result: AlkGAE5q6E9bdWOb/2dsb2JhbABEFoMrghmwRoEHgkKBCwIFIQIRAkwNCAEBiAcEB5dYjkGSL4EgjwOBEgOVLoESjm+Cew +X-IronPort-AV: E=Sophos;i="4.77,472,1336341600"; d="scan'208";a="923946298" +Received: from fanzine.igalia.com ([91.117.99.155]) + by smtp4.mundo-r.com with ESMTP; 25 Jun 2012 15:45:03 +0200 +Received: from c-98-217-239-60.hsd1.nh.comcast.net ([98.217.239.60] + helo=[192.168.35.105]) by fanzine.igalia.com with esmtpsa + (Cipher TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim) + id 1Sj9bD-0003F4-FA + for <desktop-devel-list@gnome.org>; Mon, 25 Jun 2012 15:45:03 +0200 +Message-ID: <4FE86B54.70306@igalia.com> +Date: Mon, 25 Jun 2012 09:44:52 -0400 +From: Joanmarie Diggs <jdiggs@igalia.com> +User-Agent: Mozilla/5.0 (X11; Linux x86_64; + rv:13.0) Gecko/20120615 Thunderbird/13.0.1 +MIME-Version: 1.0 +To: desktop-devel-list <desktop-devel-list@gnome.org> +Subject: [PROPOSAL] GNOME Goal for 3.8: No more Python 2 +X-Enigmail-Version: 1.4.2 +X-BeenThere: desktop-devel-list@gnome.org +X-Mailman-Version: 2.1.14 +Precedence: list +List-Id: GNOME Desktop Development List <desktop-devel-list.gnome.org> +List-Unsubscribe: <https://mail.gnome.org/mailman/options/desktop-devel-list>, + <mailto:desktop-devel-list-request@gnome.org?subject=unsubscribe> +List-Archive: <https://mail.gnome.org/archives/desktop-devel-list/> +List-Post: <mailto:desktop-devel-list@gnome.org> +List-Help: <mailto:desktop-devel-list-request@gnome.org?subject=help> +List-Subscribe: <https://mail.gnome.org/mailman/listinfo/desktop-devel-list>, + <mailto:desktop-devel-list-request@gnome.org?subject=subscribe> +Content-Type: text/plain; charset="us-ascii" +Content-Transfer-Encoding: 7bit +Errors-To: desktop-devel-list-bounces@gnome.org +Sender: desktop-devel-list-bounces@gnome.org + +As per earlier discussions, I am proposing that we target GNOME 3.8 as +our first all Python 3 release. + +Frederic Peters already did the list of modules impacted: +http://people.gnome.org/~fpeters/reports/python3.html + +Are there any reasons why we should not do this? + +Take care. +--joanie +_______________________________________________ +desktop-devel-list mailing list +desktop-devel-list@gnome.org +https://mail.gnome.org/mailman/listinfo/desktop-devel-list +]
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20120628/42c04d86/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20120628/42c04d86/attachment-0001.html new file mode 100644 index 000000000..5a06b02b2 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/42c04d86/attachment-0001.html @@ -0,0 +1,175 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"> +<html><head><meta name="qrichtext" content="1" /><style type="text/css"> +p, li { white-space: pre-wrap; } +</style></head><body style=" font-family:'Bitstream Vera Sans Mono'; font-size:9pt; font-weight:400; font-style:normal;"> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">On Tuesday, 26 June 2012 22:25:10 Thomas Backlund wrote:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> So,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> we have been discussing this many times, and not gotten any</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> satisfactory decision to go ahead yet...</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Sorry for the late reply, but as some of you are aware, I have had some problems replying to Mageia-related mails (which are finally resolved).</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> First off, we decided long ago that backports will be</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> better supported than during mdv times,</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">This may be an unfair generalisation.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> meaning security</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> and bugfixes and has to pass QA.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">In some cases, this is a basic feature of backports. For example, the primary targets of my backports typically ship new releases for any security fix, and bugfixes are typically released in new releases (and only in severe cases do we cherry-pick the bugfix from a new release for a bugfix update).</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">In the case of samba, openldap etc., my primary motivation for wanting backports is so that we can provide early bugfixes (which in most cases have been well tested by the rest of the upstream community) with less delay than cherry-picking bugfixes, QA, etc.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">The other motivation for me, is to make newly packaged software in cauldron available to stable releases. The probability of a security update being required is usually quite low in this case.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Now for references:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * we have the backports policy:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> https://wiki.mageia.org/en/Backports_policy</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I think we are over-engineering everything here.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">See for example:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">https://www.google.com/search?q=%22main/backports%20openldap-2.4%22%20site:lists.mandriva.com</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">For openldap, since upstream doesn't really look at bugs on old releases, I backported every new release to every version that had a build system available.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">In all that time, there was only ever one bug reported on the backports, due to a NMU backport.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * Last discussions started by Stormi:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * [Mageia-dev] Backports policy clarification (and discussion)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> https://www.mageia.org/pipermail/mageia-dev/2012-June/016265.html</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * [Mageia-dev] Proposed Feature:Backports_update_applet</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> https://www.mageia.org/pipermail/mageia-dev/2012-June/016263.html</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * It also came up in the discussion about fixing bug 2317:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * [Mageia-dev] bug 2317 revisited: --update option should behave like</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> --search-media</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> https://www.mageia.org/pipermail/mageia-dev/2012-June/016692.html</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> People seem to agree on most things, but there is a few questions</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> that need to be decided how to handle.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Lets start with the summary and suggestion of how to get it started:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> (addendum / refinements / important points of current backports policy)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * backports is supported as long as the rest of the release</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">But this is not a committment to always backport every already-backported package.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * packages must always be in cauldron first</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Of course.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * if you want to backport a package someone else is maintainer</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> for, you need to discuss with maintainer first. if he dont</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> want the package to be backported _and_ have valid reasons,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> respect that. (if you disagree, you can still ask council)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * if you backport anything, (regardless if you are the real</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> maintainer or not) you accept the responsibility of</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> handling the bugreports against the backport and make sure</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> it gets patched (or upgraded) to get security fixes.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * cherrypicking backports must work, so requires need</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> to be checked and be strict to make sure they work</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Agreed, but it is not critical to QA every possible combination of packages. Users are able to resolve these problems themselves, and report the problem.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * nothing in backports must require the use of "--nodeps"</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> or "--force" to get it to install</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * QA will do basic tests to make sure it works and obeys the rules</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * QA can deny package(s) to be backported if it breaks the policy</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * QA has /updates as priority, and /backports will be handled</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> if/when there is time, so if you want faster response, join QA</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> to help out with the workload.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Hmm, in many cases, I actually test backports on the stable release myself before submitting them ... I am concerned QA will become a bottle-neck that doesn't necessarily always add much value.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Now a point that got raised during discussion of bug 2317:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * if a backport break because of something ending up in /updates</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> it's a bug to be reported against the backport (and not against</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> the released update) as packages ending up in /updates are only</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> validated against /release and /updates (and rightfully so as</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> thats how they are built too)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> And some important points to avoid making backports_testing a</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> "dumping ground" for package(r)s trying to avoid the policy:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * after submitting anything to backports_testing you have</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> 48 hours to file/assign a "Backport to validate" at</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> bugs.mageia.org.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * package needs to be validated within 1 month (or shorter/longer</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> time if QA wants that)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * failure to match any of the two timelimits will get the</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> package removed from updates_testing again. (I understand this</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> will get some questions, but if we cant get people to help out</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> with QA we might as well never open backports)</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I would prefer if we could crowd-source and automate this, otherwise, again, this will be the bottle-neck.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> And then the questions we need to decide on:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> (substitute mga1/mga2 for any future release...)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> 1. Do we support backporting package with higher version</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> than package in the following next mageia release has ?</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> (meaning if mga1 has v12, and mga2 has v14, is it ok</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> to backport v16 to mga1?)</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">As long as it was backported to mga2 first.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * PRO: more uptodate package in backports</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * CON: can cause trouble during distro upgrade</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * imho both technically ok as long as we make sure</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> its documented so people know what to expect.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">E.g., if upgrading from mga1 to mga2 and having used backports after mga2 release, the users should enable backports in mga2 during upgrade, or post-upgrade.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> 2. If one want to backport a package to mga1, does it mean</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> it must be backported to mga2 in order to preserve</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> upgrade path (unless already in mga2, depending on</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> question 1)?</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Yes.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> And since we can continue this what/if discussion forever,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> and thereby delay backports even more here is my take on it:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> my suggestions to decide on question 1 and 2:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> 1. backporting bigger version to mga1 than mga2 has is</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> allowed as it will otherwise restrict backporting</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> too much. (and since its leaf packages, it should</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> not break (too much)). Lets just make it clear to</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> everyone using backports.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">What about an update to a backport for a security issue?</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> 2. we cant really require that as the one backporting</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> the package to mga1 has to backport it to mga2 too</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> as he/she might not be using mga2 at all. if someone</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> wants/needs the backport for mga2, they need to</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> request that. (in reality, going by how backports</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> got handled in mdv most backports will end up in</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> all supported releases anyway)</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Typically, if it backports easily to mga1, it will backport more easily to mga2.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> If we can agree on this as a start, we can open backports</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> soon so we get actual facts of how backports policy and</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> process works.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Then we rewiew backports policy and process in ~6 months,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> and adjust it if needed.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Comments? Questions ?</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I think we may want to review this policy one month after we open backports, as I think some pieces in the process/policy may not scale as well as the others.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Regards,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Buchan</p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20120628/42c04d86/attachment.html b/zarb-ml/mageia-dev/attachments/20120628/42c04d86/attachment.html new file mode 100644 index 000000000..5a06b02b2 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/42c04d86/attachment.html @@ -0,0 +1,175 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"> +<html><head><meta name="qrichtext" content="1" /><style type="text/css"> +p, li { white-space: pre-wrap; } +</style></head><body style=" font-family:'Bitstream Vera Sans Mono'; font-size:9pt; font-weight:400; font-style:normal;"> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">On Tuesday, 26 June 2012 22:25:10 Thomas Backlund wrote:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> So,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> we have been discussing this many times, and not gotten any</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> satisfactory decision to go ahead yet...</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Sorry for the late reply, but as some of you are aware, I have had some problems replying to Mageia-related mails (which are finally resolved).</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> First off, we decided long ago that backports will be</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> better supported than during mdv times,</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">This may be an unfair generalisation.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> meaning security</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> and bugfixes and has to pass QA.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">In some cases, this is a basic feature of backports. For example, the primary targets of my backports typically ship new releases for any security fix, and bugfixes are typically released in new releases (and only in severe cases do we cherry-pick the bugfix from a new release for a bugfix update).</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">In the case of samba, openldap etc., my primary motivation for wanting backports is so that we can provide early bugfixes (which in most cases have been well tested by the rest of the upstream community) with less delay than cherry-picking bugfixes, QA, etc.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">The other motivation for me, is to make newly packaged software in cauldron available to stable releases. The probability of a security update being required is usually quite low in this case.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Now for references:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * we have the backports policy:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> https://wiki.mageia.org/en/Backports_policy</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I think we are over-engineering everything here.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">See for example:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">https://www.google.com/search?q=%22main/backports%20openldap-2.4%22%20site:lists.mandriva.com</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">For openldap, since upstream doesn't really look at bugs on old releases, I backported every new release to every version that had a build system available.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">In all that time, there was only ever one bug reported on the backports, due to a NMU backport.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * Last discussions started by Stormi:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * [Mageia-dev] Backports policy clarification (and discussion)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> https://www.mageia.org/pipermail/mageia-dev/2012-June/016265.html</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * [Mageia-dev] Proposed Feature:Backports_update_applet</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> https://www.mageia.org/pipermail/mageia-dev/2012-June/016263.html</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * It also came up in the discussion about fixing bug 2317:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * [Mageia-dev] bug 2317 revisited: --update option should behave like</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> --search-media</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> https://www.mageia.org/pipermail/mageia-dev/2012-June/016692.html</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> People seem to agree on most things, but there is a few questions</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> that need to be decided how to handle.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Lets start with the summary and suggestion of how to get it started:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> (addendum / refinements / important points of current backports policy)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * backports is supported as long as the rest of the release</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">But this is not a committment to always backport every already-backported package.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * packages must always be in cauldron first</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Of course.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * if you want to backport a package someone else is maintainer</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> for, you need to discuss with maintainer first. if he dont</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> want the package to be backported _and_ have valid reasons,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> respect that. (if you disagree, you can still ask council)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * if you backport anything, (regardless if you are the real</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> maintainer or not) you accept the responsibility of</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> handling the bugreports against the backport and make sure</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> it gets patched (or upgraded) to get security fixes.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * cherrypicking backports must work, so requires need</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> to be checked and be strict to make sure they work</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Agreed, but it is not critical to QA every possible combination of packages. Users are able to resolve these problems themselves, and report the problem.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * nothing in backports must require the use of "--nodeps"</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> or "--force" to get it to install</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * QA will do basic tests to make sure it works and obeys the rules</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * QA can deny package(s) to be backported if it breaks the policy</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * QA has /updates as priority, and /backports will be handled</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> if/when there is time, so if you want faster response, join QA</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> to help out with the workload.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Hmm, in many cases, I actually test backports on the stable release myself before submitting them ... I am concerned QA will become a bottle-neck that doesn't necessarily always add much value.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Now a point that got raised during discussion of bug 2317:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * if a backport break because of something ending up in /updates</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> it's a bug to be reported against the backport (and not against</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> the released update) as packages ending up in /updates are only</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> validated against /release and /updates (and rightfully so as</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> thats how they are built too)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> And some important points to avoid making backports_testing a</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> "dumping ground" for package(r)s trying to avoid the policy:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * after submitting anything to backports_testing you have</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> 48 hours to file/assign a "Backport to validate" at</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> bugs.mageia.org.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * package needs to be validated within 1 month (or shorter/longer</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> time if QA wants that)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * failure to match any of the two timelimits will get the</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> package removed from updates_testing again. (I understand this</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> will get some questions, but if we cant get people to help out</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> with QA we might as well never open backports)</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I would prefer if we could crowd-source and automate this, otherwise, again, this will be the bottle-neck.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> And then the questions we need to decide on:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> (substitute mga1/mga2 for any future release...)</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> 1. Do we support backporting package with higher version</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> than package in the following next mageia release has ?</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> (meaning if mga1 has v12, and mga2 has v14, is it ok</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> to backport v16 to mga1?)</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">As long as it was backported to mga2 first.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * PRO: more uptodate package in backports</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * CON: can cause trouble during distro upgrade</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> * imho both technically ok as long as we make sure</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> its documented so people know what to expect.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">E.g., if upgrading from mga1 to mga2 and having used backports after mga2 release, the users should enable backports in mga2 during upgrade, or post-upgrade.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> 2. If one want to backport a package to mga1, does it mean</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> it must be backported to mga2 in order to preserve</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> upgrade path (unless already in mga2, depending on</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> question 1)?</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Yes.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> And since we can continue this what/if discussion forever,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> and thereby delay backports even more here is my take on it:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> my suggestions to decide on question 1 and 2:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> 1. backporting bigger version to mga1 than mga2 has is</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> allowed as it will otherwise restrict backporting</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> too much. (and since its leaf packages, it should</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> not break (too much)). Lets just make it clear to</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> everyone using backports.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">What about an update to a backport for a security issue?</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> 2. we cant really require that as the one backporting</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> the package to mga1 has to backport it to mga2 too</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> as he/she might not be using mga2 at all. if someone</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> wants/needs the backport for mga2, they need to</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> request that. (in reality, going by how backports</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> got handled in mdv most backports will end up in</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> all supported releases anyway)</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Typically, if it backports easily to mga1, it will backport more easily to mga2.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> If we can agree on this as a start, we can open backports</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> soon so we get actual facts of how backports policy and</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> process works.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Then we rewiew backports policy and process in ~6 months,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> and adjust it if needed.</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Comments? Questions ?</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I think we may want to review this policy one month after we open backports, as I think some pieces in the process/policy may not scale as well as the others.</p> +<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; "> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Regards,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Buchan</p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20120628/585bda3b/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20120628/585bda3b/attachment-0001.html new file mode 100644 index 000000000..ea787fce0 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/585bda3b/attachment-0001.html @@ -0,0 +1,21 @@ +<p><br> +Le 28 juin 2012 12:24, "Marja van Waes" <<a href="mailto:marja11@xs4all.nl">marja11@xs4all.nl</a>> a écrit :<br> +><br> +> On 28/06/2012 12:05, Dimitrios Glentadakis wrote:<br> +><br> +>><br> +>><br> +>> I filled a bug in KDe bug tracker<br> +>> <a href="https://bugs.kde.org/show_bug.cgi?id=302689">https://bugs.kde.org/show_bug.cgi?id=302689</a><br> +>><br> +>> --<br> +><br> +><br> +> With wich applications do you still use aspell?<br> +><br> +> After I removed all those links in /usr/share/hunspell/ the list of dictionaries in Kwrite is just as short as in Thunderbird or in Firefox.<br> +><br> +> Cheers,<br> +> marja<br> +></p> +<p>I did nt search about hunspell i looked only about aspell til now. I will look about hunspell and its dictionnaries</p> diff --git a/zarb-ml/mageia-dev/attachments/20120628/585bda3b/attachment.html b/zarb-ml/mageia-dev/attachments/20120628/585bda3b/attachment.html new file mode 100644 index 000000000..ea787fce0 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/585bda3b/attachment.html @@ -0,0 +1,21 @@ +<p><br> +Le 28 juin 2012 12:24, "Marja van Waes" <<a href="mailto:marja11@xs4all.nl">marja11@xs4all.nl</a>> a écrit :<br> +><br> +> On 28/06/2012 12:05, Dimitrios Glentadakis wrote:<br> +><br> +>><br> +>><br> +>> I filled a bug in KDe bug tracker<br> +>> <a href="https://bugs.kde.org/show_bug.cgi?id=302689">https://bugs.kde.org/show_bug.cgi?id=302689</a><br> +>><br> +>> --<br> +><br> +><br> +> With wich applications do you still use aspell?<br> +><br> +> After I removed all those links in /usr/share/hunspell/ the list of dictionaries in Kwrite is just as short as in Thunderbird or in Firefox.<br> +><br> +> Cheers,<br> +> marja<br> +></p> +<p>I did nt search about hunspell i looked only about aspell til now. I will look about hunspell and its dictionnaries</p> diff --git a/zarb-ml/mageia-dev/attachments/20120628/9d9a4196/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20120628/9d9a4196/attachment-0001.html new file mode 100644 index 000000000..43f4b2d10 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/9d9a4196/attachment-0001.html @@ -0,0 +1,28 @@ +<span style='font-family:Verdana'><span style='font-size:12px'><br /> +<br /> +<p style="margin:0px; padding:0px;" > + </p> +<blockquote style="border-left: 1px solid #CCC; padding-left: 5px; margin-left: 5px; margin-bottom: 0px; margin-top: 0px; margin-right: 0px;" type="cite"> + <p style="margin:0px; padding:0px;" > + <span style="font-family:Verdana"><span style="font-size:12px">----- Original Message -----</span></span></p> + <p style="margin:0px; padding:0px;" > + <span style="font-family:Verdana"><span style="font-size:12px">From: Guillaume Rousse</span></span></p> + <p style="margin:0px; padding:0px;" > + <span style="font-family:Verdana"><span style="font-size:12px">Sent: 06/28/12 10:34 AM</span></span></p> + <p style="margin:0px; padding:0px;" > + <span style="font-family:Verdana"><span style="font-size:12px">To: Mageia development mailing-list</span></span></p> + <p style="margin:0px; padding:0px;" > + <span style="font-family:Verdana"><span style="font-size:12px">Subject: Re: [Mageia-dev] Idea to fix "Way too many languages to choose from for spell checking in FF and TB" mga#6125</span></span></p> + <div> + <pre style="white-space: pre-wrap; word-wrap: break-word; font-size:11;pre"> + +Directly removing file on the system installed by rpm will break rpm +assumption than its DB content should match actual filesystem. + + +</pre> + </div> +</blockquote> +<span id="editor_signature"><span style="font-family:Verdana; font-size:12px"> Ah, I was affraid of this. So we cannot break the filesystem.<br /> +<br /> +There is also an additional solution: stop following Fedora and so stop installing symlinks (like "en_US" -> "en_X1", "en_X2", "en_X3" etc). This solution can reduce language variants for most (IIRC all) of languages to 1,2 or 3 dictionaries.</span></span></span></span> diff --git a/zarb-ml/mageia-dev/attachments/20120628/9d9a4196/attachment.html b/zarb-ml/mageia-dev/attachments/20120628/9d9a4196/attachment.html new file mode 100644 index 000000000..43f4b2d10 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/9d9a4196/attachment.html @@ -0,0 +1,28 @@ +<span style='font-family:Verdana'><span style='font-size:12px'><br /> +<br /> +<p style="margin:0px; padding:0px;" > + </p> +<blockquote style="border-left: 1px solid #CCC; padding-left: 5px; margin-left: 5px; margin-bottom: 0px; margin-top: 0px; margin-right: 0px;" type="cite"> + <p style="margin:0px; padding:0px;" > + <span style="font-family:Verdana"><span style="font-size:12px">----- Original Message -----</span></span></p> + <p style="margin:0px; padding:0px;" > + <span style="font-family:Verdana"><span style="font-size:12px">From: Guillaume Rousse</span></span></p> + <p style="margin:0px; padding:0px;" > + <span style="font-family:Verdana"><span style="font-size:12px">Sent: 06/28/12 10:34 AM</span></span></p> + <p style="margin:0px; padding:0px;" > + <span style="font-family:Verdana"><span style="font-size:12px">To: Mageia development mailing-list</span></span></p> + <p style="margin:0px; padding:0px;" > + <span style="font-family:Verdana"><span style="font-size:12px">Subject: Re: [Mageia-dev] Idea to fix "Way too many languages to choose from for spell checking in FF and TB" mga#6125</span></span></p> + <div> + <pre style="white-space: pre-wrap; word-wrap: break-word; font-size:11;pre"> + +Directly removing file on the system installed by rpm will break rpm +assumption than its DB content should match actual filesystem. + + +</pre> + </div> +</blockquote> +<span id="editor_signature"><span style="font-family:Verdana; font-size:12px"> Ah, I was affraid of this. So we cannot break the filesystem.<br /> +<br /> +There is also an additional solution: stop following Fedora and so stop installing symlinks (like "en_US" -> "en_X1", "en_X2", "en_X3" etc). This solution can reduce language variants for most (IIRC all) of languages to 1,2 or 3 dictionaries.</span></span></span></span> diff --git a/zarb-ml/mageia-dev/attachments/20120628/ab7eeca3/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20120628/ab7eeca3/attachment-0001.asc new file mode 100644 index 000000000..efee9e5d4 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/ab7eeca3/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBP67dZT1rWTfpocyQRAvEaAJ94mNUCNmrfK+4MKIp5tYDUSfo1RwCdEU0t +Eghx9JEVQd/oGbkaxyooUls= +=AcFv +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20120628/ab7eeca3/attachment.asc b/zarb-ml/mageia-dev/attachments/20120628/ab7eeca3/attachment.asc new file mode 100644 index 000000000..efee9e5d4 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120628/ab7eeca3/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBP67dZT1rWTfpocyQRAvEaAJ94mNUCNmrfK+4MKIp5tYDUSfo1RwCdEU0t +Eghx9JEVQd/oGbkaxyooUls= +=AcFv +-----END PGP SIGNATURE----- |