Bug 603337 - Wine 1.2-rc3 is available
Summary: Wine 1.2-rc3 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-12 13:10 UTC by Elad Alfassa
Modified: 2010-07-23 02:49 UTC (History)
2 users (show)

Fixed In Version: wine-1.2.0-1.fc13
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-23 02:45:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Elad Alfassa 2010-06-12 13:10:30 UTC
please update the package.

thanks.

Comment 1 Fedora Update System 2010-06-14 05:25:03 UTC
wine-1.2.0-0.3.rc3.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/wine-1.2.0-0.3.rc3.fc12

Comment 2 Fedora Update System 2010-06-14 05:26:24 UTC
wine-1.2.0-0.3.rc3.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/wine-1.2.0-0.3.rc3.fc13

Comment 3 Fedora Update System 2010-06-14 17:14:16 UTC
wine-1.2.0-0.3.rc3.fc13 has been pushed to the Fedora 13 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 wine'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/wine-1.2.0-0.3.rc3.fc13

Comment 4 Fedora Update System 2010-06-21 21:27:30 UTC
wine-1.2.0-0.4.rc4.fc13 has been pushed to the Fedora 13 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 wine'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/wine-1.2.0-0.4.rc4.fc13

Comment 5 Fedora Update System 2010-07-06 17:14:43 UTC
wine-1.2.0-0.6.rc6.fc13 has been pushed to the Fedora 13 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 wine'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/wine-1.2.0-0.6.rc6.fc13

Comment 6 Fedora Update System 2010-07-13 07:55:21 UTC
wine-1.2.0-0.7.rc7.fc13 has been pushed to the Fedora 13 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 wine'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/wine-1.2.0-0.7.rc7.fc13

Comment 7 gatlibs 2010-07-17 01:07:10 UTC
The new stable release, wine-1.2.0-1.fc13, has been built, by awjb, but it is not in the updates-testing repository. What will it take to push it to updates-testing? Is there a repository for builds prior to entering updates-testing?

Comment 8 Andreas Bierfert 2010-07-17 10:43:14 UTC
It should appear in updates-testing soon.Feedback in bodhi welcome!

https://admin.fedoraproject.org/updates/wine-1.2.0-1.fc13


https://admin.fedoraproject.org/updates/wine-1.2.0-1.fc12

Comment 9 gatlibs 2010-07-17 17:41:35 UTC
I got sick of waiting so I just downloaded and install the necessary packages from http://koji.fedoraproject.org/koji/buildinfo?buildID=184087. Is there not a repository or easier way than downloading rpms and manually installing them (for any builds that have not yet made updates-testing?

Comment 10 Fedora Update System 2010-07-23 02:44:29 UTC
wine-1.2.0-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2010-07-23 02:49:27 UTC
wine-1.2.0-1.fc12 has been pushed to the Fedora 12 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.