Hello community,

here is the log from the commit of package criu for openSUSE:Factory checked in 
at 2017-11-14 12:58:52
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/criu (Old)
 and      /work/SRC/openSUSE:Factory/.criu.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "criu"

Tue Nov 14 12:58:52 2017 rev:38 rq:541321 version:3.6

Changes:
--------
--- /work/SRC/openSUSE:Factory/criu/criu.changes        2017-11-07 
10:05:24.274179863 +0100
+++ /work/SRC/openSUSE:Factory/.criu.new/criu.changes   2017-11-14 
12:59:00.663023971 +0100
@@ -1,0 +2,9 @@
+Sun Nov 12 01:05:43 UTC 2017 - [email protected]
+
+- add 0001-images.py-remove-shebang.patch
+  * fixes a lint warning about a non-executable python file being
+    executable due to a superfluous shebang
+  * upstream: https://lists.openvz.org/pipermail/criu/2017-November/039907.html
+- run spec-cleaner
+
+-------------------------------------------------------------------

New:
----
  0001-images.py-remove-shebang.patch

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

Other differences:
------------------
++++++ criu.spec ++++++
--- /var/tmp/diff_new_pack.0eQrFF/_old  2017-11-14 12:59:01.602989602 +0100
+++ /var/tmp/diff_new_pack.0eQrFF/_new  2017-11-14 12:59:01.602989602 +0100
@@ -25,21 +25,22 @@
 Url:            http://criu.org/
 Source0:        http://download.openvz.org/criu/%{name}-%{version}.tar.bz2
 Patch1:         criu-py-install-fix.diff
+# PATCH-FIX-UPSTREAM 0001-images.py-remove-shebang.patch 
https://lists.openvz.org/pipermail/criu/2017-November/039907.html
+Patch2:         0001-images.py-remove-shebang.patch
 BuildRequires:  asciidoc
-%if 0%{suse_version} > 1320
-BuildRequires:  libbsd-devel
-%endif
 BuildRequires:  libcap-devel
 BuildRequires:  libnet-devel
 BuildRequires:  libnl3-devel
-BuildRequires:  pkg-config
+BuildRequires:  pkgconfig
 BuildRequires:  protobuf-c
 BuildRequires:  protobuf-devel
 BuildRequires:  xmlto
 Requires:       python-ipaddr
 Requires:       python-protobuf
-BuildRoot:      %{_tmppath}/%{name}-%{version}-build
 ExclusiveArch:  x86_64 aarch64 ppc64le %{arm} s390x
+%if 0%{?suse_version} > 1320
+BuildRequires:  libbsd-devel
+%endif
 
 %description
 Checkpoint/Restore In Userspace, or CRIU, is a software tool for Linux
@@ -80,6 +81,7 @@
 %prep
 %setup -q
 %patch1 -p1
+%patch2 -p1
 # default off
 echo "BINFMT_MISC_VIRTUALIZED" > .config
 
@@ -101,34 +103,27 @@
 ln -s criu.8 %{buildroot}%{_mandir}/man8/crtools.8
 
 %post -n libcriu1 -p /sbin/ldconfig
-
 %postun -n libcriu1 -p /sbin/ldconfig
-
 %post -n libcompel1 -p /sbin/ldconfig
-
 %postun -n libcompel1 -p /sbin/ldconfig
 
 %files
-%defattr(-,root,root)
 %doc README.md COPYING
 %{_sbindir}/*
 %{_bindir}/*
 %{_mandir}/man*/*
 %{_libexecdir}/criu
 %{_libexecdir}/compel
-/usr/lib/python*/site-packages/crit-*.egg-info
-/usr/lib/python*/site-packages/pycriu
+%{_prefix}/lib/python*/site-packages/crit-*.egg-info
+%{_prefix}/lib/python*/site-packages/pycriu
 
 %files -n libcriu1
-%defattr(-,root,root)
 %{_libdir}/libcriu.so.*
 
 %files -n libcompel1
-%defattr(-,root,root)
 %{_libdir}/libcompel.so.*
 
 %files devel
-%defattr(-,root,root)
 %{_includedir}/criu
 %{_includedir}/compel
 %{_libdir}/libcriu.so

++++++ 0001-images.py-remove-shebang.patch ++++++
>From aee84030f4623c468faaa90b8fc0820e39f86bda Mon Sep 17 00:00:00 2001
From: Avindra Goolcharan <[email protected]>
Date: Sat, 4 Nov 2017 18:46:03 -0400
Subject: [PATCH] images.py: remove shebang

This file is not executable directly, so it should not have the shebang.
---
 lib/py/images/images.py | 2 --
 1 file changed, 2 deletions(-)

diff --git a/lib/py/images/images.py b/lib/py/images/images.py
index bb2f383..b706fd3 100644
--- a/lib/py/images/images.py
+++ b/lib/py/images/images.py
@@ -1,5 +1,3 @@
-#!/bin/env python2
-
 # This file contains methods to deal with criu images.
 #
 # According to http://criu.org/Images, criu images can be described
-- 
2.15.0
Signed-off-by: Avindra Goolcharan <[email protected]>

Reply via email to