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

Failed to install python-mapnik from PPA #16

Open
sun9700 opened this issue Jul 30, 2015 · 5 comments
Open

Failed to install python-mapnik from PPA #16

sun9700 opened this issue Jul 30, 2015 · 5 comments
Assignees

Comments

@sun9700
Copy link

sun9700 commented Jul 30, 2015

I did the following instructions to install mapnik 3.0.0:

sudo add-apt-repository ppa:mapnik/nightly-trunk
sudo apt-get update
sudo apt-get install libmapnik libmapnik-dev mapnik-utils python-mapnik

BUT, the python binding is failed:

The following packages have unmet dependencies:
python-mapnik : Depends: libmapnik (= 3.0.0+dev20150425.git.d89033a-1trusty1) but 3.0.0+dev20150729.git.a78a895-1trusty1 is to be installed
E: Unable to correct problems, you have held broken packages.

@marcu
Copy link

marcu commented Aug 24, 2015

I have the same error. No idea to fix it...

@whitelynx
Copy link

I had a similar error:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mapnik-input-plugin-osm : Depends: libmapnik (= 3.0.0+dev20150716.git.af0369d-1~trusty1) but 3.0.0+dev20150915.git.0532df7-1~trusty1 is to be installed

It looks like the "nightly" builds sometimes don't actually build all of the packages, so some newer packages get pushed, without updating others. Since all the packages explicitly depend on specific git versions of the other packages, that breaks installation.

It seems to me like there's 3 possible options:

  • If any build fails, don't publish any updated packages to the PPA. (undesirable, because one package's build breaking prevents all other packages from getting updated)
  • Change packages to only depend on any 3.0.0+dev version, not a specific version with a date and git commit SHA. (I'm not personally familiar enough with APT to tell whether or not this is actually possible)
  • If a build fails, rebuild the previous working version against the current versions of its dependency packages. (takes more time during the build process, but should produce consistently usable results)

@ARolek
Copy link

ARolek commented Nov 1, 2015

Any updates on this? I'm also stuck where I can't install python-mapnik from the repo ppa:mapnik/nightly-trunk:

The following packages have unmet dependencies:
 python-mapnik : Depends: libmapnik (= 3.0.0+dev20150425.git.d89033a-1~trusty1) but 3.0.0+dev20151031.git.34f5b56-1~trusty1 is to be installed
E: Unable to correct problems, you have held broken packages.

@rcoup rcoup self-assigned this Nov 5, 2015
@rcoup
Copy link
Contributor

rcoup commented Nov 5, 2015

unfortunately building is being handled by Launchpad so we only have a few levers to pull here. I'll see if I can figure out what's going on.

If any build fails, don't publish any updated packages to the PPA. (undesirable, because one package's build breaking prevents all other packages from getting updated)

This should be the desired outcome -- the other options will inevitably lead to broken-in-weird-ways packages I think.

@ARolek
Copy link

ARolek commented Nov 5, 2015

@rcoup got it. Is there a work around for now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants