diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/attachments/20120325/7c7da6a8 | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20120325/7c7da6a8')
| -rw-r--r-- | zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment-0001.html | 24 | ||||
| -rw-r--r-- | zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment.html | 24 |
2 files changed, 48 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment-0001.html new file mode 100644 index 000000000..7ac07f371 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment-0001.html @@ -0,0 +1,24 @@ +<br><br><div class="gmail_quote">On Sun, Mar 25, 2012 at 18:11, Thierry Vignaud <span dir="ltr"><<a href="mailto:thierry.vignaud@gmail.com">thierry.vignaud@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> + +<div class="im">On 25 March 2012 18:15, Pascal Terjan <<a href="mailto:pterjan@gmail.com">pterjan@gmail.com</a>> wrote:<br> +>> Now, in order to provide a very good Mageia 2, every package should<br> +>> be rebuilt with the new toolchain/glibc in order to make sure they<br> +>> still build _and_ work correctly (and flush out any bugs in the<br> +>> toolchain)<br> +>><br> +>> Now this rebuild should be done preferably in BR order when possible,<br> +>> to rule out bad interaction between packages and be preferably be<br> +>> fully done by alpha3 or beta1 at the latest so we have time to fix<br> +>> it properly for Mageia 2.<br> +<br> +</div>(...)<br> +<div class="im"><br> +> Rebuilding half of the distribution now seems the best way to add bugs<br> +> before the release...<br> +<br> +</div>On the other hand, we my got bugs introduced when pushing a security<br> +update due to the new toolchain not having been tested with those<br> +packages...<br> +Or having packages not rebuilding when patching them for security<br> +fixes.<br> +</blockquote></div><br><div>Yes but I think it's something that should have been done after toolchain was updated in december, or at latest around beta1/version freeze, not 2 weeks before the release candidate</div> diff --git a/zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment.html b/zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment.html new file mode 100644 index 000000000..7ac07f371 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment.html @@ -0,0 +1,24 @@ +<br><br><div class="gmail_quote">On Sun, Mar 25, 2012 at 18:11, Thierry Vignaud <span dir="ltr"><<a href="mailto:thierry.vignaud@gmail.com">thierry.vignaud@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> + +<div class="im">On 25 March 2012 18:15, Pascal Terjan <<a href="mailto:pterjan@gmail.com">pterjan@gmail.com</a>> wrote:<br> +>> Now, in order to provide a very good Mageia 2, every package should<br> +>> be rebuilt with the new toolchain/glibc in order to make sure they<br> +>> still build _and_ work correctly (and flush out any bugs in the<br> +>> toolchain)<br> +>><br> +>> Now this rebuild should be done preferably in BR order when possible,<br> +>> to rule out bad interaction between packages and be preferably be<br> +>> fully done by alpha3 or beta1 at the latest so we have time to fix<br> +>> it properly for Mageia 2.<br> +<br> +</div>(...)<br> +<div class="im"><br> +> Rebuilding half of the distribution now seems the best way to add bugs<br> +> before the release...<br> +<br> +</div>On the other hand, we my got bugs introduced when pushing a security<br> +update due to the new toolchain not having been tested with those<br> +packages...<br> +Or having packages not rebuilding when patching them for security<br> +fixes.<br> +</blockquote></div><br><div>Yes but I think it's something that should have been done after toolchain was updated in december, or at latest around beta1/version freeze, not 2 weeks before the release candidate</div> |