blob: 3c7aa63c8c26f5ef4693e9aa37caa5211a03bc84 (
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-i18n] I18N svn access
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-i18n%40mageia.org?Subject=Re%3A%20%5BMageia-i18n%5D%20I18N%20svn%20access&In-Reply-To=%3C20110425123643.GB21138%40sisay.ephaone.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001344.html">
<LINK REL="Next" HREF="001329.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-i18n] I18N svn access</H1>
<B>Michael scherer</B>
<A HREF="mailto:mageia-i18n%40mageia.org?Subject=Re%3A%20%5BMageia-i18n%5D%20I18N%20svn%20access&In-Reply-To=%3C20110425123643.GB21138%40sisay.ephaone.org%3E"
TITLE="[Mageia-i18n] I18N svn access">misc at zarb.org
</A><BR>
<I>Mon Apr 25 14:36:43 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="001344.html">[Mageia-i18n] I18N svn access
</A></li>
<LI>Next message: <A HREF="001329.html">[Mageia-i18n] team substitute leader wanted
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1367">[ date ]</a>
<a href="thread.html#1367">[ thread ]</a>
<a href="subject.html#1367">[ subject ]</a>
<a href="author.html#1367">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Fri, Apr 22, 2011 at 01:51:21AM +0200, Michael Scherer wrote:
><i> what if it doesn't work.
</I>><i> ------------------------
</I>><i>
</I>><i> If you have a message like this :
</I>><i> Can't open file '/svn/soft/db/txn-current-lock': Permission denied
</I>><i>
</I>><i> then you suffer from the problem I spoke at the beggining.
</I>><i> It is easy to check, when you do the test for the acces
</I>><i> when you do the check with ssh and the message do not say that you are
</I>><i> in mga-shell_access group, then you are suffering from the problem I
</I>><i> need to fix, and this will not work. If it say that you are in this
</I>><i> group, then this should work.
</I>
So, thanks to boklm and others, we narrowed the problem and while we didn't solved
it, we found a workaround good enough to let people commit.
So people can go ahead and send .po ( if all goes well ).
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001344.html">[Mageia-i18n] I18N svn access
</A></li>
<LI>Next message: <A HREF="001329.html">[Mageia-i18n] team substitute leader wanted
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1367">[ date ]</a>
<a href="thread.html#1367">[ thread ]</a>
<a href="subject.html#1367">[ subject ]</a>
<a href="author.html#1367">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-i18n">More information about the Mageia-i18n
mailing list</a><br>
</body></html>
|