pck-update: add a warning message when a requirement is ignored

Signed-off-by: Davide Madrisan <davide.madrisan@gmail.com>

ChangeLog

@@ -69,11 +69,21 @@ Changes in version 1.12.6
     function is not the expected one (that is a string made by the current 
     date in the format YYYYMMDD followed by "git").
 
++ bugfix
   * pck-update - Silvan Calarco:
     Try to avoid reporting package requirements set with 'Requires:' as build
     requirements. Unless not better identified requirements are in 'a(b)' form
     don't report them as build requirements to avoid breaking stage1 builds and
     causing unneeded circular dependencies.
+    (patch by Silvan Calarco)
+
++ improvement
+  * pck-update - Davide Madrisan:
+    Add a warning message when a requirement is ignored.
+
++ update
+  * po/it/pck-update.po - Davide Madrisan:
+    Updated.
 
 -------------------------------------------------------------------------------
 

plugins/pck-update.in

@@ -2252,7 +2252,7 @@ $(echo $solibpath | sed "s|-[0-9.]*\.so|.so|")"
             else
                # other requirements probably coming from static 'Requires:'
                # so don't treat them as build requirements
-               :
+               notify.warning $"ignoring requirement: \`${NOTE}$req${NORM}'"
             fi
             if [ -n "$buildreq" \
                  -a "${buildreq/%-devel/}" = "$buildreq" ]; then

po/it/pck-update.po

@@ -468,6 +468,9 @@ msgstr "release del nuovo pacchetto non indicata"
 msgid "package not found"
 msgstr "pacchetto non trovato"
 
+msgid "ignoring requirement"
+msgstr "requirement ignorato"
+
 msgid "rpm exited with error code:"
 msgstr "rpm è terminato con il codice di errore:"