<!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 &#233;crit :
&gt;<i> Am 18.07.2012 10:58, schrieb Guillaume Rousse:
</I>&gt;&gt;<i> Installing from scratch will trigger the failure, I forgot to make the
</I>&gt;&gt;<i> script specific to upgrade scenario only. However, it's unclear why it
</I>&gt;&gt;<i> fails when upgrading from a previous installation (for you), where
</I>&gt;&gt;<i> /etc/httpd/conf directory exist, but not /etc/httpd/conf/sites.d:
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> # prevent symlink creation failure on update
</I>&gt;&gt;<i> if [ ! -d /etc/httpd/conf/sites.d ]; then
</I>&gt;&gt;<i> mkdir /etc/httpd/conf/sites.d
</I>&gt;&gt;<i> mv -f /etc/httpd/conf/webapps.d/* /etc/httpd/conf/sites.d 2&gt;/dev/null
</I>&gt;&gt;<i> mv -f /etc/httpd/conf/vhosts.d/* /etc/httpd/conf/sites.d 2&gt;/dev/null
</I>&gt;&gt;<i> rmdir /etc/httpd/conf/webapps.d
</I>&gt;&gt;<i> rmdir /etc/httpd/conf/vhosts.d
</I>&gt;&gt;<i> fi
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> I guess it has something to do with exact package ordering during
</I>&gt;&gt;<i> uninstallation transaction. In the past we had %pretrans trigger, I'm
</I>&gt;&gt;<i> not sure it is still available.
</I>&gt;&gt;<i>
</I>&gt;<i> Another short question while we are on it.
</I>&gt;<i> This does mean we have to change the web application packages (like
</I>&gt;<i> drupal, mediawiki,...) who have files in /etc/httpd/conf/webapps.d/,
</I>&gt;<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>