Announcing: ZFS-fuse 0.7.0
#66 — git tag 0.6.9 and zfs-fuse-0.6.9.tar.bz2 have different source
| State | Resolved |
|---|---|
| Version: | 0.6.9 |
| Area | Process |
| Issue type | Bug |
| Severity | Medium |
| Submitted by | Russ Gibson |
| Submitted on | Jun 22, 2010 |
| Responsible | Seth Heeren |
| Target release: | 0.6.9 |
Last modified on
Jun 22, 2010
by
Seth Heeren
The files:
src/zfs-fuse/util.c
src/zfs-fuse/zfs_operations.c
are _slightly_ different in the official git repo than they are in the downloaded source. On archlinux x64, using gcc 4.5.0, the git version fails to build, but the downloadable source version does.
I was able to build with the zfs-fuse-git-critical package from AUR by using 'makepkg -o' (download/extract source), then copying those two files from the original archive over the top of the git versions, then using 'makepkg -e' (build package using existing source).
src/zfs-fuse/util.c
src/zfs-fuse/zfs_operations.c
are _slightly_ different in the official git repo than they are in the downloaded source. On archlinux x64, using gcc 4.5.0, the git version fails to build, but the downloadable source version does.
I was able to build with the zfs-fuse-git-critical package from AUR by using 'makepkg -o' (download/extract source), then copying those two files from the original archive over the top of the git versions, then using 'makepkg -e' (build package using existing source).
- Steps to reproduce:
- Attempt to build zfs_fuse on ArchLinux x64 (as of 20100620T1623PDT) using zfs-fuse-git-critical package from AUR.
Added by
Seth Heeren
on
Jun 22, 2010 03:36 AM
Issue state:
unconfirmed → resolved
Target release:
None → 0.6.9
Responsible manager:
(UNASSIGNED) → sgheeren
Ok, thanks for the heads up
This is/was by design. The tarball is actually a snapshot from testing containing these commits
http://gitweb.zfs-fuse.net/[…]shortlog;h=0.6.9-2-g1529820
After thinking about this, I have created a separate download and ditto branch for 'maintenance snapshot'. This way we can keep the 'official' tar-ball stable and identical to 0.6.9 tag.
This should actually far better for our packagers as well.
We will let people find out the fixes if they need them... Anyways they are on the 0.7.0 preview of course.
---- For reference these were the pointers already around:
http://zfs-fuse.net/news/announcing-zfs-fuse-0.6.9
"Known fixes to compilation issues will be added to the testing branch on the official repository"
and here
http://zfs-fuse.net/[…]/i-get-compilation-error-y
"Have a look at the testing branch"
I'm open to your suggestions on how to improve the situation.
PS. Also, be invited to have a look at the wiki page for Arch building. I've posted what I know, but I'm no Arch user, so perhaps you can improve it; feel free to take a separate page on the wiki!
http://zfs-fuse.net/wiki/building-installing-tips
This is/was by design. The tarball is actually a snapshot from testing containing these commits
http://gitweb.zfs-fuse.net/[…]shortlog;h=0.6.9-2-g1529820
After thinking about this, I have created a separate download and ditto branch for 'maintenance snapshot'. This way we can keep the 'official' tar-ball stable and identical to 0.6.9 tag.
This should actually far better for our packagers as well.
We will let people find out the fixes if they need them... Anyways they are on the 0.7.0 preview of course.
---- For reference these were the pointers already around:
http://zfs-fuse.net/news/announcing-zfs-fuse-0.6.9
"Known fixes to compilation issues will be added to the testing branch on the official repository"
and here
http://zfs-fuse.net/[…]/i-get-compilation-error-y
"Have a look at the testing branch"
I'm open to your suggestions on how to improve the situation.
PS. Also, be invited to have a look at the wiki page for Arch building. I've posted what I know, but I'm no Arch user, so perhaps you can improve it; feel free to take a separate page on the wiki!
http://zfs-fuse.net/wiki/building-installing-tips
