Hello community,

here is the log from the commit of package gobject-introspection for 
openSUSE:Factory checked in at 2013-08-19 13:31:21
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/gobject-introspection (Old)
 and      /work/SRC/openSUSE:Factory/.gobject-introspection.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "gobject-introspection"

Changes:
--------
--- 
/work/SRC/openSUSE:Factory/gobject-introspection/gobject-introspection.changes  
    2013-08-16 12:20:39.000000000 +0200
+++ 
/work/SRC/openSUSE:Factory/.gobject-introspection.new/gobject-introspection.changes
 2013-08-19 13:31:23.000000000 +0200
@@ -1,0 +2,7 @@
+Fri Aug 16 08:44:06 UTC 2013 - [email protected]
+
+- Enhance gi-find-deps.sh: when scannig python file for
+  gi.require_version, make sure to ignore python comments (starting
+  with #).
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ gi-find-deps.sh ++++++
--- /var/tmp/diff_new_pack.L5qX2H/_old  2013-08-19 13:31:24.000000000 +0200
+++ /var/tmp/diff_new_pack.L5qX2H/_new  2013-08-19 13:31:24.000000000 +0200
@@ -51,7 +51,7 @@
                # Temporarly disabled... this is not true if the python code is 
written for python3... And there seems no real 'way' to identify this.
                # echo "python-gobject >= 2.21.4"
        done
-       for module in $(grep -h -P -o 
"(gi\.require_version\(['\"][^'\"]+['\"],\s*['\"][^'\"]+['\"]\))" $1 | sed -e 
's:gi.require_version::' -e "s:[()\"' ]::g" -e 's:,:-:'); do
+       for module in $(grep -h -P -o 
".*(gi\.require_version\(['\"][^'\"]+['\"],\s*['\"][^'\"]+['\"]\))" $1 | sed  
-e 's:#.*::' -e 's:.*gi.require_version::' -e "s:[()\"' ]::g" -e 's:,:-:'); do
                split_name_version $module
                print_req_prov
        done

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to