Log message:
Bump all packages for perl-5.18, that
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package

Like last time, where this caused no complaints.

Log message:
Edited DESCR in the case of:
 File too long (should be no more than 24 lines).
 Line too long (should be no more than 80 characters).
 Trailing empty lines.
 Trailing white-space.
Trucated the long files as best as possible while preserving the most info
contained in them.

Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Log message:
Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.

Log message:
Update to 0.25rc1. Add py-readline dependency for better 'bup ftp' support.

This is the latest stable release, despite its name. Lots of bug fixes
compared to previous one, but no NEWS provided.

Log message:
Bump PKGREVISION from default python to 2.7.

Log message:
Depend on fuse bindings.

Now, "bup fuse dir", assuming ~/.bup is one's bup repository, will
create a fuse mount on dir, in which one can see the backups (with
lots of rought edges).

Log message:
Reset maintainer.

Log message:
Install README and design document. Bump PKGREVISION.

Log message:
Initial import of bup-0.24b.

bup is a program that backs things up.  bup has a few advantages
over other backup software:

It uses a rolling checksum algorithm (similar to rsync) to split
large files into chunks. The most useful result of this is you can
backup huge virtual machine (VM) disk images, databases, and XML
files incrementally, even though they're typically all in one huge
file, and not use tons of disk space for multiple versions.

It uses the packfile format from git (the open source version
control system), so you can access the stored data even if you
don't like bup's user interface.

Unlike git, it writes packfiles directly (instead of having a
separate garbage collection / repacking stage) so it's fast even
with gratuitously huge amounts of data. bup's improved index formats
also allow you to track far more filenames than git (millions) and
keep track of far more objects (hundreds or thousands of gigabytes).

Data is "automagically" shared between incremental backups without
having to know which backup is based on which other one - even if
the backups are made from two different computers that don't even
know about each other. You just tell bup to back stuff up, and it
saves only the minimum amount of data needed.

You can back up directly to a remote bup server, without needing
tons of temporary disk space on the computer being backed up.  And
if your backup is interrupted halfway through, the next run will
pick up where you left off. And it's easy to set up a bup server:
just install bup on any machine where you have ssh access.

Bup can use "par2" redundancy to recover corrupted backups even if
your disk has undetected bad sectors.

Even when a backup is incremental, you don't have to worry about
restoring the full backup, then each of the incrementals in turn;
an incremental backup acts as if it's a full backup, it just takes
less disk space.

You can mount your bup repository as a FUSE filesystem and access
the content that way, and even export it over Samba.