Package: vmdb2
Version: 0.13.2+git20190215-1
Severity: normal
Tags: patch

(debbugs cc: Lars)

The documentation says `rootfs-unpacked`, but the variable is actually
called `rootfs_unpacked`.

Patch attached.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages vmdb2 depends on:
ii  cmdtest         0.32-3
ii  debootstrap     1.0.114
ii  kpartx          0.7.9-2
ii  parted          3.2-24
ii  python3         3.7.2-1
ii  python3-cliapp  1.20180812.1-2
ii  python3-jinja2  2.10-1
ii  python3-yaml    3.13-2
ii  qemu-utils      1:3.1+dfsg-4

Versions of packages vmdb2 recommends:
ii  ansible  2.7.6+dfsg-1

vmdb2 suggests no packages.

-- no debconf information
From ada2297a65e4c3a87ab6e956838bc434aaca9925 Mon Sep 17 00:00:00 2001
From: Antonio Terceiro <terce...@debian.org>
Date: Tue, 19 Feb 2019 15:25:28 -0300
Subject: [PATCH] Change: fix variable name for rootfs caching in documentation

This was renamed internally and the documentation wasn't updated.
---
 vmdb2.mdwn | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/vmdb2.mdwn b/vmdb2.mdwn
index 62326b1..de09c75 100644
--- a/vmdb2.mdwn
+++ b/vmdb2.mdwn
@@ -152,7 +152,7 @@ filesystem and stores it into the file as a compress tar archive
 skip running debootstrap needlessly.
 
 The specify which steps should be skipped, the `unless` field can be
-used: `unpack-rootfs` sets the `rootfs-unpacked` flag if it actually
+used: `unpack-rootfs` sets the `rootfs_unpacked` flag if it actually
 unpacks a tarball, and `unless` allows checking for that flag. If the
 tarball doesn't exist, the flag is not set.
 
@@ -160,10 +160,10 @@ tarball doesn't exist, the flag is not set.
 
     - debootstrap: stretch
       target: root
-      unless: rootfs-unpacked
+      unless: rootfs_unpacked
 
     - cache-rootfs: root
-      unless: rootfs-unpacked
+      unless: rootfs_unpacked
 
 If the tarball exists, it's unpacked, and the `debootstrap` and
 `cache-rootfs` steps are skipped.
-- 
2.20.1

Attachment: signature.asc
Description: PGP signature

Reply via email to