Your message dated Mon, 02 Oct 2006 20:39:16 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#390563: No vc_new_s_context() in libvserver.* has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: util-vserver Version: 0.30.210-10 Severity: normal Hello, The /usr/lib/libvserver.{a,so} files does not contain the vc_new_s_context() call. [EMAIL PROTECTED]:~$ nm /usr/lib/libvserver.a lib_libvserver_a-syscall.o: nm: lib_libvserver_a-syscall.o: no symbols lib_libvserver_a-checkversion.o: U __errno_location 00000004 b res.2833 00000000 T utilvserver_checkCompatVersion 00000000 b v_errno.2834 ... I think it's either a configure option or due to one of the patch, as vc_new_s_context() is present in the Mandriva util-vserver-devel. [EMAIL PROTECTED]:~$ nm util-vserver-devel-0.30.210-5mdk.i586/libvserver.a lib_libvserver_a-syscall.o: U __errno_location 0000008e T vc_new_s_context 00000000 T vc_set_ipv4root lib_libvserver_a-checkversion.o: U __errno_location 00000004 b res.2820 00000000 T utilvserver_checkCompatVersion 00000000 b v_errno.2821 ... I've tried to recompile from the debian source under two kernels, a vserver-patched one and a non-patched with the same result. Vincent
--- End Message ---
--- Begin Message --------BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Ola Lundqvist wrote: > Hi > > I do not think that upstream have really settled the development > files for this. As far as I know they do not really treat this > as an external library. They do not properly handle it with > versioning as far as I know. This is definately true. > That sais, I do not really have a good idea on why it is like > this. You can try with the 0.30.210-11 version that I uploaded > to unstable yesterday. It had some more things compiled in but I > do not think it has anything to do with this though. > > Micah (my co maintainer may know). I believe that this is fixed in 0.30.210-11 because the - --enable-apis=NOLEGACY option was added to the ./configure: See below: >> [EMAIL PROTECTED]:~$ nm /usr/lib/libvserver.a >> >> lib_libvserver_a-syscall.o: >> nm: lib_libvserver_a-syscall.o: no symbols >> >> lib_libvserver_a-checkversion.o: >> U __errno_location >> 00000004 b res.2833 >> 00000000 T utilvserver_checkCompatVersion >> 00000000 b v_errno.2834 This version shows it: ~/debian/vserver/util-vserver/build-area% nm /usr/lib/libvserver.a lib_libvserver_a-syscall.o: U __errno_location 00000087 T vc_new_s_context 00000000 T vc_set_ipv4root lib_libvserver_a-checkversion.o: U __errno_location 00000004 b res.2956 00000000 T utilvserver_checkCompatVersion 00000000 b v_errno.2957 I'm closing this bug. Micah -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFIc1U9n4qXRzy1ioRAl9bAJ94KkguqR80NM/PiqA+U+GnSxmxBQCdHSeS PwjC3He2XP83Hf9kJbChErg= =tT6U -----END PGP SIGNATURE-----
--- End Message ---
