launchpad-dev team mailing list archive
-
launchpad-dev team
-
Mailing list archive
-
Message #07643
Broken Lp deps in Oneiric
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There are a few classes of broken deps that I think need discussion to
determine how to fix Lp's deps in oneiric. I and Tim are currently
reading the packages that our meta packages require, and install what we
can, sometimes locating older version of packages.
Special packages:
The spidermonkey-bin package is a good example here. We package it
because it is notoriously hard to keep current; Ubuntu does not package
it amymore. I could try to copy the package the package to ~launchpad's
oneiric series, but the only use of it is jslint. Oh, and I see it uses
a stale version of crockerford's fulljslint in the tree. Pocketlint uses
seed, which is already installed with Ubuntu, and It uses the a very
recent version of fulljslint. I propose we just use pocketlint.
Conflicting packages:
Oneiric users cannot install launchpad because python-profiler conflicts
with Python 2.6/2.7 It appears to require surgery to install. I forced
it to install and it overwrote files installed by other packages. I am
not familiar with the issue, but this seams like a candidate for lp
packaging/egg/sourcecode to ensure the features we want are available.
However, the package says it conflicts with python2.5. Do we really need
this package? Can we remove it from the deps now that we use python2.6?
Old packages:
I have python-subunit pinned, The current version cannot be installed.
This looks like a python2.7 issue. Updating Lp to python 2.7 is the
official answer from Robert when he closed the bug I reported. We do not
have a plan to get to 2.7. By plan, I mean a tagged bugs, committed
engineers, and a release plan to make Lp run on 2.7. I do not think we
want to backport python2.7 to Lucid. We could republish the the order
python 2.6 packages in ~launchpad's repo.
- --
Curtis Hovey
http://launchpad.net/~sinzui
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk4fLtIACgkQnGlTRlchMn2YdQCfdVlovYlkRGwDZUqc1/KQSnGY
4mEAoNACzPHNagViOgwAgGwvYDJpZ8dV
=wcXY
-----END PGP SIGNATURE-----
Follow ups