| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
0.7.10 will not be committed due to a regression:
https://github.com/zfsonlinux/zfs/issues/7906
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
| |
Bug: https://bugs.gentoo.org/590992
|
|
|
|
| |
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/662228
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.43, Repoman-2.3.10
|
|
|
|
| |
Package-Manager: Portage-2.3.41, Repoman-2.3.9
|
|
|
|
|
| |
Acked-by: Richard Yao <ryao@gentoo.org>
Package-Manager: Portage-2.3.40, Repoman-2.3.9
|
|
|
|
|
|
|
|
| |
Also, this blocker was never correct in the first place because
CONFIG_REISER4_FS became CONFIG_CONFIG_REISER4_FS. I am also fixing the
blocker in zfs-kmod-0.6.5.11.ebuild, which still needs it.
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
|
|
| |
Merging the SPL into the upstream repository required changes to the
ebuild.
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.36, Repoman-2.3.9
|
|
|
|
|
|
| |
masks.
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/651866
Package-Manager: Portage-2.3.27, Repoman-2.3.9
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.21, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.14, Repoman-2.3.6
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.12, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.12, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.12, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.11, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
Reported-by: Justin Lecher <jlec@gentoo.org>
Signed-off-by: Richard Yao <ryao@gentoo.org>
|
|
|
|
| |
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
|
|
| |
- Bumped to ZFS on Linux 0.6.5.9
- Added additional maintainer: fearedbliss
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
|
|
|
|
| |
We are abandoning the /dev/zfs API stabilization effort in Gentoo until
it is merged by upstream because stronger QA tests are causing it to
hold us back.
Signed-off-by: Richard Yao <ryao@gentoo.org>
|
|
|
|
|
|
|
|
| |
up to kernel 4.8 compatibility, acked by maintainer
Gentoo-Bug: 594360
Package-Manager: portage-2.3.1
|
|
|
|
|
|
|
|
| |
still unkeyworded, acked by maintainer
Gentoo-Bug: 586434
Package-Manager: portage-2.3.0_rc1
|
|
|
|
| |
Closes: https://github.com/gentoo/gentoo/pull/1382
|
|
|
|
|
|
|
|
| |
The updated patchset has been delayed due to some matters that I am in
the process of resolving. I am committing the 0.6.5.6 ebuilds without
keywords for the people who want it sooner.
Signed-off-by: Richard Yao <ryao@gentoo.org>
|
|
|
|
|
|
|
|
|
|
| |
The requirement that PAX_USERCOPY_SLABS be disabled has been fixed in master
for many releases now.
They are correct in the latest release ebuild but the live ebuild was
out of sync.
Package-Manager: portage-2.2.26
|
|
|
|
|
|
|
|
|
|
|
| |
The stable API patches from the 0.6.5.3-r4 ebuild and fix for the
temporary pool names have been carried forward in 0.6.5.4-r1. 0.6.5.4
has been commited without any patches as an aid to users who do not want
patches. However, it is left unkeyworded to ensure the upgrade path is
smooth.
Package-Manager: portage-2.2.24
Signed-off-by: Richard Yao <ryao@gentoo.org>
|
|
|
|
|
|
|
| |
Fixes additional regressions in the code from the proposed stable API branch.
Package-Manager: portage-2.2.24
Signed-off-by: Richard Yao <ryao@gentoo.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Fixes regressions in the code from the proposed stable API branch and an old
regression that caused `zpool create -m none -t ...` to fail to set the
mountpoint and certain other properties. That only occurred when the ZFSOnLinux
specific -t argument is set.
Package-Manager: portage-2.2.24
Signed-off-by: Richard Yao <ryao@gentoo.org>
|
|
|
|
|
|
|
| |
Fixes have been backported from both HEAD and the proposed stable API branch.
Package-Manager: portage-2.2.24
Signed-off-by: Richard Yao <ryao@gentoo.org>
|
|
|
|
|
| |
Package-Manager: portage-2.2.20.1
Signed-off-by: Richard Yao <ryao@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This backports various fixes and also implements the partial /dev/zfs
stable API that I have developed at ClusterHQ over the past 14 months.
Ordinarily, I would not commit something like this until it has gone
upstream, but upstream wants review from people in the Illumos project
that prefer to see things like this in production before it reaches them
and it would have likely been deadlocked until I volunteered Gentoo.
I am confident that this is ready for production and I believe Gentoo
benefits from it enough to justify being the first production user.
Unless the API changes under review, situations where the kernel modules
and userland bits fall out of sync will no longer break the boot process
(excluding zfs-share and zfs-zed). This was the longstanding blocker to
the ebuilds moving from ~arch to arch, so we could finally see that
happen around later this month / early next month.
Package-Manager: portage-2.2.20.1
Signed-off-by: Richard Yao <ryao@gentoo.org>
|
|
|
|
|
|
| |
Upstream no longer depends on this.
Package-Manager: portage-2.2.20.1
|
|
|
|
| |
Package-Manager: portage-2.2.20.1
|