btrfsmaintenance 0.5-4 source package in Ubuntu

Changelog

btrfsmaintenance (0.5-4) unstable; urgency=medium

  * Acknowledge buggy NMU.  Debian/NEWS refers to changelog entry 0.4-1~exp1,
    which was removed by the "rebuild with debhelper 13.10".  The purpose of
    this NMU appears to have been to unilaterally push changelog trimming.
  * Drop NEWS, and recommend against periodic balancing in README.Debian.
  * Import 0003-btrfsmaintenance-refresh-cron.sh-reset-OnCalendar-fo.patch
    from upstream (Closes: #1027846).  Thanks to Andrew Bezella for reporting
    this bug as well as testing the fix.
  * Add 0004-disable-periodic-balance-by-default.patch.
  * Update my copyright years.
  * Declare Standards-Version: 4.6.2. (No additional changes needed)
  * Update lintian override for "spare-manual-page".

 -- Nicholas D Steeves <email address hidden>  Thu, 02 Mar 2023 20:11:16 -0500

Upload details

Uploaded by:
Nicholas D Steeves
Uploaded to:
Sid
Original maintainer:
Nicholas D Steeves
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Lunar release universe misc

Builds

Lunar: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
btrfsmaintenance_0.5-4.dsc 1.9 KiB 38756b95f65080734a5fb15035f8fd8d4610864b81906930276148520f4c4e58
btrfsmaintenance_0.5.orig.tar.xz 21.9 KiB 58b2e38a28ebf438b9dc546272205296e6dbde83cce091ae87849498969d629d
btrfsmaintenance_0.5-4.debian.tar.xz 9.9 KiB 3f8586f746be322c1b9bfc686a59112c2ce392dc276b6f714528c51509857218

Available diffs

No changes file available.

Binary packages built by this source

btrfsmaintenance: automate btrfs maintenance tasks on mountpoints or directories

 This is a set of scripts for the btrfs filesystem that automates the
 following maintenance tasks: scrub, balance, trim, and defragment.
 .
 Tasks are enabled, disabled, scheduled, and customised from a single text
 file. The default configuration assumes an installation profile where '/'
 is a btrfs filesystem.
 .
 The default values have been chosen as an even compromise between time to
 complete maintenance, improvement in filesystem performance, and
 minimisation of resources taken from other processes. Please note that I/O
 priority scheduling requires the use of BFQ or CFQ, and not noop, deadline,
 anticipatory, nor the new mq-deadline which uses blk-mq.