Thomas Goirand
2011-Oct-26 08:24 UTC
[Pkg-xen-devel] ITP for XCP toolstack (xapi) on Debian
On 10/26/2011 05:29 AM, Mike McClurg wrote:> Perhaps you could send us a private deb file to test? I'm worried that > this might not be the right version that we need. Can you point us at > the upstream code you used?I used what was in the Git at: http://github.com/jonludlam/blktap.git The clone was made about a month ago, and it would be hard for me to tell when exactly. Adding version numbers will certainly help everyone here... There are many differences between my package and the one from Jon at http://downloads.xen.org/XCP/debian/repo/debian/pool/main/b/blktap/. I'll try summarize differences here: 1/ I didn't name the binary packages the same. Library package names *MUST* (by policy, IIRC) include the SONAME version in their package names. So my source package builds: blktap - libvhd1.0 - libvhdio1.0 - libblktapctl1.0 - blktap-dev - blktap-utils I was really not sure of the version number, so "1.0" might not be what we should use here. However, a version number should be there, and if I remember well, 1.0 was the internal SONAME of the libs. I have only one -dev and one -utils package. I think that's enough, no? Why splitting into more packages? 2/ Everywhere, I have Architecture: i386, and not just "any" since it wont work on other platforms anyway (Mike or Jon told me that amd64 wont be supported). 3/ *My* debian/copyright is correct ... :) Please don't even try to upload your blktap with such copyright, or accept the flames from the ftp-masters... :) 4/ There's still few lintian warnings in my package, the only one I'm really concerned with is: E: libblktapctl1.0: sharedobject-in-library-directory-missing-soname usr/lib/libblktapctl.so.1.0 N: N: A shared object was identified in a library directory (a directory in N: the standard linker path) which doesn't have a SONAME. This is usually N: an error. N: N: SONAMEs are set with something like gcc -Wl,-soname,libfoo.so.0, where 0 N: is the major version of the library. If your package uses libtool, then N: libtool invoked with the right options should be doing this. N: N: To view the SONAME of a shared library, run readelf -d on the shared N: library and look for the tag of type SONAME. N: N: Severity: important, Certainty: possible N: N: Check: shared-libs, Type: binary, udeb That one must be fixed before upload for sure. 5/ Please check my work: I've put the resulting binary and source packages here: http://node4407.gplhost.com/blktap/ Please let me know if: - if version are correct - if you think my package is ok - when you correct the above lintian warning, so I can pull again from github and re-create an orig.tar.gz Cheers, Thomas Goirand (zigo)
Possibly Parallel Threads
- Processed: Retitle and reassign "xcp-xapi fails to start" to xen-utils-common as "xend shouldn't start if TOOLSTACK is not xm"
- Bug#648691: ITP: blktap-dkms -- Xen blktap kernel component DKMS package
- Does libvirt support xapi/xe toolstack?
- Re: Does libvirt support xapi/xe toolstack?
- Re: Does libvirt support xapi/xe toolstack?