Closed ianthomas23 closed 4 years ago
Looks like the fluidity package is out-of-date. It should no longer depend on python-spud
. python-spud
should indeed conflict with python3-spud
and it should be using python3-spud
. @tmbgreaves: did you have a more up-to-date debian/control than what is in master, or shall I fix it there?
Good catch, thank you @ianthomas23 . @stephankramer master is the latest version; I'll update there and rebuild the package. I need to do a .17 release for Python3 in any case so will sort both of those out today -- watch this space :-)
This is a slightly bigger job than expected - needs a more general overhaul of the control file (and dockerfiles). I'll push a bugfix to master for all of that and aim to rebuild the package this afternoon.
Running some test package builds now and hoping to push a new package in the next half hour or so.
Changes PR'ed as #248
Manual build breaks (which I should have thought of...). Fixing..
Packages built; running a test install in a container.
All done - merged PR.
I can confirm that this now works OK for me. Thanks for fixing it!
When trying to install fluidity on a clean ubuntu 18.04 installation using the PPA, there are conflicts between the versions of the various spud packages, particularly
python-spud
, meaning fluidity cannot be installed.Looking at https://launchpad.net/~fluidity-core/+archive/ubuntu/ppa/+packages, spud 1.1.8.1 does not include a
python-spud
package.