Package Details: btrfs-progs-git 6994_6.7.1_r0_g60abf7a9-1

Git Clone URL: https://aur.archlinux.org/btrfs-progs-git.git (read-only, click to copy)
Package Base: btrfs-progs-git
Description: Btrfs filesystem utilities
Upstream URL: https://btrfs.wiki.kernel.org/index.php/Main_Page
Licenses: GPL-2.0-only
Conflicts: btrfs-progs
Provides: btrfs-progs
Submitter: None
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 62
Popularity: 0.000038
First Submitted: 2008-12-27 21:29 (UTC)
Last Updated: 2024-03-03 12:09 (UTC)

Required by (101)

Sources (5)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

WorMzy commented on 2013-11-26 21:07 (UTC)

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

WorMzy commented on 2013-11-13 21:17 (UTC)

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'.

WorMzy commented on 2013-11-12 00:36 (UTC)

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.

WorMzy commented on 2013-09-09 17:36 (UTC)

I've still not had chance to test that the hooks work, so use them at your own risk. This pkgver bump was more to add btrfs-select-super, which WonderWoofy pointed out needs to be explicitly built and installed manually. If there are any other tools that can be built but aren't by default, and you think would be useful, please let me know.

WorMzy commented on 2013-09-06 01:25 (UTC)

Just an FYI: I updated the PKGBUILD with the mkinitcpio hook a week or so ago, but I've not had chance to test it yet. Anyone interested in testing it can download it from here: https://raw.github.com/WorMzy/PKGBUILDs/master/btrfs-progs-git/PKGBUILD

WonderWoofy commented on 2013-08-22 03:01 (UTC)

These days, having udev or systemd in your initramfs is IMO a no brainer. But I also know that there are people out there who vehemently oppose perceived over-complication. Personally I wouldn't get use out of it, but I just noticed that it was something that the Arch package included, but this one doesn't. Considering that this package is much more useful to a true btrfs user than the Tom Gunderson's in [core], I just thought it might be a nice thing to include. Tom has recently inquired on the btrfs-devel list about having some kind of a "release" structure, so that it would be more clear about when his package should be updated. Apparently, the last real release was v19 and that was a few years ago. Sometimes, updates of the featureset in the kernel require a "matching" btrfs-progs to make use of the features. For example, I use send/receive, yet last I checked, this was not included in the Arch package. I think too that skinny extents cannot be enabled by the btrfs-progs package either.

WorMzy commented on 2013-08-20 15:46 (UTC)

Some one else asked about it back in May. I can add it if you think it will be useful, but I don't use it, so I can't guarantee it will always work.

WonderWoofy commented on 2013-08-18 00:34 (UTC)

WorMzy, I don't actually use them, but the official package includes a 'btrfs' mkinitpcio hook, which is intended to be used with initramfs' w/o udev (for multi device btrfs filesystems). Have you ever thought to add those to your package? I just got really confused the other day when a friend was asking about whether nor not to use it. I was going to copy/paste the output of 'mkinitpcio -H btrfs' to him, but it wasn't there. It took me a minute or so to realize that it was because the hook was provided by the btrfs-progs package.

WorMzy commented on 2013-06-12 15:46 (UTC)

Seems like a reasonable addition, and I note that the same thing is implemented in the official PKGBUILD. Done. :)

aya commented on 2013-06-04 16:00 (UTC)

oops. rebooted and ${pkgname/-git} worked for me as well. It really should have. sorry. Maybe take into account $CFLAGS? make CFLAGS="$CFLAGS" all btrfs-zero-log

« First ‹ Previous 1 2 3 4 5 6 Next › Last »