Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build failing, potentially Python? #218

Closed
annevk opened this issue Mar 31, 2020 · 2 comments · Fixed by #219
Closed

Build failing, potentially Python? #218

annevk opened this issue Mar 31, 2020 · 2 comments · Fixed by #219

Comments

@annevk
Copy link
Member

annevk commented Mar 31, 2020

So https://travis-ci.org/github/whatwg/html/builds/669108048 ends on

E: Unable to locate package python-pip
The command '/bin/sh -c apt-get update &&     apt-get install -y ca-certificates curl rsync git unzip     fp-compiler fp-units-fcl fp-units-net libc6-dev             default-jre                                                 libfontconfig1 libgomp1 libxml2                             python2.7 python-pip                                        fonts-dejavu fonts-droid-fallback fonts-liberation fonts-symbola fonts-unfonts-core' returned a non-zero code: 100

and the same after retrying.

cc @sideshowbarker @domenic

@sideshowbarker
Copy link
Contributor

We have this:

FROM debian:sid
RUN apt-get update && \
apt-get install -y ca-certificates curl rsync git unzip \
fp-compiler fp-units-fcl fp-units-net libc6-dev \
default-jre \
libfontconfig1 libgomp1 libxml2 \
python2.7 python-pip \
fonts-dejavu fonts-droid-fallback fonts-liberation fonts-symbola fonts-unfonts-core

…so it’s trying to install python-pip from the "sid" distribution of Debian. But if you go to https://packages.debian.org/sid/python-pip, the document there says:

Package not available in this suite.

…which means, I guess, that Debian recently removed the python-pip package from "sid".

https://packages.debian.org/source/testing/python-pip also shows “Package not available”.

https://packages.debian.org/source/stable/python-pip (buster) has it, though.

So I guess we could try changing FROM debian:sid to FROM debian:stable — though I’m guessing the reason we had it set to FROM debian:sid to begin with is that some of the other packages we need to install are only in sid. Or at least they were only in sid when we added them to the apt install invocation in that Docker file. But maybe by this time, they’re all in stable.

@sideshowbarker
Copy link
Contributor

sideshowbarker commented Mar 31, 2020

I’ll try changing the Dockerfile locally to FROM debian:stable, and see if it builds successfully.

sideshowbarker added a commit that referenced this issue Mar 31, 2020
domenic pushed a commit that referenced this issue Mar 31, 2020
Fixes #218. See #220 for migrating to Python 3, the better long-term fix.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants