summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-December/020711.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-December/020711.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-dev/2012-December/020711.html')
-rw-r--r--zarb-ml/mageia-dev/2012-December/020711.html109
1 files changed, 109 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-December/020711.html b/zarb-ml/mageia-dev/2012-December/020711.html
new file mode 100644
index 000000000..c10f58c69
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-December/020711.html
@@ -0,0 +1,109 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Package drop request: ruby-ParseTree
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Package%20drop%20request%3A%20ruby-ParseTree&In-Reply-To=%3C20121210142702.GQ21938%40mars-attacks.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="020709.html">
+ <LINK REL="Next" HREF="020712.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Package drop request: ruby-ParseTree</H1>
+ <B>nicolas vigier</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Package%20drop%20request%3A%20ruby-ParseTree&In-Reply-To=%3C20121210142702.GQ21938%40mars-attacks.org%3E"
+ TITLE="[Mageia-dev] Package drop request: ruby-ParseTree">boklm at mars-attacks.org
+ </A><BR>
+ <I>Mon Dec 10 15:27:02 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="020709.html">[Mageia-dev] Package drop request: ruby-ParseTree
+</A></li>
+ <LI>Next message: <A HREF="020712.html">[Mageia-dev] Package drop request: ruby-ParseTree
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#20711">[ date ]</a>
+ <a href="thread.html#20711">[ thread ]</a>
+ <a href="subject.html#20711">[ subject ]</a>
+ <a href="author.html#20711">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Mon, 10 Dec 2012, Colin Guthrie wrote:
+
+&gt;<i> 'Twas brillig, and Johnny A. Solbu at 08/12/12 10:37 did gyre and gimble:
+</I>&gt;<i> &gt; On Saturday 8. December 2012 11.06, Guillaume Rousse wrote:
+</I>&gt;<i> &gt;&gt;&gt; Unless I misunderstand, adding it to &#171;task-obsolete&#187; does the same thing, with a 2 week delay on deleting.
+</I>&gt;<i> &gt;&gt;&gt; So the proper action would be to add it to &#171;task-obsolete&#187;.
+</I>&gt;<i> &gt;&gt; That's still not the proper action.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; In other words, I did misunderstand.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt;&gt; Stop removing packages from end
+</I>&gt;<i> &gt;&gt; user machines just to remove them from the mirrors as a side effect of
+</I>&gt;<i> &gt;&gt; our package submission procedure.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; So what should we do?
+</I>&gt;<i> &gt; The current packaging guidelines[1] says that this is the correct action for obsolete packages, which a depcrecated package is.
+</I>&gt;<i> &gt; If this is not the desired solution, then the guidelines should change. Perhaps just clairfied as to what is an obsolete package, which belongs in task-obsolete, and what is Not an obsolete package even if it's deprecated.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; [1] <A HREF="https://wiki.mageia.org/en/Packaging_guidelines#Obsoleting_a_package">https://wiki.mageia.org/en/Packaging_guidelines#Obsoleting_a_package</A>
+</I>&gt;<i>
+</I>&gt;<i> I totally agree with Johnny here. If users want to keep unmaintained and
+</I>&gt;<i> no-longer-supplied packages on their machine (obviously making a
+</I>&gt;<i> concious decision to not get security updates etc. on such packages)
+</I>&gt;<i> then they are welcome to add task-obsolete to their urpmi skip lists.
+</I>&gt;<i>
+</I>&gt;<i> I see absolutely no problem with this and I don't consider this
+</I>&gt;<i> something that's done as a &quot;side effect&quot;, rather it's a quite deliberate
+</I>&gt;<i> and concious mechanism to remove no longer supported packages from a
+</I>&gt;<i> users machine.
+</I>
+One of the problem with task-obsolete obsoleting packages is that it can
+silently uninstall packages and break something which was working,
+without warning.
+
+Maybe instead of obsoleting packages, task-obsolete could conflict with
+those packages :
+ - users who want to remove unsupported packages install task-obsolete,
+ and have a warning from rpmdrake/urpmi before conflicting packages
+ are removed
+ - users who don't want to remove unsupported packages don't install
+ task-obsolete. They can still ask urpmi to install task-obsolete to
+ see the list of packages it would remove.
+
+Or we can stop using task-obsolete package, and instead create a file
+&quot;unsupported&quot; in media_info directory on the mirrors containing a list
+of unsupported packages, and used by urpmq/urpme --unsupported to
+list/remove unsupported packages.
+
+What do you think ?
+
+</PRE>
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="020709.html">[Mageia-dev] Package drop request: ruby-ParseTree
+</A></li>
+ <LI>Next message: <A HREF="020712.html">[Mageia-dev] Package drop request: ruby-ParseTree
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#20711">[ date ]</a>
+ <a href="thread.html#20711">[ thread ]</a>
+ <a href="subject.html#20711">[ subject ]</a>
+ <a href="author.html#20711">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>