Bug 986622 - Pootle 2.1.6 broken as incorrectly packaged as requiring Django 1.4
Pootle 2.1.6 broken as incorrectly packaged as requiring Django 1.4
Product: Fedora
Classification: Fedora
Component: pootle (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Dwayne Bailey
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-07-21 00:14 EDT by Martin
Modified: 2015-02-17 11:16 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 11:16:51 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin 2013-07-21 00:14:49 EDT
Description of problem:
pootle 2.1.6 is incompatible with Django 1.4 and is broken on a new install.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. yum install pootle
2. Fix https://bugzilla.redhat.com/show_bug.cgi?id=871467
3. Browse to /pootle site.

Actual results:
"Server Error
An error has occurred. Thank you for your patience."
Server log:
"ImproperlyConfigured: settings.DATABASES is improperly configured. Please supply the ENGINE value. Check settings documentation for more details."

Expected results:
Working Pootle website / welcome page.

Additional info:

From the RPM log:
* Tue May 07 2013 Matthias Runge <mrunge@redhat.com> - 2.1.6-6
- change requirements to python-django14

However, 2.1.6 (Apr 2011) was released prior to Django 1.4 (March 2012). Its settings.py contains DATABASE_ENGINE, etc, which are incompatible with Django 1.4 (deprecated since 1.2; see https://docs.djangoproject.com/en/1.3/ref/settings/#database-engine).
Pootle 2.5.0 is released (https://bugzilla.redhat.com/show_bug.cgi?id=965246) and should be updated if Django 1.3 is unavailable.
Comment 1 Fedora End Of Life 2015-01-09 14:01:40 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Fedora End Of Life 2015-02-17 11:16:51 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.