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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Can't update to new apache package
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Can%27t%20update%20to%20new%20apache%20package&In-Reply-To=%3C50067FE2.2010302%40gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="017439.html">
<LINK REL="Next" HREF="017444.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Can't update to new apache package</H1>
<B>Guillaume Rousse</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Can%27t%20update%20to%20new%20apache%20package&In-Reply-To=%3C50067FE2.2010302%40gmail.com%3E"
TITLE="[Mageia-dev] Can't update to new apache package">guillomovitch at gmail.com
</A><BR>
<I>Wed Jul 18 11:20:34 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="017439.html">[Mageia-dev] Can't update to new apache package
</A></li>
<LI>Next message: <A HREF="017444.html">[Mageia-dev] Can't update to new apache package
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#17440">[ date ]</a>
<a href="thread.html#17440">[ thread ]</a>
<a href="subject.html#17440">[ subject ]</a>
<a href="author.html#17440">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 18/07/2012 11:07, Oliver Burger a écrit :
><i> Am 18.07.2012 10:58, schrieb Guillaume Rousse:
</I>>><i> Installing from scratch will trigger the failure, I forgot to make the
</I>>><i> script specific to upgrade scenario only. However, it's unclear why it
</I>>><i> fails when upgrading from a previous installation (for you), where
</I>>><i> /etc/httpd/conf directory exist, but not /etc/httpd/conf/sites.d:
</I>>><i>
</I>>><i> # prevent symlink creation failure on update
</I>>><i> if [ ! -d /etc/httpd/conf/sites.d ]; then
</I>>><i> mkdir /etc/httpd/conf/sites.d
</I>>><i> mv -f /etc/httpd/conf/webapps.d/* /etc/httpd/conf/sites.d 2>/dev/null
</I>>><i> mv -f /etc/httpd/conf/vhosts.d/* /etc/httpd/conf/sites.d 2>/dev/null
</I>>><i> rmdir /etc/httpd/conf/webapps.d
</I>>><i> rmdir /etc/httpd/conf/vhosts.d
</I>>><i> fi
</I>>><i>
</I>>><i> I guess it has something to do with exact package ordering during
</I>>><i> uninstallation transaction. In the past we had %pretrans trigger, I'm
</I>>><i> not sure it is still available.
</I>>><i>
</I>><i> Another short question while we are on it.
</I>><i> This does mean we have to change the web application packages (like
</I>><i> drupal, mediawiki,...) who have files in /etc/httpd/conf/webapps.d/,
</I>><i> doesn't it?
</I>Just rebuilding should be enough, once the %webappconfdir macro get
updated in rpm-mageia-setup.
BTW, there is no emergency here, given than /etc/httpd/conf/webapps.d
still exist as a symlink to /etc/httpd/conf/site.d
--
BOFH excuse #347:
The rubber band broke
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="017439.html">[Mageia-dev] Can't update to new apache package
</A></li>
<LI>Next message: <A HREF="017444.html">[Mageia-dev] Can't update to new apache package
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#17440">[ date ]</a>
<a href="thread.html#17440">[ thread ]</a>
<a href="subject.html#17440">[ subject ]</a>
<a href="author.html#17440">[ 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>
|
