<!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%20updates_testing&In-Reply-To=%3C201107172343.59608.stormi%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006941.html">
<LINK REL="Next" HREF="006850.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] How to push new packages to Mageia 1 updates_testing</H1>
<B>Samuel Verschelde</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20to%20push%20new%20packages%20to%20Mageia%201%20updates_testing&In-Reply-To=%3C201107172343.59608.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] How to push new packages to Mageia 1 updates_testing">stormi at laposte.net
</A><BR>
<I>Sun Jul 17 23:43:59 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006941.html">[Mageia-dev] [RPM] cauldron nonfree/release flash-player-plugin11-11.0.1.60-0.b1.071311.1.mga2.nonfree
</A></li>
<LI>Next message: <A HREF="006850.html">[Mageia-dev] How to push new packages to Mageia 1 updates_testing
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6842">[ date ]</a>
<a href="thread.html#6842">[ thread ]</a>
<a href="subject.html#6842">[ subject ]</a>
<a href="author.html#6842">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hi,
I wanted to share the method I use when I need to push a new package (new =
missing from Mageia 1) from cauldron to Mageia 1 updates. This concerns only
packages available in Mandriva 2010.2 but absent from Mageia 1.
I'm sharing for 2 reasons :
- maybe I'm doing it wrong, so you can comment and maybe give me better instructions
- it can be of use, the way I do it or the way I will be told to do :)
Here is my procedure :
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>
(with comment "Add PACKAGENAME to Mageia 1")
svn mkdir svn+<A HREF="ssh://svn.mageia.org/svn/binrepos/updates/1/putty">ssh://svn.mageia.org/svn/binrepos/updates/1/putty</A>
(with comment "Add PACKAGENAME")
mgarepo co 1/PACKAGENAME
cd PACKAGENAME
cp PATH_TO_BINARY_SOURCE_FILES_IN_CAULDRON SOURCES/
mgarepo sync -c #uploads the source files to binrepo
vi SPECS/PACKAGENAME.spec #update release and add subrel
mgarepo submit -t 1 --define section=core/updates_testing
For release and subrel, usually a new package would have release 0 and subrel
1, but to allow migration from mandriva, I set a higher release that in
mandriva 2010.2 if the version is the same, + subrel 1, then increase it in cauldron too so
that it's higher than in Mageia 1.
I do that to be safe : the point of subrel is to be increased without any risk
of the package becoming not upgradable to the version in the n+1 distribution.
If cauldron has release 5.mga2 and updates has 5.mga1, it looks safe, but as
soon as we'll fix a bug in mga1, release will become 5.1.mga1 which is higher
than 5.mga2. That's why, for security, I would set the release in cauldron to
6.mga2 so that we can increase the subrel at will in mga1.
Comments ?
Samuel Verschelde
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006941.html">[Mageia-dev] [RPM] cauldron nonfree/release flash-player-plugin11-11.0.1.60-0.b1.071311.1.mga2.nonfree
</A></li>
<LI>Next message: <A HREF="006850.html">[Mageia-dev] How to push new packages to Mageia 1 updates_testing
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6842">[ date ]</a>
<a href="thread.html#6842">[ thread ]</a>
<a href="subject.html#6842">[ subject ]</a>
<a href="author.html#6842">[ 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>