[Piuparts-devel] Bug#633033: piuparts: libeatmydata alternative

Scott Schaefer saschaefer at neurodiverse.org
Thu Jul 7 22:31:59 UTC 2011

Package: piuparts
Version: 0.40
Severity: wishlist
Tags: patch

Attached patch addresses TODO item re libeatmydata ..

"- use libeatmydata - either install it in all chroots or find a
better way to use it."

With Squeeze release, the version of dpkg in stable has had an option
"--force-unsafe-io" which, while it certainly does not disable ALL
fsync() calls, does disable some of them (sorry, that is extent of
my knowledge).

So, while installing libeatmydata into chroot would be superior,
the attached patch provides for running dpkg with the ”force-unsafe-io”
option (whether directly or via apt) in the chroot.

I added a command-line option to allow the user to DISABLE
this behavior; i.e. the default is to use force-unsafe-io. If
the user specifies "--dpkg-noforce-unsafe-io" on piuparts
command line, dpkg runs as normal (safe, but slower).

Hopefully, the text of the option in piuparts --help, and in man
page is clear.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: dpkg_unsafe_io.patch
Type: text/x-patch
Size: 3619 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20110707/a3a382bd/attachment.bin>

More information about the Piuparts-devel mailing list