New pre-release

.gitignore

@@ -1 +1,2 @@
 /boom-0.9.tar.gz
+/boom-6ff3e08.tar.gz

boom-boot.spec

@@ -1,14 +1,17 @@
 %global summary A set of libraries and tools for managing boot loader entries
 %global sphinx_docs 1
 
+%global commit 6ff3e0869b9818f4cc477e5771bc9e72352e7737
+%global shortcommit %(c=%{commit}; echo ${c:0:7})
+
 Name:		boom-boot
-Version:	0.9
-Release:	5%{?dist}
+Version:	1.0
+Release:	0.1.20190329git%{shortcommit}%{?dist}
 Summary:	%{summary}
 
 License:	GPLv2
 URL:		https://github.com/bmr-cymru/boom
-Source0:	https://github.com/bmr-cymru/boom/archive/%{version}/boom-%{version}.tar.gz
+Source0:	https://github.com/bmr-cymru/boom/archive/%{commit}/boom-%{shortcommit}.tar.gz
 
 BuildArch:	noarch
 
@@ -79,7 +82,7 @@ include this support in both Red Hat Enterprise Linux 7 and Fedora).
 This package provides integration scripts for grub2 bootloader.
 
 %prep
-%setup -q -n boom-%{version}
+%setup -q -n boom-%{commit}
 # NOTE: Do not use backup extension - MANIFEST.in is picking them
 
 %build
@@ -139,6 +142,7 @@ rm doc/conf.py
 %dir /boot/boom
 %config(noreplace) /boot/boom/boom.conf
 %dir /boot/boom/profiles
+%dir /boot/boom/hosts
 %dir /boot/loader/entries
 
 %files grub2
@@ -149,6 +153,9 @@ rm doc/conf.py
 
 
 %changelog
+* Thu May 09 2019 Marian Csontos <mcsontos@redhat.com> 1.0-0.1.20190329git6ff3e08
+- Pre-release of new version.
+
 * Thu Jan 31 2019 Fedora Release Engineering <releng@fedoraproject.org> - 0.9-5
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
 

sources

@@ -1 +1 @@
-SHA512 (boom-0.9.tar.gz) = 6991d2546b5a5b996450aa9fa570257d7a00d93a7598f25a0815ad0d0306172e9e826ada81ed86222f0ad616aa9318465651d697d123dbc70a184bfdcc762386
+SHA512 (boom-6ff3e08.tar.gz) = 1500028ad0896240f0d17a605201d16e20b7829eae7d35aa68a862ebdf10ec75ed61f558903ee9b5b060bfc8ba741d225d1c3ae9667a5bc1829f7fca470bfcd7

tests/tests.yml

@@ -0,0 +1,54 @@
+---
+- hosts: localhost
+  roles:
+  - role: standard-test-source
+    tags:
+    - classic
+  - role: standard-test-basic
+    tags:
+    - classic
+    tests:
+    - testsuite_pre:
+        dir: .
+        # boom test suite requires LV to exist on the system. We create one in case there is not one...
+        # boom requires /boot/boom/hosts directory to exist on the host. Is this a bug or feature?
+        run: |
+          set -xv;
+          rm -rf testsuite &>/dev/null;
+          mkdir -p /boot/boom/hosts;
+          if [[ ! -b /dev/boomvg/root ]]; then dd if=/dev/zero of=/dev/shm/boompv bs=1M count=128 && PV=$(losetup --show -f /dev/shm/boompv) && vgcreate boomvg $PV && lvcreate -n root -L32M boomvg; fi
+    - testsuite:
+        # to run the testsuite against installed python modules, we should run
+        # outside of source directory. Let's copy tests into new directory...
+        dir: .
+        run: |
+          set -xv;
+          mkdir testsuite && cd testsuite && cp -R ../source/tests . && python3 -m unittest -v tests/[a-z]*.py
+    - cli:
+        dir: .
+        run: |
+          (
+          set -xve;
+
+          boom profile list;
+          boom profile create --name test --short-name test --os-version rhel8 --os-version-id rhel8 --uname-pattern el8;
+          boom profile list;
+          boom entry list;
+
+          PROFILE=$(boom profile list --name test --no-headings -o osid);
+          boom entry create --root-lv boomvg/root --title test --profile $PROFILE;
+          boom entry list;
+
+          boom entry delete --title test;
+
+          boom profile delete --name test;
+          )
+    - testsuite_post:
+        dir: .
+        run: |
+          set -xv;
+          vgremove -ff boomvg; losetup -D; rm -f /dev/shm/boompv
+    required_packages:
+    - boom-boot
+    - boom-boot-grub2
+    - lvm2