blob: 9211cf80ea337dad92626ea0d5c72a3d405b9846 (
plain)
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Proposal of a backporting process
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C20110628095559.09d7f703.john%40neodoc.biz%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006070.html">
<LINK REL="Next" HREF="006072.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Proposal of a backporting process</H1>
<B>John</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C20110628095559.09d7f703.john%40neodoc.biz%3E"
TITLE="[Mageia-dev] Proposal of a backporting process">john at neodoc.biz
</A><BR>
<I>Mon Jun 27 23:55:59 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006070.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI>Next message: <A HREF="006072.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6071">[ date ]</a>
<a href="thread.html#6071">[ thread ]</a>
<a href="subject.html#6071">[ subject ]</a>
<a href="author.html#6071">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Mon, 27 Jun 2011 20:17:22 +0100
Colin Guthrie wrote:
><i> 'Twas brillig, and Michael Scherer at 25/06/11 23:16 did gyre and gimble:
</I>><i> >> we
</I>><i> >> always say that backports should mainly be cherry picked, but not
</I>><i> >> enabled all the time... so how does installing a new version of e.g.
</I>><i> >> wine break the user's system when he can easily back out that rpm?
</I>><i> >
</I>><i> > I a not sure that most people realize they can revert. Maybe a easier
</I>><i> > interface to do that could be offered ( along maybe with a tool that
</I>><i> > send feedback on why it did downgrade it ? ).
</I>><i>
</I>><i> I've seen various ppa-purge commands being dished out for custom PPAs on
</I>><i> Ubuntu. It looks like quite a nice idea, but only really applies for
</I>><i> individual use archives (e.g. help us test the development version of
</I>><i> $foo), not a general purpose one like "backports".
</I>><i>
</I>><i> That said, a GUI which detected that certain packages have come from
</I>><i> backports and offers and easy mechanism to "switch" back to the older
</I>><i> one from release or updates would, IMO, be a plus.
</I>
Rpms from Tainted have 'tainted' in the filename - why not do the same for
backports? Surely that would make their identification a little simpler?
John NZ
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006070.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI>Next message: <A HREF="006072.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6071">[ date ]</a>
<a href="thread.html#6071">[ thread ]</a>
<a href="subject.html#6071">[ subject ]</a>
<a href="author.html#6071">[ 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>
|