--- # leave this alone, if the template changes this will # give us something to check against. contrib_package_information: 1.0 # update_type added in by SL update_type: enhancement # What is this package named? # # This should corrospond to a single source rpm # If you've got multiple source packages that are part of a single # application, please fill out the form once for each source package # but let us know they are part of a single application # examples: # # nagios # filezilla # brtfs-utils # kmod-brtfs package: zfs-0.6.4.1-1.el6 # A non-opensource licence will be rejected without consideration licence: CDDL # you can only have one primary_contact but you MUST have one # If you don't want to set an alternate contacts, that is fine submitted_by: # # Note each 'name' begins with '-' and nothing else does # - name: Chris Brown email: christopher.brown@med.ge.com primary_contact: Yes - name: Dave Kraus email: Dave.Kraus@ge.com primary_contact: No - name: Jonathan Schaaf email: jonathan.P.schaaf@ge.com primary_contact: No - name: Jim Foris email: jim.foris@med.ge.com primary_contact: No # the project webpage # examples: # http://www.nagios.org/ # http://filezilla-project.org/ project_page: http://zfsonlinux.org # the project's public code repo # examples: # http://nagios.svn.sourceforge.net/viewvc/nagios/ # https://svn.filezilla-project.org/svn/FileZilla3/trunk project_code: https://github.com/zfsonlinux/spl # The format of this date should be: # MM/DD/YYYY # for example: # 01/31/2012 # would be January 31, 2012 release_date: 06/11/2015 # Simply taking a copy of the project's current source repo # is not advised. An official release typically has had # some review to make sure any code changes don't lead to weird # regressions. A snapshot of the source tree typically has no such guarantee release_announcement: https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.6.4.1 # # If the project has released code that works for you, but # they have not said it is production ready, mark this as No # # Even if you've been running it in production for a while, # if the project says it isn't ready - we need to trust them. # production_ready: Yes explanation_of_hosting: > ZFS on Linux (ZOL) is currently manually added to HELiOS (Healthcare Enterprise Linux Operating System). HELiOS is a spin of Scientific Linux created and maintained by the GE Healthcare Compute Systems team (CST). HELiOS strives to be as upstream as possible thus including ZOL into SL helps us better maintain upstream purity in HELiOS. Including ZOL in SL also allows the rest of the SL community to benefit from our work with ZOL. release_description: > Update to latest upstream. # Any security update must have the correct severity # for the update specified. The guidelines are published at the following site: # https://access.redhat.com/security/updates/classification/ security_update: No # if you don't have any you must have this instead # fixed_bugs : No fixed_bugs: No # if you don't have any you must have this instead # fixed_cves : No fixed_cves: No # # Any i686 packages also in the x86_64 tree must be listed in both places # any noarch packages should be listed as though they were not. # rpms: - SL6_SRPMS: - zfs-0.6.4.1-1.el6.src.rpm - SL6_x86_64: - zfs-0.6.4.1-1.el6.x86_64.rpm - zfs-devel-0.6.4.1-1.el6.x86_64.rpm - zfs-dracut-0.6.4.1-1.el6.x86_64.rpm - zfs-test-0.6.4.1-1.el6.x86_64.rpm - libnvpair1-0.6.4.1-1.el6.x86_64.rpm - libuutil1-0.6.4.1-1.el6.x86_64.rpm - libzfs2-0.6.4.1-1.el6.x86_64.rpm - libzfs2-devel-0.6.4.1-1.el6.x86_64.rpm - libzpool2-0.6.4.1-1.el6.x86_64.rpm - SL6_debuginfo: - zfs-debuginfo-0.6.4.1-1.el6.x86_64.rpm