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
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] How to push new packages to Mageia 1 updates_testing
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20to%20push%20new%20packages%20to%20Mageia%201%0A%09updates_testing&In-Reply-To=%3CCAJmd%2BxoyUJGVCbF48GQcKNcabhxbL%2BhVcxFQZNou5mjZKeVamQ%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006842.html">
<LINK REL="Next" HREF="006845.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] How to push new packages to Mageia 1 updates_testing</H1>
<B>Ahmad Samir</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20to%20push%20new%20packages%20to%20Mageia%201%0A%09updates_testing&In-Reply-To=%3CCAJmd%2BxoyUJGVCbF48GQcKNcabhxbL%2BhVcxFQZNou5mjZKeVamQ%40mail.gmail.com%3E"
TITLE="[Mageia-dev] How to push new packages to Mageia 1 updates_testing">ahmadsamir3891 at gmail.com
</A><BR>
<I>Mon Jul 18 07:34:13 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006842.html">[Mageia-dev] How to push new packages to Mageia 1 updates_testing
</A></li>
<LI>Next message: <A HREF="006845.html">[Mageia-dev] [Mageia 2 specifications] Wiki page
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6850">[ date ]</a>
<a href="thread.html#6850">[ thread ]</a>
<a href="subject.html#6850">[ subject ]</a>
<a href="author.html#6850">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 17 July 2011 23:43, Samuel Verschelde <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi at laposte.net</A>> wrote:
><i> Hi,
</I>><i>
</I>><i> I wanted to share the method I use when I need to push a new package (new =
</I>><i> missing from Mageia 1) from cauldron to Mageia 1 updates. This concerns only
</I>><i> packages available in Mandriva 2010.2 but absent from Mageia 1.
</I>><i>
</I>><i> I'm sharing for 2 reasons :
</I>><i> - maybe I'm doing it wrong, so you can comment and maybe give me better instructions
</I>><i> - it can be of use, the way I do it or the way I will be told to do :)
</I>><i>
</I>><i> Here is my procedure :
</I>><i>
</I>><i> svn cp svn+<A HREF="ssh://svn.mageia.org/svn/packages/cauldron/PACKAGENAME">ssh://svn.mageia.org/svn/packages/cauldron/PACKAGENAME</A> svn+<A HREF="ssh://svn.mageia.org/svn/packages/updates/1/PACKAGENAME">ssh://svn.mageia.org/svn/packages/updates/1/PACKAGENAME</A>
</I>><i> (with comment "Add PACKAGENAME to Mageia 1")
</I>><i> svn mkdir svn+<A HREF="ssh://svn.mageia.org/svn/binrepos/updates/1/putty">ssh://svn.mageia.org/svn/binrepos/updates/1/putty</A>
</I>><i> (with comment "Add PACKAGENAME")
</I>
'svn mkdir' step is redundant, 'mgarepo sync -c' will automatically
create the binrepos/updates/1/$pkg-name.
><i> mgarepo co 1/PACKAGENAME
</I>><i> cd PACKAGENAME
</I>><i> cp PATH_TO_BINARY_SOURCE_FILES_IN_CAULDRON SOURCES/
</I>><i> mgarepo sync -c #uploads the source files to binrepo
</I>><i> vi SPECS/PACKAGENAME.spec #update release and add subrel
</I>><i> mgarepo submit -t 1 --define section=core/updates_testing
</I>><i>
</I>><i> For release and subrel, usually a new package would have release 0 and subrel
</I>><i> 1, but to allow migration from mandriva, I set a higher release that in
</I>><i> mandriva 2010.2 if the version is the same, + subrel 1, then increase it in cauldron too so
</I>><i> that it's higher than in Mageia 1.
</I>><i>
</I>><i> I do that to be safe : the point of subrel is to be increased without any risk
</I>><i> of the package becoming not upgradable to the version in the n+1 distribution.
</I>><i> If cauldron has release 5.mga2 and updates has 5.mga1, it looks safe, but as
</I>><i> soon as we'll fix a bug in mga1, release will become 5.1.mga1 which is higher
</I>><i> than 5.mga2. That's why, for security, I would set the release in cauldron to
</I>><i> 6.mga2 so that we can increase the subrel at will in mga1.
</I>><i>
</I>><i> Comments ?
</I>><i>
</I>><i> Samuel Verschelde
</I>><i>
</I>
--
Ahmad Samir
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006842.html">[Mageia-dev] How to push new packages to Mageia 1 updates_testing
</A></li>
<LI>Next message: <A HREF="006845.html">[Mageia-dev] [Mageia 2 specifications] Wiki page
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6850">[ date ]</a>
<a href="thread.html#6850">[ thread ]</a>
<a href="subject.html#6850">[ subject ]</a>
<a href="author.html#6850">[ 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>
|
