Bug#629100: Status update
Package updated and now build correctly on Sid: https://github.com/Fantu/pkg-winexe About Samba private libraries now there is a workaround on upstream, I added override to lintian error. About hardening I disabled it on package and upstream added it on winexe's executable, then the hardening is enabled except for mingw's executables where is not supported. I did also some other minor package improvements. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629100: Status update
I updated the package for compatibility with samba 4.0.10+dfsg-2 now on unstable: https://github.com/Fantu/pkg-winexe On configure gave error of cli-ldap not found (but present). It was only moved to new samba-libs package and the file now is /usr/lib/*/samba/libcli-ldap.so.0 Give the same error with all libraries ending with version (.0) on so file and moved to new package. It still gives the -z option missed on winexesvc ld also with DEB_BUILD_HARDENING_RELRO=0. Is there something on winexe source that can force it? With fast grep search I not found nothing about. Thanks for any reply. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629100: Status update
I have updated package to latest winexe git commit [2a03a7] and latest
samba debian package of experimental.
https://github.com/Fantu/pkg-winexe
I saw other important samba package change ongoing:
http://anonscm.debian.org/gitweb/?p=pkg-samba/samba.git;a=shortlog;h=refs/heads/samba_4.0_integrate
When will be complete I'll update the winexe package also for those
change with dependencies and any others.
On my latest test on clean sid installation with Samba from experimental
I had one problem with winexe compilation:
[ 9/16] cprogram: build/winexesvc_launch.c.1.o
build/winexesvc_loop.c.1.o - build/winexesvc32.exe
/usr/bin/i686-w64-mingw32-ld: -z option unrecognized
collect2: ld returned 1 exit status
Waf: Leaving directory `/root/winexe/source/build'
Build failed
- task in 'winexesvc32.exe' failed (exit status 1):
{task 20082064: cprogram
winexesvc_launch.c.1.o,winexesvc_loop.c.1.o - winexesvc32.exe}
['/usr/bin/i686-w64-mingw32-gcc', '-Wl,-z,relro', '-s',
'winexesvc_launch.c.1.o', 'winexesvc_loop.c.1.o', '-o',
'/root/winexe/source/build/winexesvc32.exe', '-Wl,-Bstatic',
'-Wl,-Bdynamic', '-luserenv']
-z option is missed on mingw ld but I not found where to remove it, I
did grep on winexe source without found '-Wl,-z,relro' options setting.
Can someone help me to solve please?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629100: Status update
The Samba team has been very busy preparing a unified, solid, and policy-compliant package based on release 4.0.6. Those guys deserve some serious respect. Their package will soon appear in experimental and then unstable and in Ubuntu. Once this package appears and has stabilized for a few weeks, winexe upstream (viz., the author and myself) will get winexe building against it. This may require some time, since the samba packaging has changed significantly. Once that work is done I will post another update here. To any Debian developer using winexe: please volunteer to package winexe for Debian! -- Thomas
Bug#629100: Status update
Winexe in the winexe-waf repository now builds nicely against the Samba 4 public API and shared libraries as represented by Debian Samba 4 packages and I am hoping, therefore, that there will soon be a new Winexe release based on this winexe-waf code. Once Winexe has been released it would be very nice if someone from the Debian community would package it. :) (Winexe can also be built statically, but this requires building against the Samba 4 source tree since the necessary static Samba 4 libraries aren't available.) -- Thomas
Bug#629100: Status update
I saw no updates for more than one year on this. I started to prepare package based on one debian folder of actual stable version, I had updated it for new winexe version (probably near to stable) on git://git.code.sf.net/p/winexe/winexe-waf . Public repository for debian package is here: https://github.com/Fantu/pkg-winexe I start to learning debian package on last years for support packaging of software that I use but without debian or with no more mantainer, probably I'll need help for good packaging following the debian standard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629100: Status update
I have submitted the revised source code (i.e., winexe ported to current samba git master branch) to winexe's author but it is not yet clear to me what he plans to do with it. The winexe build needs access to the samba source tree. This has not changed in my port. I have looked into the possibility of building winexe against Samba 4 *-dev packages. Unfortunately, the latter do not include all the needed header files. One possible course of action would be to work with the Samba 4 maintainers to get the missing header files included in the -dev files. But there are quite a few header files missing, so I wouldn't expect this request to be met with much enthusiasm. Given that winexe has to be built against the samba source tree, I think it's best if we try to get winexe included in Samba 4. If this attempt fails then winexe will have to be maintained separately from Samba. Winexe upstream will have to be maintained as a Samba 4 fork. The pain of this can be minimized by syncing regularly with Samba 4 master. For Debian we can then revisit the idea of building against -dev packages by including more headers. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629100: Status update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/08/11 15:08, Thomas Hood wrote: I have submitted the revised source code (i.e., winexe ported to current samba git master branch) to winexe's author but it is not yet clear to me what he plans to do with it. The winexe build needs access to the samba source tree. This has not changed in my port. I have looked into the possibility of building winexe against Samba 4 *-dev packages. Unfortunately, the latter do not include all the needed header files. One possible course of action would be to work with the Samba 4 maintainers to get the missing header files included in the -dev files. But there are quite a few header files missing, so I wouldn't expect this request to be met with much enthusiasm. Which headers are necessary? It seems like the only headers necessary would be the headers for svcctl. Alternatively, you should be able to use svcctl from Python rather than from C. The svcctl python module is included in the python-samba package already. Given that winexe has to be built against the samba source tree, I think it's best if we try to get winexe included in Samba 4. This doesn't seem likely given winexe is quite hard to build - it requires mingw32. Cheers, Jelmer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJOS8HgAAoJEACAbyvXKaRX994QAJwhP7zK0/aqVx6XXhmjbNpI Ege62Jhf17dZKG/UXu9WFOIEWOwQwE45azMD8zUrcEJ2EzSiKGW2AOul8K/PKOL8 cDEYgwsAL/rLXVqdDc2aAT4p395POsxr7Kh+5lp8+lnJIp6ugIrx8UdDxHBDZRu6 3cxcyHjBb8ZNukDL5ANWW15BbUq9SpHRfIuzTueLh8jjb8rlHz8DgDn9fpzTCMYa allw21StuOAyI9jElyyEJRISEloQrbtsqN5mr5zfkvy/hsA0mpiDIUfDNtHJUzkp MZIKvkRgDbdDUY+nm9+/p6Ud0zFbBY2X4kuxDS/rlOb8IMT2gJllTj6zLEX9o26N p8vffhY4R9ayQ+FHvESSeMqavWUEE31eZLjxeQ71QbexVlHrq//iuLonGaUidmv/ Jz0/W5NNNAvRuzjsQYFo5qySG8CV/pfkU560NMsGoj4wKhxHrnJLiPDceDInz8za iKK1RjIC6EObfwt2AYNHkDKsqT8sDs19DqckQLGIW26jz5zKS3Fhjp7cPc0D6v0u VtvM1CIEsrgd0jrM3prIt3IDYPbrkg/KWKdjTUMQXMgWbcFZgt5z86oW93C/qSOb /rJf/vFet9TD41+JzStTzmMKjwsgNJTsiGEC/JZ2fpy/y7oFTexzGq7BNwDpM8Ts LfOZMCO1NhjsEZxOep+A =uhib -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629100: Status update
On Wed, Aug 17, 2011 at 15:28, Jelmer Vernooij jel...@samba.org wrote: Which headers are necessary? Here are the header files that are #included by winexe source files but which I couldn't find in the -dev packages. * includes.h = source4/include/includes.h * libcli/libcli.h = source4/libcli/libcli.h * libcli/raw/raw_proto.h = bin/default/source4/libcli/raw/raw_proto.h * libcli/resolve/resolve.h = source4/libcli/resolve/resolve.h * libcli/smb_composite/smb_composite.h = source4/libcli/smb_composite/smb_composite.h * lib/events/events.h = source4/lib/events/events.h * system/filesys.h = lib/replace/system/filesys.h These header files #include others. Results of a quick grep: #include libcli/libcli_proto.h #include ../libcli/nbt/libnbt.h #include libcli/raw/libcliraw.h #include libcli/raw/signing.h #include libcli/resolve/lp_proto.h #include libcli/resolve/proto.h #include libcli/smb2/smb2.h #include libcli/smb_composite/proto.h #include libcli/util/error.h #include librpc/gen_ndr/nbt.h #include ../lib/util/attr.h #include ../lib/util/debug.h #include ../lib/util/safe_string.h #include ../lib/util/smb_threads.h #include ../lib/util/smb_threads_internal.h #include ../lib/util/util.h #include ../lib/util/xfile.h #include ../replace/replace.h #include system/locale.h #include system/time.h #include system/wait.h and these, in turn, will #include others Alternatively, you should be able to use svcctl from Python rather than from C. The svcctl python module is included in the python-samba package already. Interesting idea! Given that winexe has to be built against the samba source tree, I think it's best if we try to get winexe included in Samba 4. This doesn't seem likely given winexe is quite hard to build - it requires mingw32. Building the winexesvc.exe Windows binary does require mingw (specifically, /usr/bin/i586-mingw32msvc-gcc and /usr/bin/amd64-mingw32msvc-gcc from the gcc-mingw32 package). Given that winexe would be the only component of Samba with this requirement, it would be sensible for upstream to make winexe an optional component, built conditionally upon waf being given --with-winexe or something like that. But this shouldn't be an issue for Debian which introduced gcc-mingw32 in squeeze. Are there any difficulties beyond that? Probably some things would have to be changed to follow Samba coding style, but that would not be much work. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#629100: Status update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/08/11 17:10, Thomas Hood wrote: On Wed, Aug 17, 2011 at 15:28, Jelmer Vernooij jel...@samba.org wrote: Which headers are necessary? Here are the header files that are #included by winexe source files but which I couldn't find in the -dev packages. * includes.h = source4/include/includes.h * libcli/libcli.h = source4/libcli/libcli.h * libcli/raw/raw_proto.h = bin/default/source4/libcli/raw/raw_proto.h * libcli/resolve/resolve.h = source4/libcli/resolve/resolve.h * libcli/smb_composite/smb_composite.h = source4/libcli/smb_composite/smb_composite.h * lib/events/events.h = source4/lib/events/events.h * system/filesys.h = lib/replace/system/filesys.h Have you verified that these headers are actually necessary? None of these should strictly be necessary for the stuff that winexe is trying to do. Is the source as you currently have it available somewhere? Cheers, Jelmer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJOS+KDAAoJEACAbyvXKaRXGV8P/2ObUP2VkmY4T6pcUv1YgRO7 7og/aRUgNGF4ogD49fpo9w2KDcLIS26oPjAQH9r6SMl1Y6tzhrB8Q0Npi/IOu7Gb pPJn6pbskMrUW1uv7NuwxfOrv9HTEKgrkLNlIc0l/FFjBn6PedG4E/qZbssVTUM2 GosAstv76XxZqT5fahsi+VbuJtHEmH4UzjB+yj/uBaB4JvtxZdTyZ3EenZTz19v0 CI40QT3sg8Yu2pJ7SHU8yTh0U+cFDtgLnozMRC9XKFxO3exZZ2P9ccpXG9qBkgLx GwJRSzQGPasIhq8d5ZGkY590fnzT6Cfyay+f68yl7xGdW2SUqBWm7+qPs9RxUswR 8JIB1pbkar7d1JuolQSzsp5P1dxMimIKeKfiEursNch0qgd2UYEvOtf+VwUQXxKN LjMeOvE/ixoTWCl3AqrWq/YSIHKsZ70bnABy/WDdL4U4zreuV3z0Ea3FW7PJ7VAX WUXEkPTdGQw4arzVxOgyHkNx5omowgkvC8iY6oV5R0CwWBb5xh6Xfd4UuRVcooTD 5+IesAPrV0ctpB3h7KJLHT7ss3KfCfkN6+SD5CSKWmprv81Z7rgRjN6qEbYxgtxN 2yFo3as22aUTN9TSGws6kHIZXkQoUDnS9LNaO5USf4dhorS7dewk1i5APfFzHCsO 0dA5o+/Z8AvzIpt+eUwX =9vaw -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
