From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-December/021049.html | 86 ++++++++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-December/021049.html (limited to 'zarb-ml/mageia-dev/2012-December/021049.html') diff --git a/zarb-ml/mageia-dev/2012-December/021049.html b/zarb-ml/mageia-dev/2012-December/021049.html new file mode 100644 index 000000000..a15c2c2e3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-December/021049.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] how to update mageia rpmlint configuration on submission host ? + + + + + + + + + +

[Mageia-dev] how to update mageia rpmlint configuration on submission host ?

+ Thomas Backlund + tmb at mageia.org +
+ Mon Dec 31 19:39:16 CET 2012 +

+
+ +
Thomas Backlund skrev 31.12.2012 17:09:
+> Guillaume Rousse skrev 31.12.2012 16:24:
+>> I can't suceed submitting metasploit, because of some rpmlint error:
+>>
+>> Submission errors, aborting:
+>> - metasploit-4.5-1.mga3:
+>>   - unexpanded-macro
+>> /usr/share/metasploit/lib/gemcache/ruby/1.9.1/gems/railties-3.2.8/lib/rails/generators/rails/plugin_new/templates/lib/%name%/engine.rb
+>>
+>> %name
+>>
+>> I did update rpmlint-mageia-policy a week ago (0.2.25), but the
+>> configuration used on the host running the check seems to still use the
+>> previous version. Do we need an explicit actions from sysadmins here ?
+>
+> Yep.
+>
+> I'll check it out tonight unless any other sysadmin beats me to it....
+
+New rpmlint and policy now in place.
+
+Also -debuginfo packages should now be ok and the changes for /run,
+and checking for udev, systemd and tmpfiles location are now in effect
+
+
+--
+Thomas
+
+
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1