Comments

25 Comments
karma

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1445302 and doesn't seem to otherwise cause any unwanted/unexpected changes in behavior.

BZ#1445302 partition on a FW RAID used as a PV is put into a list of filtered devices by blivet

Makes the DNF module work with rawhide hosts, thanks!

BZ#1387621 dnf module doesn't work with a rawhide host
karma

Works just fine and fixes the issue with the new DBus service not automatically starting up.

karma

Fixes the bug #1325851 for me and seems to be working fine.

BZ#1325851 [abrt] storaged: __strstr_sse2_unaligned(): storaged killed by SIGSEGV

How to test:

1) install the libblockdev-lvm-dbus package

2) run ipython as root

3) make sure the lvm2-lvmdbusd.service is stopped

4) run from gi.repository import BlockDev; BlockDev.init()

5) run BlockDev.get_plugin_soname(BlockDev.Plugin.LVM)

6) check that the result is 'libbd_lvm-dbus.so.0'

7) check that the lvm2-lvmdbusd service is now running

The new build should also add the init.py file(s) to python (2 and 3) bindings.

An easy way to test the change is:

$ LANG=cs_CZ.UTF-8 ipython3
In [1]: from bytesize.bytesize import Size
In [2]: s = Size("1.5 KiB")
In [3]: s.convert_to("KiB")
Out[3]: Decimal('1.5')

Previously this would result in a traceback.

The update can be easily tested on a system with LVM, by running:

from gi.repository import BlockDev; BlockDev.init()
BlockDev.lvm.vgreduce("SOME_VG_NAME", None)

which tries to remove the missing PVs from the VG (there should be none). Previously this resulted in an error, now it should just be a no-op.

karma

Fixes the bug #1285661 and seems to be working great. Thanks!

BZ#1285661 aws-devel should require openldap-devel
karma

Everything seems to be working great and the new functionality of the 'lvs' command is in place and working.

BZ#1264190 Enhancement: lvs, add uuid columns for associated PVs and LVs

The new upstream release for example adds support for bool(Size("10 GiB")) as well as abs(Size("-10 GiB")) which are easy to test using (i)python(3).

The new upstream release for example adds support for bool(Size("10 GiB")) as well as abs(Size("-10 GiB")) which are easy to test using (i)python(3).

karma

forgot to set karma

Fixes bug #1229186 (which is not referenced by this update, btw) for me.

A testing run with 'strace' looks like it does things in the right order now. Thanks!

BZ#1255175 useradd -R reads /etc/login.defs from outside of the chroot
karma

Doesn't work for me. Simple testing results with a traceback: $ python -c 'import cpioarchive; archive = cpioarchive.CpioArchive("python3-cpio.cpio"); print([entry.name for entry in archive])' ['./usr/lib/python3.4/site-packages/cpioarchive.py', './usr/lib/python3.4/site-packages/python_cpio-0.1-py3.4.egg-info', './usr/share/doc/python3-cpio', './usr/share/doc/python3-cpio/AUTHORS', './usr/share/doc/python3-cpio/ChangeLog', './usr/share/doc/python3-cpio/README', './usr/share/doc/python3-cpio/TODO', './usr/share/licenses/python3-cpio', './usr/share/licenses/python3-cpio/COPYING.lib', './usr/lib/python3.4/site-packages/pycache/cpioarchive.cpython-34.pyc', './usr/lib/python3.4/site-packages/pycache/cpioarchive.cpython-34.pyo'] [vpodzime@localhost ~]$ python3 -c 'import cpioarchive; archive = cpioarchive.CpioArchive("python3-cpio.cpio"); print([entry.name for entry in archive])' Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib/python3.4/site-packages/cpioarchive.py", line 125, in init self._readfile(name) File "/usr/lib/python3.4/site-packages/cpioarchive.py", line 162, in _readfile self._readobj(open(name, 'rb')) File "/usr/lib/python3.4/site-packages/cpioarchive.py", line 172, in _readobj ce=CpioEntry(text, self, istart) File "/usr/lib/python3.4/site-packages/cpioarchive.py", line 29, in init if not hdr.startswith('070701'): TypeError: startswith first arg must be bytes or a tuple of bytes, not str

fixes the issue with cached LV (de)activation

fixes the issue with (de)activation of a cached LV

works for me

I can confirm that the new version of the package fixes the issue reported in the bug #1190847