FWIW, I was able to apply bb96fc4295 cleanly to the current 20.04
package (2:3.3.16-1ubuntu2) and it works for me.
apt-get -y source procps && cd procps-*
curl -fSsL -o debian/patches/sc_arg_max
https://gitlab.com/procps-ng/procps/-/commit/bb96fc4295.patch
echo sc_arg_max >>debian/patches/series
FWIW, I fixed the bionic package in my PPA:
https://launchpad.net/~nvidia-deepops/+archive/ubuntu/slurm/+packages?field.status_filter=
I also backported the disco package for bionic in that PPA, since the
symlinks are fixed there.
--
You received this bug notification because you are a member
** Changed in: pymongo (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639354
Title:
pip doesn't recognize installation because of missing egg information
To
FROM ubuntu:xenial
RUN apt-get update \
&& apt-get install -y --no-install-recommends \
python-pymongo \
python-pip \
&& rm -rf /var/lib/apt/lists/*
RUN python -c 'import pymongo; print pymongo.__version__, pymongo.__file__'
RUN pip list
RUN pip install pymongo
RUN python
^ That was supposed to be an attachment. A dockerfile to repro.
The pip list command shows only one Python package installed (pip
(8.1.1)).
The pip install command should do nothing, since pymongo is already
installed. But instead, pip doesn't see the existing installation and
re-installs the
Sorry, I'm new to this bug system. This comment makes it seem like
Sandro closed the debian bug as "Won't Fix":
> since the patch is taken from upstream i wont change it as it will
make it harder to merge when they release again. it's purely aesthetic
so we can live with that, closing.
... but
Public bug reported:
Ubuntu 16.04
pymongo 3.2-1build1
When most packages (i.e. numpy, scipy, flask, etc.) are installed with
deb packages, they are installed in such a way that pip can see them.
This is done by installing "*.egg-info/" directories (find
/usr/lib/python2.7/dist-packages -type d
