summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-February/012354.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-February/012354.html')
-rw-r--r--zarb-ml/mageia-dev/2012-February/012354.html108
1 files changed, 108 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-February/012354.html b/zarb-ml/mageia-dev/2012-February/012354.html
new file mode 100644
index 000000000..f0c94328d
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-February/012354.html
@@ -0,0 +1,108 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Build system broken
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Build%20system%20broken&In-Reply-To=%3Cjida41%24t27%241%40dough.gmane.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="012344.html">
+ <LINK REL="Next" HREF="012355.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Build system broken</H1>
+ <B>David Walser</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Build%20system%20broken&In-Reply-To=%3Cjida41%24t27%241%40dough.gmane.org%3E"
+ TITLE="[Mageia-dev] Build system broken">luigiwalser at yahoo.com
+ </A><BR>
+ <I>Sun Feb 26 13:55:28 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="012344.html">[Mageia-dev] Build system broken
+</A></li>
+ <LI>Next message: <A HREF="012355.html">[Mageia-dev] Build system broken
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#12354">[ date ]</a>
+ <a href="thread.html#12354">[ thread ]</a>
+ <a href="subject.html#12354">[ subject ]</a>
+ <a href="author.html#12354">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>David Walser wrote:
+&gt;<i> For some reason, the build system is trying to install libnss3 into every chroot. I don't know why. It is also trying to install the
+</I>current
+&gt;<i> version in Cauldron, rather than a known good version.
+</I>&gt;<i>
+</I>&gt;<i> The issue was introduced when nspr was updated to version 4.9, because the package provides version 4.9, but the pkg-config file says 4.9.0
+</I>is
+&gt;<i> the version.
+</I>&gt;<i>
+</I>&gt;<i> The breakage happened when updating the nss package, and it has a macro in it that generates the version of libnspr4 it requires from the
+</I>pkg-
+&gt;<i> config file in nspr. So basically, we have libnspr4-4.9, but libnss3 is requiring libnspr4-4.9.0 and doesn't think it exists.
+</I>&gt;<i>
+</I>&gt;<i> I committed a change in svn for nspr that I believe will fix this, but nspr needs to be able to be rebuilt, so that nss can be rebuilt
+</I>against
+&gt;<i> it. For anything to be built, the build system needs to either stop trying to install libnss3, or it needs to install the previous version
+</I>of
+&gt;<i> the package.
+</I>
+Thank you to D Morgan for fixing it. I apologize for making sure that nss not only built, but also installed correctly before uploading it.
+
+This got me to thinking, however, that something like this should not have broken the build system. There's no reason for iurt to be setting
+up the chroot with packages from Cauldron, unless they are part of the BuildRequires (including recursively) for the package being built. In
+this situation, once a package needed in the base of the chroot is broken, there is no way to fix it without sysadmin intervention. This
+would be true for a broken package in Cauldron, or stable/updates_testing.
+
+I believe a better way for iurt to work would be this. It would set up the initial chroot from the newest stable release of Mageia that is
+the same version of Mageia the package is being built for, or older. So right now, that would mean Mageia 1 in all cases. Once Mageia 2 is
+out, it would mean Mageia 2 for packages being built for 2 or Cauldron, and Mageia 1 for packages being built for 1. Also, when the initial
+chroot was being installed, release and updates would be enabled only. Then, when it gets to the BuildRequires stage, first enable either
+updates_testing if it's being built for a stable relase, or Cauldron if it's being built for that, and then install the BuildRequires and
+build the package.
+
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="012344.html">[Mageia-dev] Build system broken
+</A></li>
+ <LI>Next message: <A HREF="012355.html">[Mageia-dev] Build system broken
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#12354">[ date ]</a>
+ <a href="thread.html#12354">[ thread ]</a>
+ <a href="subject.html#12354">[ subject ]</a>
+ <a href="author.html#12354">[ 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>