Dan Nurmi indicated that the carried patch could be eliminated, and
instead generated at build time if some axis2 (??) package were in main
instead of universe, and eucalyptus could build-depend on it, rather
than the eucalyptus package maintainer installing this universe package
on his local system and generating the patch.
I'm still learning about this WSDL-stubs issue, but I'm trying to
document my understanding here in this bug.
Looking through the archive for what package Dan is talking about --->
$ apt-cache search axis2 | awk '{print $1}' | xargs -i apt-cache show {} | grep
Filename
Filename: pool/main/a/axis2c/libapache2-mod-axis2c_1.6.0-0ubuntu7_amd64.deb
Filename: pool/main/a/axis2c/libaxis2c-dev_1.6.0-0ubuntu7_amd64.deb
Filename: pool/main/a/axis2c/libaxis2c-doc_1.6.0-0ubuntu7_all.deb
Filename: pool/main/a/axis2c/libaxis2c0_1.6.0-0ubuntu7_amd64.deb
Filename: pool/main/r/rampart/librampart-doc_1.3.0-0ubuntu5_amd64.deb
Filename: pool/universe/a/axis2c/libaxis2c-bin_1.6.0-0ubuntu7_amd64.deb
<------------
Filename: pool/main/r/rampart/librampart0_1.3.0-0ubuntu5_amd64.deb
Filename: pool/main/r/rampart/librampart-dev_1.3.0-0ubuntu5_amd64.deb
I only see one axis2c-related package that's in universe, libaxis2c-bin.
Is it not possible/practical to get this package promoted to Main for
Lucid? Thierry, do you know?
** Changed in: eucalyptus (Ubuntu)
Status: Triaged => Incomplete
--
improve wsdl stubs generation
https://bugs.launchpad.net/bugs/487270
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
