Bug 690103
| Summary: | Django-1.3 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
| Component: | Django | Assignee: | Steve Milner <smilner> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | dmalcolm, esm, j, michel, smilner |
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Django-1.3.1-2.fc16 | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-04-15 21:27:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Upstream Release Monitoring
2011-03-23 11:12:37 UTC
I did a naive update to 1.3 (change version; spectool -g *spec, fedpkg mockbuild) but it fails due to an unpackaged file (/usr/lib/python2.7/site-packages/django/conf/locale/es_MX/__init__py) which seems to be an upstream bug. There are also a load of "File listed twice" complaints for all of the new locale files under django/contrib/* since they localized all of the contrib stuff. I guess those should be easy to deal with. I can probably fix all of this up for you if you like. I noticed the same thing when I was updating the spec and trying a build in Koji. If you have the time go for it! :-) Upstream bug: http://code.djangoproject.com/ticket/15726 I have been poking around with a simpler way to avoid all of the "file listed twice" complaints without making the %files list huge but I've not been successful. There seems to be no simple way to do this, though to be honest I have to wonder about the value of %lang-tagging all of the .mo files anyway. Does the software actually cope properly if they're missing? Django-1.3-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/Django-1.3-1.fc14 Django-1.3-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/Django-1.3-1.fc13 Django-1.3-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/Django-1.3-1.fc15 (In reply to comment #4) > I have been poking around with a simpler way to avoid all of the "file listed > twice" complaints without making the %files list huge but I've not been > successful. There seems to be no simple way to do this, though to be honest I > have to wonder about the value of %lang-tagging all of the .mo files anyway. > Does the software actually cope properly if they're missing? Good question, I don't know -- I have not tried it without them yet :-). I submitted it as is for testing to see how it goes with the current 'file listed twice' issue. Did you really mean to push this as an update to F13 and F14? See: http://docs.djangoproject.com/en/dev/releases/1.3/#backwards-incompatible-changes-1-3 It was submitted to testing; I would assume that it wouldn't actually be pushed to stable. Perhaps some negative karma would ensure that. I did mean to push it as an update but your point is valid and well taken -- the security enhancement and changes could cause issues. I will only push it to stable for F15+. I am not planning on pushing 1.3 to EL6 or older. I've added a -1 to the F13 and F14 instances. Since you created the update requests, you can also simply revoke them. Or I can do it for you. Package Django-1.3-1.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing Django-1.3-1.fc14' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/Django-1.3-1.fc14 then log in and leave karma (feedback). Django-1.3-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/Django-1.3-2.fc15 Django-1.3-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. Django-1.2.6-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/Django-1.2.6-2.el6 Django-1.3.1-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/Django-1.3.1-2.fc15 Django-1.3.1-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/Django-1.3.1-2.fc16 Django-1.3.1-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/Django-1.3.1-2.fc14 Django-1.3.1-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. Django-1.3.1-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. Django-1.2.6-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. Django-1.3.1-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |