diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2010-November/000140.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2010-November/000140.html | 134 |
1 files changed, 134 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2010-November/000140.html b/zarb-ml/mageia-sysadm/2010-November/000140.html new file mode 100644 index 000000000..e98264e59 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-November/000140.html @@ -0,0 +1,134 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] Packages SVN + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Packages%20SVN&In-Reply-To=%3C1288653849.7069.16.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000137.html"> + <LINK REL="Next" HREF="000144.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Packages SVN</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Packages%20SVN&In-Reply-To=%3C1288653849.7069.16.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-sysadm] Packages SVN">misc at zarb.org + </A><BR> + <I>Tue Nov 2 00:24:09 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="000137.html">[Mageia-sysadm] Packages SVN +</A></li> + <LI>Next message: <A HREF="000144.html">[Mageia-sysadm] Packages SVN +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#140">[ date ]</a> + <a href="thread.html#140">[ thread ]</a> + <a href="subject.html#140">[ subject ]</a> + <a href="author.html#140">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le lundi 01 novembre 2010 à 16:25 +0100, nicolas vigier a écrit : +><i> Hello, +</I>><i> +</I>><i> To avoid the problem of a growing svn repository full of old tarballs, I +</I>><i> think it is a good time to start using separate repositories for binary +</I>><i> files. +</I>><i> +</I>><i> repsys has a branch called "binrepo-svn" with support for separate +</I>><i> binary repositories : +</I>><i> <A HREF="http://git.mandriva.com/?p=projects/repsys.git;a=summary">http://git.mandriva.com/?p=projects/repsys.git;a=summary</A> +</I>><i> The README file is interesting : +</I>><i> <A HREF="http://git.mandriva.com/?p=projects/repsys.git;a=blob;f=BRANCH;h=ebb87c7d6d20daa476ed49990b150ac45b02ddf4;hb=binrepo-svn">http://git.mandriva.com/?p=projects/repsys.git;a=blob;f=BRANCH;h=ebb87c7d6d20daa476ed49990b150ac45b02ddf4;hb=binrepo-svn</A> +</I>><i> +</I>><i> About packages import, I would not import a copy of Mandriva svn, but +</I>><i> instead do something like this : +</I>><i> for file in *.src.rpm +</I>><i> do +</I>><i> mdvsys import $file +</I>><i> done +</I>><i> We lose all svn history, but it allows us to have a much smaller +</I>><i> repository (without all the tarballs history), and we can keep a +</I>><i> readonly copy of Mandriva repository somewhere for reference. +</I>><i> +</I>><i> What do you think ? +</I> +My main fear would be that this code is basically untested. So could we +please do a full test run before ( like let people test the repository +at least once before declaring this is "production" ) +? + +We should write a test procedure, with error cases : += import = + - import a package + - import a binary rpm + - import a random file ( and see it doesn't work ) + - reimport a rpm already present += checkout = + - checkout a package + - checkout a package that do not exist yet + - commit a change + - commit something that violate something fobidden by hook + - change the tarball and commit it + += submit + - submit it + - submit a non existing rpm + - submit a rpm with some problem in the srpm + - missing macros + - submit a rpm without increasing the release/version + - submit a older rpm + - submit a rpm that violate some youri rules ( or rpmlint one ) + += build = + - build a rpm + - build a rpm that do not work + - missing builddeps ( ie, at rpm level ) + - error in the build ( segfault, missing file ) + - over capacity ( memory, disk space ) + - build a backport + - build a update + - build a rpm with arch and noarch + - build rpm with ArchExcluded + - build a rpm for only one of the 2 arch ( or even no valid arch, like +sparc ) + +and maybe test the robustness of every component ( ie, how does the +server react if we stop ecosse/jonund, how does the main scheduler work +if we stop something else, etc ). + +I tried to be exhaustive, but I guess I wasn't, so do not hesitate to +complete :) + +-- +Michael Scherer + +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000137.html">[Mageia-sysadm] Packages SVN +</A></li> + <LI>Next message: <A HREF="000144.html">[Mageia-sysadm] Packages SVN +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#140">[ date ]</a> + <a href="thread.html#140">[ thread ]</a> + <a href="subject.html#140">[ subject ]</a> + <a href="author.html#140">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |