Bug 750045 - fluxbox-1.3.2 is available
Summary: fluxbox-1.3.2 is available
Alias: None
Product: Fedora
Classification: Fedora
Component: fluxbox
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-10-30 11:10 UTC by Upstream Release Monitoring
Modified: 2011-11-21 22:56 UTC (History)
1 user (show)

Fixed In Version: fluxbox-1.3.2-2.fc16
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2011-11-21 22:56:37 UTC
Type: ---

Attachments (Terms of Use)

Description Upstream Release Monitoring 2011-10-30 11:10:13 UTC
Latest upstream release: 1.3.2
Current version in Fedora Rawhide: 1.3.1
URL: http://fluxbox.org/download/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:

Comment 1 Fedora Update System 2011-11-06 21:43:58 UTC
fluxbox-1.3.2-1.fc16 has been submitted as an update for Fedora 16.

Comment 2 Fedora Update System 2011-11-06 21:52:06 UTC
fluxbox-1.3.2-1.fc15 has been submitted as an update for Fedora 15.

Comment 3 Fedora Update System 2011-11-07 08:54:51 UTC
Package fluxbox-1.3.2-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fluxbox-1.3.2-1.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2011-11-21 22:53:11 UTC
fluxbox-1.3.2-2.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2011-11-21 22:56:37 UTC
fluxbox-1.3.2-2.fc16 has been pushed to the Fedora 16 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.