Description of problem: The COPYING file included with the package should be the GPL v2 file for consistency with License.txt. Currently it is the LGPL. Please update the package to the 0.2 release which fixes this problem. Version-Release number of selected component (if applicable): liberation-fonts-0.1-9.fc7 See thread here for more details. https://www.redhat.com/archives/fedora-maintainers/2007-August/msg00030.html
Currently liberation-fonts-0.1-9.fc7 has liberation-fonts-ttf-2.tar.gz which this problem doesn't exist. Change status to: CLOSED WORKSFORME.
No, you're missing the point. Let me spell it out: $ rpm -qa | grep liberation liberation-fonts-0.1-9.fc7 $ cat /usr/share/doc/liberation-fonts-0.1/COPYING GNU LIBRARY GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA [rest ommitted] $ cat /usr/share/doc/liberation-fonts-0.1/License.txt LICENSE AGREEMENT AND LIMITED PRODUCT WARRANTY LIBERATION FONT SOFTWARE This agreement governs the use of the Software and any updates to the Software, regardless of the delivery mechanism. Subject to the following terms, Red Hat, Inc. ("Red Hat") grants to the user ("Client") a license to this work pursuant to the GNU General Public License v.2 with the exceptions set forth below and such other terms as our set forth in this End User License Agreement. License.txt refers to GPL v2. COPYING is LGPL v2. Inconsistent.
Updated source to liberation-fonts-ttf-3.tar.gz Tested, built, pushed to testing. Pending for pushing to stable after 3-5 days.
Please push an update for F7 too when you have time.
Sorry above was referring to an F7 update.
http://koji.fedoraproject.org/packages/liberation-fonts/0.2/1.fc7/
liberation-fonts-0.2-1.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
Requested push to F7 update stable repo.
liberation-fonts-0.2-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.