Bug 912675
| Summary: | Package BitlBee 3.2 (current package will break with Twitter on 2013-03-05 due to new API) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Eike Hein <hein> | ||||
| Component: | bitlbee | Assignee: | Robert Scheck <redhat-bugzilla> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | mcepl, mcepl, rdieter, redhat-bugzilla | ||||
| Target Milestone: | --- | Keywords: | Patch | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-03-02 19:59:59 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: | |||||||
| Attachments: |
|
||||||
|
Description
Eike Hein
2013-02-19 11:42:46 UTC
Created attachment 699453 [details]
.spec patch
update looks simple enough packaging-wise, get to drop a few upstreamed patches (always good).
Rex, in theory that's right. But when looking deeper, this is not correct. However, thank you very much for the patch...I merged some of the hunks that were needed. Additionally, upstream decided to require glib2 >= 2.14, which would exclude EPEL 5 completely. Technically they only need this more recent glib2 version due to their programming lazyness (sorry!) and the wish to use regexps for URL length detection for the Twitter stuff. As the current used Twitter API is anyway going to break soon, I decided to drop Twitter support for EPEL 5, till either upstream can be couraged to re-implement that code (which is not likely as from what I got told on the IRC) or if somebody else provides a nice portable piece of code. Again, affects only EPEL 5 - no other branch! bitlbee-3.2-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/bitlbee-3.2-1.fc18 bitlbee-3.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/bitlbee-3.2-1.fc17 bitlbee-3.2-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/bitlbee-3.2-1.el6 bitlbee-3.2-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/bitlbee-3.2-1.el5 Thanks to both of you! Package bitlbee-3.2-1.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 bitlbee-3.2-1.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-0400/bitlbee-3.2-1.el5 then log in and leave karma (feedback). bitlbee-3.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. bitlbee-3.2-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. bitlbee-3.2-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. bitlbee-3.2-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. |