1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
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:
><i> 'Twas brillig, and Johnny A. Solbu at 08/12/12 10:37 did gyre and gimble:
</I>><i> > On Saturday 8. December 2012 11.06, Guillaume Rousse wrote:
</I>><i> >>> Unless I misunderstand, adding it to «task-obsolete» does the same thing, with a 2 week delay on deleting.
</I>><i> >>> So the proper action would be to add it to «task-obsolete».
</I>><i> >> That's still not the proper action.
</I>><i> >
</I>><i> > In other words, I did misunderstand.
</I>><i> >
</I>><i> >> Stop removing packages from end
</I>><i> >> user machines just to remove them from the mirrors as a side effect of
</I>><i> >> our package submission procedure.
</I>><i> >
</I>><i> > So what should we do?
</I>><i> > The current packaging guidelines[1] says that this is the correct action for obsolete packages, which a depcrecated package is.
</I>><i> > 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>><i> >
</I>><i> > [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>><i>
</I>><i> I totally agree with Johnny here. If users want to keep unmaintained and
</I>><i> no-longer-supplied packages on their machine (obviously making a
</I>><i> concious decision to not get security updates etc. on such packages)
</I>><i> then they are welcome to add task-obsolete to their urpmi skip lists.
</I>><i>
</I>><i> I see absolutely no problem with this and I don't consider this
</I>><i> something that's done as a "side effect", rather it's a quite deliberate
</I>><i> and concious mechanism to remove no longer supported packages from a
</I>><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
"unsupported" 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>
|
