Bug 444940 - Amarok 1.4.9.1-2.fc8 built without libnjb support
Summary: Amarok 1.4.9.1-2.fc8 built without libnjb support
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: amarok
Version: 8
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-02 06:54 UTC by Edward Sheldrake
Modified: 2008-05-17 22:18 UTC (History)
2 users (show)

Fixed In Version: 1.4.9.1-3.fc8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-17 22:18:09 UTC


Attachments (Terms of Use)

Description Edward Sheldrake 2008-05-02 06:54:04 UTC
Description of problem:
Amarok 1.4.9.1-2.fc8 has been built without libnjb support.

Version-Release number of selected component (if applicable):
1.4.9.1-2.fc8 (updates-testing)

How reproducible:
Always.

Steps to Reproduce:
1. Install amarok from F-8 updates-testing
2.
3.
  
Actual results:
No NJB support.

Expected results:
NJB support.

Additional info:
It's due to an error in the .spec: _with_njb needs to be changed to _with_libnjb
in the BuildRequires and files sections.

NB I don't actually use the libnjb support, but was rebuilding the .src.rpm
locally, and had libnjb-devel installed so the build failed due to unpackaged files.

Comment 1 Rex Dieter 2008-05-02 11:59:02 UTC
rats, thanks!

Comment 2 Fedora Update System 2008-05-10 13:54:31 UTC
amarok-1.4.9.1-3.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update amarok'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-3320

Comment 3 Fedora Update System 2008-05-17 22:18:07 UTC
amarok-1.4.9.1-3.fc8 has been pushed to the Fedora 8 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.