Arch Linux User Repository

Thanks for the heads up, fixed.

Looks like the source for btrfs-scrub@.timer has been updated: https://git.archlinux.org/svntogit/packages.git/commit/trunk/btrfs-scrub@.timer?h=packages/btrfs-progs&id=087f43d6119392c553e0eb41c9f491299d923c1b

New checksums are:

$ md5sum btrfs-scrub@.timer
40ac621390e93a934b9661adbcedf7a8  btrfs-scrub@.timer
$ sha1sum btrfs-scrub@.timer
f75f76ff1a760f6c710cf0d5ab1c52874fc5625c  btrfs-scrub@.timer

Yes, thanks for the heads-up. I reported it on the mailing list, but didn't have time to post here.

Just FYI, this problem has been fixed now: http://repo.or.cz/btrfs-progs-unstable/devel.git/commit/550b508129f26940790ddb82f00a5412b37e8741

Strange, I can reproduce this, but only outside of a clean chroot. I beleive that it is caused by this commit: http://repo.or.cz/btrfs-progs-unstable/devel.git?a=commit;h=ebe5b1cc7885027521db3c1d16d84bd54cc1321b

You should report it upstream. You could fix it by modifying the makefile in the prepare function, but I don't want to do this for a -git package.

Can't seem to build this:

===========================
/usr/bin/install -c -m644 -d 64-btrfs-dm.rules /home/myuser/aur/btrfs-progs-git/pkg/btrfs-progs-git/usr/lib/udev/rules.d
/usr/bin/install: cannot create directory ‘64-btrfs-dm.rules’: File exists
Makefile:400: recipe for target 'install' failed
make: *** [install] Error 1
==> ERROR: A failure occurred in package()
===========================

For a while now, this package has basically become a mirror of the btrfs-progs package in core/, and the integration branches have become what this used to be, albeit somewhat more experimental.

Unless anyone has any objections, I will change the PKGBUILD to pull in the btrfs-progs release candidates form the unstable repository. The latest of these is currently 3.15-rc3 [1], and lags behind integration-20140627 by about 50 commits.

This will mean that this package will potentially less stable (the hint was in the repository name), and may come as a shock to some users; especially since, historically, this package was recommended over core/ due to upstream stalling at v0.19/v0.20-rc1.

If you want to keep using stable btrfs-progs, I recommend that you use the package in core/.

Anyone who wants to test the new PKGBUILD before it goes live, can find it here: [2].

Cheers.

[1] http://repo.or.cz/w/btrfs-progs-unstable/devel.git/commit/2d4697d27501889823be71427ac06941b7508679
[2] https://github.com/WorMzy/PKGBUILDs/blob/332d8d59f443c2eb788e0b6eb4f1d8966aa9fd1a/btrfs-progs-git/PKGBUILD

I dropped the changelog from this package, it'd be too difficult to maintain it for an active git branch. Just use git log.

It appears he is. Anyone who wants/needs bleeding edge btrfs progs should switch to btrfs-progs-unstable-integration, people who want to play it safe should stick with this package. In either case, I recommend that you subscribe to the btrfs mailing list and use an up-to-date kernel (preferably mainline).

I have started generating changelogs and bundling them with the packages, so

pacman -Qc btrfs-progs-git | less -R

will give you a vague indication of what's changed recently (I include the last 50 commits). If you want more information, cd into your local copy of btrfs-progs and run 'git log'.

I've updated the PKGBUILD to include the check function I added to the unstable package. If the check fails, something went wrong. Check your RAM, etc., and rebuild, but don't install and use the failed package, you'll probably end up with a corrupted filesystem. If you think the checks are wrong, ask upstream first, I don't want anyone to lose data.

Incidentally, this package is now more current than the unstable package, so.. yeah. Use this one for now. I'm not sure if David will be carrying on with his integration snapshots now that Chris has updated master (I hope he will!), so stay tuned.