Some packages are named differently in Jessie compared to Trusty:
| Ubuntu | Debian |
| firefox | iceweasel |
| chromium-browser | chromium |
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| contint: update browsers package names for Jessie | operations/puppet | production | +18 -3 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | hashar | T103972 Setup jobs for operations/software/conftool | |||
| Resolved | hashar | T95545 Migrate all debian-glue jobs to Jessie slaves | |||
| Resolved | hashar | T102894 Move labs/tools/extdist tox tests to jessie | |||
| Resolved | hashar | T103977 Create tox templates that are bound to jessie | |||
| Resolved | hashar | T94836 Create CI slaves using Debian Jessie | |||
| Resolved | hashar | T95000 Update puppet for packages having different names in Jessie |
Event Timeline
Comment Actions
Change 201711 had a related patch set uploaded (by Hashar):
contint: update browsers package names for Jessie
Comment Actions
firefox -> iceweasel
chromium-browser -> chromium
This also affects the global binaries from shell. We'll need individual projects to ensure that whatever frameworks they use support these alternate names (or provide aliases to them in the default PATH). I believe this support is currently not present.
Do not bother installing phantomjs on Jessie. It is not available and we are going to drop its usage entirely.
PhantomJS will still be used by some tests as additional browser. That is unlikely to change. However, at least for npm builds, this is not an issue since it installs phantomjs via an npm package in the local workspace and runs it from there.
Comment Actions
Change 201711 merged by Giuseppe Lavagetto:
contint: update browsers package names for Jessie
Comment Actions
Solved! That also made firefox to be magically upgraded just like chromium.
Labs instance integration-slave-jessie-1001 is all happy about it.