Bug 1048510

Summary: octave-NLopt install errors
Product: [Fedora] Fedora Reporter: Jerry James <loganjerry>
Component: NLoptAssignee: Björn 'besser82' Esser <besser82>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 20CC: besser82, ml
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: NLopt-2.4.1-5.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-25 02:20:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jerry James 2014-01-04 19:04:24 UTC
Description of problem:
Installing octave-NLopt results in some installation errors:

Installing : octave-NLopt-2.4.1-1.fc20.x86_64                            8/26 
skipping line
skipping line
skipping line
skipping line
error: description is missing needed field name
error: called from:
error:   /usr/share/octave/3.6.4/m/pkg/pkg.m at line 1768, column 7
error:   /usr/share/octave/3.6.4/m/pkg/pkg.m at line 562, column 12
error:   /usr/share/octave/3.6.4/m/pkg/pkg.m at line 472, column 25
warning: %post(octave-NLopt-2.4.1-1.fc20.x86_64) scriptlet failed, exit status 1
Non-fatal POSTIN scriptlet failure in rpm package octave-NLopt-2.4.1-1.fc20.x86_64

The problem appears to be that the DESCRIPTION file contains free text, rather than the formatted text described in http://www.gnu.org/software/octave/doc/interpreter/The-DESCRIPTION-File.html.

Version-Release number of selected component (if applicable):
octave-NLopt-2.4.1-1.fc20.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install octave-NLopt
2.
3.

Actual results:
Errors resulting from an incorrect DESCRIPTION file.

Expected results:
No errors.

Additional info:

Comment 1 Fedora Update System 2014-01-14 13:07:56 UTC
NLopt-2.4.1-5.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/NLopt-2.4.1-5.el5

Comment 2 Fedora Update System 2014-01-14 13:08:28 UTC
NLopt-2.4.1-5.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/NLopt-2.4.1-5.el6

Comment 3 Fedora Update System 2014-01-14 13:08:53 UTC
NLopt-2.4.1-5.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/NLopt-2.4.1-5.fc18

Comment 4 Fedora Update System 2014-01-14 13:09:20 UTC
NLopt-2.4.1-5.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/NLopt-2.4.1-5.fc19

Comment 5 Fedora Update System 2014-01-14 13:26:20 UTC
NLopt-2.4.1-5.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/NLopt-2.4.1-5.fc20

Comment 6 Fedora Update System 2014-01-14 20:56:08 UTC
Package NLopt-2.4.1-5.el5:
* should fix your issue,
* was pushed to the Fedora EPEL 5 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing NLopt-2.4.1-5.el5'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0165/NLopt-2.4.1-5.el5
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2014-01-25 02:20:12 UTC
NLopt-2.4.1-5.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2014-01-25 02:21:53 UTC
NLopt-2.4.1-5.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2014-01-31 20:09:35 UTC
NLopt-2.4.1-5.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2014-01-31 20:10:33 UTC
NLopt-2.4.1-5.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.