Bug 927283 - SuperLU must ship code examples
Summary: SuperLU must ship code examples
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: SuperLU
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Shakthi Kannan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-25 14:50 UTC by Shakthi Kannan
Modified: 2013-04-03 04:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-03 04:27:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Shakthi Kannan 2013-03-25 14:50:23 UTC
The code examples in the SuperLU package need to be shipped.

Comment 1 Fedora Update System 2013-03-25 16:25:01 UTC
SuperLU-4.3-5.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/SuperLU-4.3-5.fc17

Comment 2 Fedora Update System 2013-03-25 16:25:11 UTC
SuperLU-4.3-5.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/SuperLU-4.3-5.fc18

Comment 3 Fedora Update System 2013-03-25 22:52:14 UTC
Package SuperLU-4.3-5.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing SuperLU-4.3-5.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-4382/SuperLU-4.3-5.fc18
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-04-03 04:27:27 UTC
SuperLU-4.3-5.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2013-04-03 04:44:32 UTC
SuperLU-4.3-5.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.