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/20110611 | |
| 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/20110611')
10 files changed, 754 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20110611/286e7c35/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110611/286e7c35/attachment-0001.html new file mode 100644 index 000000000..383343a3c --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110611/286e7c35/attachment-0001.html @@ -0,0 +1,11 @@ +<br><br><div class="gmail_quote">2011/6/11 Dick Gevers <span dir="ltr"><<a href="mailto:dvgevers@xs4all.nl">dvgevers@xs4all.nl</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +Not that I understand half of what is posted, but for reference and<br> +satisfying my curiosity, I'd like to subscribe to the submit ML, but can't<br> +find it at <a href="https://mageia.org/mailman/" target="_blank">https://mageia.org/mailman/</a><br> +<br> +Obviously I can send a subscribe mail, but I dunno the details.<br></blockquote><div><br></div><div><br></div><div>have a look on <a href="https://ml.mageia.org/">https://ml.mageia.org/</a>. Some of the ML are still hosted on Zarb server and others have been created on Mageia servers. This is on sysadmin todo list</div> +<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +<br> +TIA!<br> +<font color="#888888">=Dick Gevers=<br> +</font></blockquote></div><br><br clear="all"><br>-- <br>Anne<br><a href="http://www.mageia.org" target="_blank">http://www.mageia.org</a><br> diff --git a/zarb-ml/mageia-dev/attachments/20110611/286e7c35/attachment.html b/zarb-ml/mageia-dev/attachments/20110611/286e7c35/attachment.html new file mode 100644 index 000000000..383343a3c --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110611/286e7c35/attachment.html @@ -0,0 +1,11 @@ +<br><br><div class="gmail_quote">2011/6/11 Dick Gevers <span dir="ltr"><<a href="mailto:dvgevers@xs4all.nl">dvgevers@xs4all.nl</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +Not that I understand half of what is posted, but for reference and<br> +satisfying my curiosity, I'd like to subscribe to the submit ML, but can't<br> +find it at <a href="https://mageia.org/mailman/" target="_blank">https://mageia.org/mailman/</a><br> +<br> +Obviously I can send a subscribe mail, but I dunno the details.<br></blockquote><div><br></div><div><br></div><div>have a look on <a href="https://ml.mageia.org/">https://ml.mageia.org/</a>. Some of the ML are still hosted on Zarb server and others have been created on Mageia servers. This is on sysadmin todo list</div> +<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> +<br> +TIA!<br> +<font color="#888888">=Dick Gevers=<br> +</font></blockquote></div><br><br clear="all"><br>-- <br>Anne<br><a href="http://www.mageia.org" target="_blank">http://www.mageia.org</a><br> diff --git a/zarb-ml/mageia-dev/attachments/20110611/87fe5693/attachment-0001.ksh b/zarb-ml/mageia-dev/attachments/20110611/87fe5693/attachment-0001.ksh new file mode 100644 index 000000000..fbf13ab1b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110611/87fe5693/attachment-0001.ksh @@ -0,0 +1,171 @@ +%define name get-skype +%define version 2.2.0.35 +%define release %mkrel 6 +%define instdir %{_datadir}/skype +%define langdir %{instdir}/lang +%define avatardir %{instdir}/avatars +%define sounddir %{instdir}/sounds +%define icondir %{instdir}/icons +%define md5 6e28002c0086fae5206e2d242c3edcfa +%define mytmp %{_localstatedir}/lib/%{name} + +Summary: Download and Install Skype. +Name: %{name} +Version: %{version} +Release: %{release} +License: Proprietary +Group: Networking/Instant messaging +URL: http://www.skype.com +Buildarch: noarch +Requires: wget +Requires: liblcms1 +Requires: libmng1 +Requires: libqtcore4 +Requires: libqtdbus4 +Requires: libqtnetwork4 +Requires: libqtgui4 +Requires: libqtsvg4 +Requires: libqtxml4 +Requires: libxscrnsaver1 +Requires: libxv1 +Requires: libv4l-wrappers + +# The following are lists of filenames (124 in total) placed +# in text files to save clutter in the spec. +Source0: avatars-2.2.0.35.txt +Source1: sounds-2.2.0.35.txt +Source2: lang-2.2.0.35.txt + +%description + +This is an installer for Skype-%{version}. + +This package does not contain any files as the Skype license does not allow distribution. +By installing this package you will download and install Skype from skype.com. +You must accept the Skype EULA before using it. +Please be patient - this is a 23MB download and may take some time. +Uninstalling this package will uninstall Skype from your system. + +%pre + +mkdir %{mytmp} +cd %{mytmp} +wget -nc "http://download.skype.com/linux/skype-%{version}.tar.bz2" + +md5chk=$(md5sum skype-%{version}.tar.bz2 | cut -d' ' -f1) +if [[ %{md5} != $md5chk ]]; then +rm skype-%{version}.tar.bz2 +cd .. +rm -r %{mytmp} +echo "Error - download failed" +exit 1 +fi + +%install + +rm -rf $RPM_BUILD_ROOT +install -d -m 0755 %buildroot%{_bindir} +install -d -m 0755 %buildroot%{_datadir}/applications +touch %buildroot%{_datadir}/applications/skype.desktop + +install -d -m 0755 %buildroot%{instdir} +touch %buildroot%{instdir}/{skype.desktop,skype,skype.conf,LICENSE,README} + +install -d -m 0755 %buildroot%{langdir} +while read line; do +touch %buildroot%{langdir}/skype_"$line" +done < %{SOURCE2} + +install -d -m 0755 %buildroot%{instdir}/icons +install -d -m 0755 %buildroot%{_iconsdir} +touch %buildroot%{_iconsdir}/skype.png +for i in 16 32 48; do +touch %buildroot%{_iconsdir}/SkypeBlue_${i}x${i}.png +touch %buildroot%{instdir}/icons/SkypeBlue_${i}x${i}.png +done + +install -d -m 0755 %buildroot%{avatardir} +while read line; do +touch %buildroot%{avatardir}/"$line" +done < %{SOURCE0} + +install -d -m 0755 %buildroot%{sounddir} +while read line; do +touch %buildroot%{sounddir}/"$line" +done < %{SOURCE1} + +echo "LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so %{instdir}/skype --resources=%{instdir}"\ + > %buildroot%{_bindir}/skype && chmod +x %buildroot%{_bindir}/skype + +%post + +newtmp=$(mktemp -d) +%define tmpextdir $newtmp +cd %{tmpextdir} +tar jxf %{mytmp}/skype-%{version}.tar.bz2 + +%define tmpdir %{tmpextdir}/skype-%{version} +mkdir %{instdir} + +cp -a %{tmpdir}/icons/* %{_iconsdir} +cp -a %{_iconsdir}/SkypeBlue_48x48.png %{_iconsdir}/skype.png +cp -a %{tmpdir}/skype.desktop %{_datadir}/applications/ +mv %{tmpdir}/skype %{instdir} +mv %{tmpdir}/skype.desktop %{instdir} +mv %{tmpdir}/skype.conf %{instdir} +mv %{tmpdir}/LICENSE %{instdir} +mv %{tmpdir}/README %{instdir} +mv %{tmpdir}/avatars %{instdir} +mv %{tmpdir}/lang %{langdir} +mv %{tmpdir}/sounds %{sounddir} +mv %{tmpdir}/icons %{icondir} +rm -r %{tmpdir} +cd .. +rm -r %{tmpextdir} +rm -r %{mytmp} + +%clean + +rm -rf $RPM_BUILD_ROOT + +%files + +%defattr(-,root,root) +%{_bindir}/skype +%ghost %{_iconsdir}/skype.png +%ghost %{_iconsdir}/SkypeBlue_*.png +%ghost %{_datadir}/applications/skype.desktop +%ghost %{instdir} + +%changelog + +* Sat Jun 11 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-6.mga1 +- Added md5sum check on download and cleanup on fail. +- Downloads to /var/lib/get-skype - removed after install. +- Creates unique /tmp/tmp.xxxx dir for extraction of tar. +- Added versioning to .txt files. +- Added removal of all tmp directories after install. +- Corrected URL: + +* Thu Jun 9 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-5.mga1 +- Bumped release to test update - no changes + +* Thu Jun 9 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-4.mga1 +- Moved installation to /usr/share instead of /opt +- Changed group and license +- Changed temporary dir +- Changed to wget for d/l + +* Mon Jun 6 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-2.mga1 +- Moved download to %pre to stop install if d/l fails + +* Sun Jun 5 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-1.mga1 +- Changed get-skype version to follow Skype version. +- Changed URL to directly download only correct version. +- A copy of the downloaded file is retained in /tmp/skype-%{version} to +- speed re-installation (unless you clean /tmp) + +* Sat Jun 4 2011 Barry Jackson <zen25000@zen.co.uk> 0.2.mga1 +- Now all files are registered in rpm database. +- lang, avatar and sound filenames supplied in source files. + diff --git a/zarb-ml/mageia-dev/attachments/20110611/87fe5693/attachment.ksh b/zarb-ml/mageia-dev/attachments/20110611/87fe5693/attachment.ksh new file mode 100644 index 000000000..fbf13ab1b --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110611/87fe5693/attachment.ksh @@ -0,0 +1,171 @@ +%define name get-skype +%define version 2.2.0.35 +%define release %mkrel 6 +%define instdir %{_datadir}/skype +%define langdir %{instdir}/lang +%define avatardir %{instdir}/avatars +%define sounddir %{instdir}/sounds +%define icondir %{instdir}/icons +%define md5 6e28002c0086fae5206e2d242c3edcfa +%define mytmp %{_localstatedir}/lib/%{name} + +Summary: Download and Install Skype. +Name: %{name} +Version: %{version} +Release: %{release} +License: Proprietary +Group: Networking/Instant messaging +URL: http://www.skype.com +Buildarch: noarch +Requires: wget +Requires: liblcms1 +Requires: libmng1 +Requires: libqtcore4 +Requires: libqtdbus4 +Requires: libqtnetwork4 +Requires: libqtgui4 +Requires: libqtsvg4 +Requires: libqtxml4 +Requires: libxscrnsaver1 +Requires: libxv1 +Requires: libv4l-wrappers + +# The following are lists of filenames (124 in total) placed +# in text files to save clutter in the spec. +Source0: avatars-2.2.0.35.txt +Source1: sounds-2.2.0.35.txt +Source2: lang-2.2.0.35.txt + +%description + +This is an installer for Skype-%{version}. + +This package does not contain any files as the Skype license does not allow distribution. +By installing this package you will download and install Skype from skype.com. +You must accept the Skype EULA before using it. +Please be patient - this is a 23MB download and may take some time. +Uninstalling this package will uninstall Skype from your system. + +%pre + +mkdir %{mytmp} +cd %{mytmp} +wget -nc "http://download.skype.com/linux/skype-%{version}.tar.bz2" + +md5chk=$(md5sum skype-%{version}.tar.bz2 | cut -d' ' -f1) +if [[ %{md5} != $md5chk ]]; then +rm skype-%{version}.tar.bz2 +cd .. +rm -r %{mytmp} +echo "Error - download failed" +exit 1 +fi + +%install + +rm -rf $RPM_BUILD_ROOT +install -d -m 0755 %buildroot%{_bindir} +install -d -m 0755 %buildroot%{_datadir}/applications +touch %buildroot%{_datadir}/applications/skype.desktop + +install -d -m 0755 %buildroot%{instdir} +touch %buildroot%{instdir}/{skype.desktop,skype,skype.conf,LICENSE,README} + +install -d -m 0755 %buildroot%{langdir} +while read line; do +touch %buildroot%{langdir}/skype_"$line" +done < %{SOURCE2} + +install -d -m 0755 %buildroot%{instdir}/icons +install -d -m 0755 %buildroot%{_iconsdir} +touch %buildroot%{_iconsdir}/skype.png +for i in 16 32 48; do +touch %buildroot%{_iconsdir}/SkypeBlue_${i}x${i}.png +touch %buildroot%{instdir}/icons/SkypeBlue_${i}x${i}.png +done + +install -d -m 0755 %buildroot%{avatardir} +while read line; do +touch %buildroot%{avatardir}/"$line" +done < %{SOURCE0} + +install -d -m 0755 %buildroot%{sounddir} +while read line; do +touch %buildroot%{sounddir}/"$line" +done < %{SOURCE1} + +echo "LD_PRELOAD=/usr/lib/libv4l/v4l2convert.so %{instdir}/skype --resources=%{instdir}"\ + > %buildroot%{_bindir}/skype && chmod +x %buildroot%{_bindir}/skype + +%post + +newtmp=$(mktemp -d) +%define tmpextdir $newtmp +cd %{tmpextdir} +tar jxf %{mytmp}/skype-%{version}.tar.bz2 + +%define tmpdir %{tmpextdir}/skype-%{version} +mkdir %{instdir} + +cp -a %{tmpdir}/icons/* %{_iconsdir} +cp -a %{_iconsdir}/SkypeBlue_48x48.png %{_iconsdir}/skype.png +cp -a %{tmpdir}/skype.desktop %{_datadir}/applications/ +mv %{tmpdir}/skype %{instdir} +mv %{tmpdir}/skype.desktop %{instdir} +mv %{tmpdir}/skype.conf %{instdir} +mv %{tmpdir}/LICENSE %{instdir} +mv %{tmpdir}/README %{instdir} +mv %{tmpdir}/avatars %{instdir} +mv %{tmpdir}/lang %{langdir} +mv %{tmpdir}/sounds %{sounddir} +mv %{tmpdir}/icons %{icondir} +rm -r %{tmpdir} +cd .. +rm -r %{tmpextdir} +rm -r %{mytmp} + +%clean + +rm -rf $RPM_BUILD_ROOT + +%files + +%defattr(-,root,root) +%{_bindir}/skype +%ghost %{_iconsdir}/skype.png +%ghost %{_iconsdir}/SkypeBlue_*.png +%ghost %{_datadir}/applications/skype.desktop +%ghost %{instdir} + +%changelog + +* Sat Jun 11 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-6.mga1 +- Added md5sum check on download and cleanup on fail. +- Downloads to /var/lib/get-skype - removed after install. +- Creates unique /tmp/tmp.xxxx dir for extraction of tar. +- Added versioning to .txt files. +- Added removal of all tmp directories after install. +- Corrected URL: + +* Thu Jun 9 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-5.mga1 +- Bumped release to test update - no changes + +* Thu Jun 9 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-4.mga1 +- Moved installation to /usr/share instead of /opt +- Changed group and license +- Changed temporary dir +- Changed to wget for d/l + +* Mon Jun 6 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-2.mga1 +- Moved download to %pre to stop install if d/l fails + +* Sun Jun 5 2011 Barry Jackson <zen25000@zen.co.uk> 2.2.0.35-1.mga1 +- Changed get-skype version to follow Skype version. +- Changed URL to directly download only correct version. +- A copy of the downloaded file is retained in /tmp/skype-%{version} to +- speed re-installation (unless you clean /tmp) + +* Sat Jun 4 2011 Barry Jackson <zen25000@zen.co.uk> 0.2.mga1 +- Now all files are registered in rpm database. +- lang, avatar and sound filenames supplied in source files. + diff --git a/zarb-ml/mageia-dev/attachments/20110611/976fba78/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110611/976fba78/attachment-0001.html new file mode 100644 index 000000000..a7db4bb84 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110611/976fba78/attachment-0001.html @@ -0,0 +1,39 @@ +<!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:'Sans Serif'; font-size:10pt; 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;">Le samedi 11 juin 2011 12:06:55, Christiaan Welvaart a écrit :</p> +<p 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 Fri, 10 Jun 2011, Michael Scherer 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;">> > We can agree that everybody want something newer for some rpms, but few</p> +<p 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 want everything to be newer ( ie, now one run backports as 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;">> > update media, I think ). So as much as I am against asking to users</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > questions, we must show them the choice somewhere, in a non obstrusive</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > way.</p> +<p 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;">> Maybe, but how would be "support" this? We must be able to reproduce 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;">> reported problem. This becomes complicated when we don't know what 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;">> installed on the user's system. A guideline for bug reporters is (or</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> should be) "make sure you installed the latest updates". What would be 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;">> equivalent for backports? I'm afraid it should be "if you installed 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;">> backports, make sure you installed all backports that are relevant for</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> your system". If someone has a problem with any other combination, the bug</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> report might be rejected. How would QA even work when only selected</p> +<p 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 are upgraded from backports, or integration testing:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> integration with what?</p> +<p 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;">> So the only combinations we can support are:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> - release + 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;">> - release + updates + 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;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> More practical: for mga1 I have a VM that I can keep updated. For mga1</p> +<p 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 I can install another VM with backports enabled. But for bugs</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> reported with only selected backports installed I suppose I would have 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;">> install a new VM with mga1, update it, and install only those 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;">> for each bug report. But maybe I'm missing something, please explain. (:</p> +<p 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; -qt-user-state:0;"><br /></p> +<p 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 suppose that either updates or backports are supported (with a support level to be defined), the situation is simpler to me : a good backport must work with all its dependencies coming from updates or release OR it must explicitly require higher versions, found only in the backports media and so automatically pulled.</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; -qt-user-state:0;"><br /></p> +<p 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 I don't think that having picked up only certain backported packages is a problem for the maintainer's support. Maybe I over-simplified the situation, but I don't think it will be as complex as you say.</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; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Samuel </p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110611/976fba78/attachment.html b/zarb-ml/mageia-dev/attachments/20110611/976fba78/attachment.html new file mode 100644 index 000000000..a7db4bb84 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110611/976fba78/attachment.html @@ -0,0 +1,39 @@ +<!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:'Sans Serif'; font-size:10pt; 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;">Le samedi 11 juin 2011 12:06:55, Christiaan Welvaart a écrit :</p> +<p 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 Fri, 10 Jun 2011, Michael Scherer 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;">> > We can agree that everybody want something newer for some rpms, but few</p> +<p 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 want everything to be newer ( ie, now one run backports as 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;">> > update media, I think ). So as much as I am against asking to users</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > questions, we must show them the choice somewhere, in a non obstrusive</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > way.</p> +<p 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;">> Maybe, but how would be "support" this? We must be able to reproduce 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;">> reported problem. This becomes complicated when we don't know what 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;">> installed on the user's system. A guideline for bug reporters is (or</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> should be) "make sure you installed the latest updates". What would be 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;">> equivalent for backports? I'm afraid it should be "if you installed 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;">> backports, make sure you installed all backports that are relevant for</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> your system". If someone has a problem with any other combination, the bug</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> report might be rejected. How would QA even work when only selected</p> +<p 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 are upgraded from backports, or integration testing:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> integration with what?</p> +<p 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;">> So the only combinations we can support are:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> - release + 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;">> - release + updates + 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;">> </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> More practical: for mga1 I have a VM that I can keep updated. For mga1</p> +<p 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 I can install another VM with backports enabled. But for bugs</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> reported with only selected backports installed I suppose I would have 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;">> install a new VM with mga1, update it, and install only those 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;">> for each bug report. But maybe I'm missing something, please explain. (:</p> +<p 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; -qt-user-state:0;"><br /></p> +<p 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 suppose that either updates or backports are supported (with a support level to be defined), the situation is simpler to me : a good backport must work with all its dependencies coming from updates or release OR it must explicitly require higher versions, found only in the backports media and so automatically pulled.</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; -qt-user-state:0;"><br /></p> +<p 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 I don't think that having picked up only certain backported packages is a problem for the maintainer's support. Maybe I over-simplified the situation, but I don't think it will be as complex as you say.</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; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Samuel </p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110611/cd906686/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110611/cd906686/attachment-0001.html new file mode 100644 index 000000000..ef0e38543 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110611/cd906686/attachment-0001.html @@ -0,0 +1,94 @@ +<!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:'Sans Serif'; font-size:10pt; 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;">Le samedi 11 juin 2011 18:01:54, Maarten Vanraes a écrit :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Op zaterdag 11 juni 2011 16:55:00 schreef Samuel Verschelde:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > Le samedi 11 juin 2011 14:26:19, Maarten Vanraes a écrit :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > Op zaterdag 11 juni 2011 13:14:29 schreef Samuel Verschelde:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > Le samedi 11 juin 2011 12:06:55, Christiaan Welvaart a écrit :</p> +<p 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 Fri, 10 Jun 2011, Michael Scherer 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;">> > > > > > We can agree that everybody want something newer for some rpms,</p> +<p 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 few people want everything to be newer ( ie, now one run</p> +<p 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 as a update media, I think ). So as much as I am</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > > against asking to users questions, we must show them the choice</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > > somewhere, in a non obstrusive way.</p> +<p 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;">> > > > > Maybe, but how would be "support" this? We must be able 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;">> > > > > reproduce a reported problem. This becomes complicated when we</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > don't know what is installed on the user's system. A guideline for</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > bug reporters is (or should be) "make sure you installed 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;">> > > > > latest updates". What would be the equivalent for backports? I'm</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > afraid it should be "if you installed any backports, make sure you</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > installed all backports that are relevant for your system". If</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > someone has a problem with any other combination, the bug report</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > might be rejected. How would QA even work when only selected</p> +<p 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 are upgraded from backports, or integration testing:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > integration with what?</p> +<p 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;">> > > > > So the only combinations we can support are:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > - release + 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;">> > > > > - release + updates + 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;">> > > > > </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > More practical: for mga1 I have a VM that I can keep updated. For</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > mga1 backports I can install another VM with backports enabled. But</p> +<p 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 bugs reported with only selected backports installed I suppose</p> +<p 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 have to install a new VM with mga1, update it, and 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;">> > > > > only those 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;">> > > > > </p> +<p 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 each bug report. But maybe I'm missing something, please</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > explain.</p> +<p 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;">> > > > If we suppose that either updates or backports are supported (with 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;">> > > > support level to be defined), the situation is simpler to me : 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;">> > > > good backport must work with all its dependencies coming from</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > updates or release OR it must explicitly require higher versions,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > found only in the backports media and so automatically pulled.</p> +<p 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;">> > > > So I don't think that having picked up only certain backported</p> +<p 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 is a problem for the maintainer's support. Maybe I</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > over-simplified the situation, but I don't think it will be 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;">> > > > complex as you say.</p> +<p 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;">> > > > Samuel</p> +<p 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;">> > > imho this creates more work for packagers or qa team to support</p> +<p 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, i'm not really in favor of this solution</p> +<p 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;">> > So it someone has a problem with a package you backported and reports 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;">> > in bugzilla, you'll answer "not supported" and close the door ? Then we</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > have not a single chance to have users accept to use backports rather</p> +<p 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 ask for a rolling release (supposing that we want to stay with</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > stable releases model, which hasn't been decided yet).</p> +<p 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;">> > In my opinion, a backport must be either supported or not exist. Even 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;">> > Mandriva, where everybody keep saying "backports ain't supported",</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > usually people try to solve the problems caused by 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;">> > </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > However, the level of support can be different between backports 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;">> > updates, as I said in my previous message. The differences are yet 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;">> > define, but here are some I see :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > - when a critical bug in a backport exists, you can simply update to 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;">> > newer version and see if it's solved</p> +<p 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 the program already is in its the latest version and has an upstream</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > bug, you can answer "report the bug upstream" and stop there until</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > upstream solves the bug. For packages in release or updates, ideally you</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > have to try to help fixing it or work it around because the bug 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;">> > considered part of the whole distribution.</p> +<p 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;">> > Best 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;">> > </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > Samuel</p> +<p 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;">> What about security fixes? if there's 1 version in release and 10 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;">> backports? do the older backported packages have to be securitypatched?</p> +<p 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;">> imho not supported backports means that if backports has an issue, try 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;">> newer 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;">> </p> +<p 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 that is a good level, that doesn't require much effort.</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; -qt-user-state:0;"><br /></p> +<p 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 agree, because if we follow the Mandriva way, upload of a new backport for a given package removes the old one if there is one. So at a given time, you only have to support the package in release or updates + 0 or 1 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; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Samuel</p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110611/cd906686/attachment.html b/zarb-ml/mageia-dev/attachments/20110611/cd906686/attachment.html new file mode 100644 index 000000000..ef0e38543 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110611/cd906686/attachment.html @@ -0,0 +1,94 @@ +<!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:'Sans Serif'; font-size:10pt; 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;">Le samedi 11 juin 2011 18:01:54, Maarten Vanraes a écrit :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Op zaterdag 11 juni 2011 16:55:00 schreef Samuel Verschelde:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > Le samedi 11 juin 2011 14:26:19, Maarten Vanraes a écrit :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > Op zaterdag 11 juni 2011 13:14:29 schreef Samuel Verschelde:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > Le samedi 11 juin 2011 12:06:55, Christiaan Welvaart a écrit :</p> +<p 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 Fri, 10 Jun 2011, Michael Scherer 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;">> > > > > > We can agree that everybody want something newer for some rpms,</p> +<p 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 few people want everything to be newer ( ie, now one run</p> +<p 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 as a update media, I think ). So as much as I am</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > > against asking to users questions, we must show them the choice</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > > somewhere, in a non obstrusive way.</p> +<p 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;">> > > > > Maybe, but how would be "support" this? We must be able 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;">> > > > > reproduce a reported problem. This becomes complicated when we</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > don't know what is installed on the user's system. A guideline for</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > bug reporters is (or should be) "make sure you installed 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;">> > > > > latest updates". What would be the equivalent for backports? I'm</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > afraid it should be "if you installed any backports, make sure you</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > installed all backports that are relevant for your system". If</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > someone has a problem with any other combination, the bug report</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > might be rejected. How would QA even work when only selected</p> +<p 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 are upgraded from backports, or integration testing:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > integration with what?</p> +<p 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;">> > > > > So the only combinations we can support are:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > - release + 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;">> > > > > - release + updates + 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;">> > > > > </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > More practical: for mga1 I have a VM that I can keep updated. For</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > mga1 backports I can install another VM with backports enabled. But</p> +<p 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 bugs reported with only selected backports installed I suppose</p> +<p 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 have to install a new VM with mga1, update it, and 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;">> > > > > only those 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;">> > > > > </p> +<p 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 each bug report. But maybe I'm missing something, please</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > > explain.</p> +<p 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;">> > > > If we suppose that either updates or backports are supported (with 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;">> > > > support level to be defined), the situation is simpler to me : 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;">> > > > good backport must work with all its dependencies coming from</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > updates or release OR it must explicitly require higher versions,</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > found only in the backports media and so automatically pulled.</p> +<p 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;">> > > > So I don't think that having picked up only certain backported</p> +<p 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 is a problem for the maintainer's support. Maybe I</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > over-simplified the situation, but I don't think it will be 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;">> > > > complex as you say.</p> +<p 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;">> > > > Samuel</p> +<p 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;">> > > imho this creates more work for packagers or qa team to support</p> +<p 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, i'm not really in favor of this solution</p> +<p 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;">> > So it someone has a problem with a package you backported and reports 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;">> > in bugzilla, you'll answer "not supported" and close the door ? Then we</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > have not a single chance to have users accept to use backports rather</p> +<p 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 ask for a rolling release (supposing that we want to stay with</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > stable releases model, which hasn't been decided yet).</p> +<p 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;">> > In my opinion, a backport must be either supported or not exist. Even 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;">> > Mandriva, where everybody keep saying "backports ain't supported",</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > usually people try to solve the problems caused by 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;">> > </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > However, the level of support can be different between backports 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;">> > updates, as I said in my previous message. The differences are yet 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;">> > define, but here are some I see :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > - when a critical bug in a backport exists, you can simply update to 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;">> > newer version and see if it's solved</p> +<p 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 the program already is in its the latest version and has an upstream</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > bug, you can answer "report the bug upstream" and stop there until</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > upstream solves the bug. For packages in release or updates, ideally you</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > have to try to help fixing it or work it around because the bug 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;">> > considered part of the whole distribution.</p> +<p 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;">> > Best 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;">> > </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > Samuel</p> +<p 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;">> What about security fixes? if there's 1 version in release and 10 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;">> backports? do the older backported packages have to be securitypatched?</p> +<p 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;">> imho not supported backports means that if backports has an issue, try 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;">> newer 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;">> </p> +<p 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 that is a good level, that doesn't require much effort.</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; -qt-user-state:0;"><br /></p> +<p 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 agree, because if we follow the Mandriva way, upload of a new backport for a given package removes the old one if there is one. So at a given time, you only have to support the package in release or updates + 0 or 1 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; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Samuel</p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110611/e0b9ab4a/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20110611/e0b9ab4a/attachment-0001.html new file mode 100644 index 000000000..0e0182e90 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110611/e0b9ab4a/attachment-0001.html @@ -0,0 +1,62 @@ +<!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:'Sans Serif'; font-size:10pt; 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;">Le samedi 11 juin 2011 14:26:19, Maarten Vanraes a écrit :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Op zaterdag 11 juni 2011 13:14:29 schreef Samuel Verschelde:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > Le samedi 11 juin 2011 12:06:55, Christiaan Welvaart a écrit :</p> +<p 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 Fri, 10 Jun 2011, Michael Scherer 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;">> > > > We can agree that everybody want something newer for some rpms, but</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > few people want everything to be newer ( ie, now one run 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;">> > > > as a update media, I think ). So as much as I am against asking 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;">> > > > users questions, we must show them the choice somewhere, in a non</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > obstrusive way.</p> +<p 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;">> > > Maybe, but how would be "support" this? We must be able to reproduce 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;">> > > reported problem. This becomes complicated when we don't know what 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;">> > > installed on the user's system. A guideline for bug reporters is (or</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > should be) "make sure you installed the latest updates". What would 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;">> > > the equivalent for backports? I'm afraid it should be "if you installed</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > any backports, make sure you installed all backports that are relevant</p> +<p 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 your system". If someone has a problem with any other combination,</p> +<p 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 bug report might be rejected. How would QA even work when 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;">> > > selected packages are upgraded from backports, or integration testing:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > integration with what?</p> +<p 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;">> > > So the only combinations we can support are:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > - release + 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;">> > > - release + updates + 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;">> > > </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > More practical: for mga1 I have a VM that I can keep updated. For mga1</p> +<p 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 I can install another VM with backports enabled. But for bugs</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > reported with only selected backports installed I suppose I would 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;">> > > to install a new VM with mga1, update it, and install only those</p> +<p 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 -</p> +<p 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;">> > > for each bug report. But maybe I'm missing something, please explain. (:</p> +<p 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 suppose that either updates or backports are supported (with 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;">> > support level to be defined), the situation is simpler to me : a good</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > backport must work with all its dependencies coming from updates or</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > release OR it must explicitly require higher versions, found only in 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;">> > backports media and so automatically pulled.</p> +<p 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;">> > So I don't think that having picked up only certain backported packages</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > is a problem for the maintainer's support. Maybe I over-simplified 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;">> > situation, but I don't think it will be as complex as you say.</p> +<p 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;">> > Samuel</p> +<p 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;">> imho this creates more work for packagers or qa team to support 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;">> i'm not really in favor of this solution</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; -qt-user-state:0;"><br /></p> +<p 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 it someone has a problem with a package you backported and reports it in bugzilla, you'll answer "not supported" and close the door ? Then we have not a single chance to have users accept to use backports rather than ask for a rolling release (supposing that we want to stay with stable releases model, which hasn't been decided 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; -qt-user-state:0;"><br /></p> +<p 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 my opinion, a backport must be either supported or not exist. Even in Mandriva, where everybody keep saying "backports ain't supported", usually people try to solve the problems caused by 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; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">However, the level of support can be different between backports and updates, as I said in my previous message. The differences are yet to define, but here are some I see :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">- when a critical bug in a backport exists, you can simply update to a newer version and see if it's solved</p> +<p 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 the program already is in its the latest version and has an upstream bug, you can answer "report the bug upstream" and stop there until upstream solves the bug. For packages in release or updates, ideally you have to try to help fixing it or work it around because the bug is considered part of the whole distribution.</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; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Best regards</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; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Samuel</p></body></html>
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/attachments/20110611/e0b9ab4a/attachment.html b/zarb-ml/mageia-dev/attachments/20110611/e0b9ab4a/attachment.html new file mode 100644 index 000000000..0e0182e90 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20110611/e0b9ab4a/attachment.html @@ -0,0 +1,62 @@ +<!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:'Sans Serif'; font-size:10pt; 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;">Le samedi 11 juin 2011 14:26:19, Maarten Vanraes a écrit :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Op zaterdag 11 juni 2011 13:14:29 schreef Samuel Verschelde:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > Le samedi 11 juin 2011 12:06:55, Christiaan Welvaart a écrit :</p> +<p 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 Fri, 10 Jun 2011, Michael Scherer 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;">> > > > We can agree that everybody want something newer for some rpms, but</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > few people want everything to be newer ( ie, now one run 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;">> > > > as a update media, I think ). So as much as I am against asking 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;">> > > > users questions, we must show them the choice somewhere, in a non</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > > obstrusive way.</p> +<p 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;">> > > Maybe, but how would be "support" this? We must be able to reproduce 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;">> > > reported problem. This becomes complicated when we don't know what 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;">> > > installed on the user's system. A guideline for bug reporters is (or</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > should be) "make sure you installed the latest updates". What would 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;">> > > the equivalent for backports? I'm afraid it should be "if you installed</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > any backports, make sure you installed all backports that are relevant</p> +<p 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 your system". If someone has a problem with any other combination,</p> +<p 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 bug report might be rejected. How would QA even work when 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;">> > > selected packages are upgraded from backports, or integration testing:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > integration with what?</p> +<p 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;">> > > So the only combinations we can support are:</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > - release + 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;">> > > - release + updates + 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;">> > > </p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > More practical: for mga1 I have a VM that I can keep updated. For mga1</p> +<p 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 I can install another VM with backports enabled. But for bugs</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > > reported with only selected backports installed I suppose I would 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;">> > > to install a new VM with mga1, update it, and install only those</p> +<p 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 -</p> +<p 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;">> > > for each bug report. But maybe I'm missing something, please explain. (:</p> +<p 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 suppose that either updates or backports are supported (with 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;">> > support level to be defined), the situation is simpler to me : a good</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > backport must work with all its dependencies coming from updates or</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > release OR it must explicitly require higher versions, found only in 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;">> > backports media and so automatically pulled.</p> +<p 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;">> > So I don't think that having picked up only certain backported packages</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> > is a problem for the maintainer's support. Maybe I over-simplified 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;">> > situation, but I don't think it will be as complex as you say.</p> +<p 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;">> > Samuel</p> +<p 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;">> imho this creates more work for packagers or qa team to support 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;">> i'm not really in favor of this solution</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; -qt-user-state:0;"><br /></p> +<p 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 it someone has a problem with a package you backported and reports it in bugzilla, you'll answer "not supported" and close the door ? Then we have not a single chance to have users accept to use backports rather than ask for a rolling release (supposing that we want to stay with stable releases model, which hasn't been decided 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; -qt-user-state:0;"><br /></p> +<p 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 my opinion, a backport must be either supported or not exist. Even in Mandriva, where everybody keep saying "backports ain't supported", usually people try to solve the problems caused by 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; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">However, the level of support can be different between backports and updates, as I said in my previous message. The differences are yet to define, but here are some I see :</p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">- when a critical bug in a backport exists, you can simply update to a newer version and see if it's solved</p> +<p 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 the program already is in its the latest version and has an upstream bug, you can answer "report the bug upstream" and stop there until upstream solves the bug. For packages in release or updates, ideally you have to try to help fixing it or work it around because the bug is considered part of the whole distribution.</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; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Best regards</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; -qt-user-state:0;"><br /></p> +<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Samuel</p></body></html>
\ No newline at end of file |