Closed Bug 846349 Opened 11 years ago Closed 8 years ago

Update outdated packages

Categories

(Marketplace Graveyard :: Code Quality, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: robhudson, Unassigned)

References

Details

(Whiteboard: [ktlo][possible_future_need])

This is output from pip-tools `pip-review` command. We may or may not want to upgrade many of these but I thought it'd be worth a review from time to time...

Django==1.5 is available (you have 1.4.5)
Jinja2==2.6 is available (you have 2.5.5)
M2Crypto==0.21.1 is available (you have 0.20.2)
PIL==1.1.6 is available (you have 1.1.7)
PyBrowserID==0.9.1 is available (you have 0.6.0)
SQLAlchemy==0.7.10 is available (you have 0.7.5)
Sphinx==1.1.3 is available (you have 0.6.3)
bleach==1.2.1 is available (you have 1.1.5)
celery==3.0.15 is available (you have 2.5.1)
chardet==2.1.1 is available (you have 1.0.1)
django-celery==3.0.11 is available (you have 2.2.4)
django-statsd-mozilla==0.3.8.5 is available (you have 0.3.8)
django-storages==1.1.6 is available (you have 1.1.4)
django-tastypie==0.9.12 is available (you have 0.9.11)
docutils==0.10 is available (you have 0.7)
easy-thumbnails==1.2 is available (you have 1.1)
elasticutils==0.6 is available (you have 0.5)
feedparser==5.1.3 is available (you have 5.0.1)
gunicorn==0.17.2 is available (you have 0.15.0)
html5lib==0.95 is available (you have 0.90)
httplib2==0.7.7 is available (you have 0.7.6)
kombu==2.5.6 is available (you have 2.1.2)
lxml==3.1.0 is available (you have 2.2.6)
metlog-py==0.10.0 is available (you have 0.9.10)
mimeparse==0.1.4 is available (you have 0.1.3)
newrelic==1.10.2.38 is available (you have 1.5.0.103)
pyquery==1.2.4 is available (you have 0.4)
python-dateutil==2.1 is available (you have 1.5)
pytz==2012j is available (you have 2010e)
raven==3.1.16 is available (you have 2.0.7.1)
rdflib==3.2.3 is available (you have 3.0.0)
recaptcha-client==1.0.6 is available (you have 1.0.5)
receipts==0.2.5 is available (you have 0.2.4.1)
requests==1.1.0 is available (you have 0.14.0)
simplejson==3.1.0 is available (you have 2.3.2)
suds==0.4 is available (you have 0.3.9)
This bug is ripe for splitting up.  If you upgrade one or two, file a new bug and assign it to yourself.
Priority: -- → P5
Whiteboard: p=3
The number of outdated apps have now doubled. I'll be trying to eliminate a few... I already stumbled upon https://github.com/gawel/pyquery/issues/6 and https://github.com/gawel/pyquery/issues/40 , which prevent us to update pyquery.
Took a first stab at some that looked easy / straightforward / harmless : https://github.com/mozilla/zamboni/pull/990
Assignee: nobody → mpillard
According to discussion in the PR, https://github.com/kennethreitz/requests/issues/749#issuecomment-19284753 prevents us from upgrading to requests 1.2.1 or higher.
Status: NEW → ASSIGNED
Priority: P5 → P4
Depends on: 915742
Depends on: 883477
Depends on: 917040
More outdated packages fixed in https://github.com/mozilla/zamboni/commit/00b40589773dbe9edeff197fc5cf001806536f81

There is still a lot of work to do...
Updated a few outdated celery packages (& dependencies):
https://github.com/mozilla/zamboni/commit/89e8cfa
Updated most of the outdated packages: PR opened https://github.com/mozilla/zamboni/pull/1538

Extended report is here: https://gist.github.com/magopian/d4b6d497d0a9a3b67362
Some failing tests related to Bleach https://ci-addons.allizom.org/job/marketplace/5535/
I'm pretty sure those failures happen because jenkins doesn't have the up to date requirements (especially bleach). Is it possible? How are we supposed to fix that?

I ran a few failing tests locally, and they pass without a glitch (and fail with bleach 1.1.5 instead of 1.2.2).
With updated requirements, the whole mkt jenkins build now fails: https://ci-addons.allizom.org/job/marketplace/5542/console

This is because there's no STATIC_URL in the jenkins settings, and django-browserid (the updated version) requires one.

@mat thus downgraded django-browserid back to 0.8 (the previous used version).
it looks like STATIC_URL is just "" according to https://github.com/mozilla/zamboni/blob/master/scripts/run_mkt_tests.sh#L86 .  You can change that file and build.sh to adjust how jenkins runs, afaik.
Depends on: 961156
After running pip-review I'm not sure we'll ever be able to close this bug.  Perhaps we should review/update the packages quarterly or something?  Anyone have a good upgrade strategy?
We were discussing this with magopian on IRC, I think we need a much shorter review period. Something like every month minimum. And we need better tools than just barebone pip-review (I know magopian has some he needs to clean up and share). 

But I think it's doable, it's just that the first steps are very painful because it hasn't been done in a long time. I also think it's valuable, especially because a lot of these packages don't get backported security fixes, this means the best way to stay secure is to stay on top of the updates.
Depends on: 968226
Depends on: 963513
check https://requires.io (thanks Rob for the tip ;)
Here's a report from https://requires.io/github/magopian/zamboni/requirements/?branch=master

The more requirements we can switch from a github link to a PyPI requirement, the more accurate the report!

What's missing is a view of what blocks upgrading a specific package, and the perceived "risk".
Assignee: mpillard → nobody
Whiteboard: p=3 → [repoman]
Status: ASSIGNED → NEW
Priority: P4 → P3
Depends on: 1027337
See Also: → 1027340
Closing this because it is an eternal issue, but in lieu of the bug we should have a policy about periodically updating dependencies.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Re-opening because we haven't decided on a policy and it has gotten worse. https://requires.io/ is a good start to get an overview.
Some easy ones taken care of in https://github.com/mozilla/zamboni/commit/113432198f4e28560a3a74e6f66ce5b7663e50c0
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Depends on: 1136676
Depends on: 1136820
Depends on: 1138404
Blocks: 1139886
Depends on: 1141810
Priority: P3 → P2
Whiteboard: [repoman] → [repoman][ktlo]
Well, it was fixed to a point. But this is really just ongoing maintenance.
Status: REOPENED → RESOLVED
Closed: 10 years ago8 years ago
Resolution: --- → WONTFIX
Whiteboard: [repoman][ktlo] → [ktlo][possible_future_need]
You need to log in before you can comment on or make changes to this bug.