Hi, > Hi everybody. [...] > So I cleaned the packages, and now, by this mail, I'm releasing them.
As I answer you in the Debian bug report where you just post your message, I've been working on a Debian packaging since a few weeks. > Packages are available the following versions of Debian and Ubuntu : [...lots of releases...] My goal is to introduce owfs in Debian itself. I'm already a DD, so I will not have any problem to upload the packages. They will be available in sid and they will propagate to testing, stable and ubuntu more or less quickly. Of course, it will be possible to create backport of the packages so they will available for Squeeze (or other current Ubuntu release) > So now, some explanation about the packages. > > For the moment, I do not package owperl, owmon, owtap, owphp, owcapi, > owpython, owtcl , owftpd and owhttpd. Their are ready in my packaging > Here is the packages list (available in versions 2.8p6 and 2.8p7 if not > indicated) : > - owfs-common : contains the /etc/owfs.conf file, and the manpage same for me > - owfs-server : contains the /usr/sbin/owserver binary (originally in > /usr/bin, but I moved it in the package, because of the Debian Policy > requirements), the manpage and the init.d script package called owserver for me. But I let owserver in /usr/bin : why do you think that owserver whould only run by root ? To which Debian Policy requirement are you thinking ? > - owfs (only 2.8p7) : contains the /usr/sbin/owfs binary, to use with > fuse (originally in /usr/bin, but I moved it in the package, because of > the Debian Policy requirements), the manpage and the init.d script called owfs-fuse. And owfs is an empty meta-package depending on owfs-fuse, owserver, owhttpd and owftpd. Here again, I do not see which Debian Policy requirements is asking you to move the owfs to /usr/sbin (as it is a fuse helper, it can be ok) > - owfs-client : contains de client tools (owdir, owpresent, owread, > owwrite and owread), with the manpages associated. called ow-shell (and I added owtap and owmon for now) > - libow-2.8-7 (only 2.8p7) : contains the libow for version 2.8p7 > - libow-2.8-6 (only 2.8p6) : contains the libow for version 2.8p6 Idem But also libowcapi-2.8-7 for libowcapi > - owfs-dev : contains the file /usr/include/owfs_config.h contains developments files (.so link, includes, manpages, examples) for libow and libowcapi > - owfs-doc : contains all the remaining manpages same for me (ie all DS*.3 manpages, ...) > - owfs-dbg : contains the debugging symbols idem But also: libownet-2.8-7 : libownet libownet-dev : devel files (headers, .so link, manpages and examples) for libownet libow-php5: php5 bindings to libow/libowcapi libownet-php: php bindings to libownet/owserver libow-perl: perl bindings to libow/libowcapi libownet-perl: perl bindings to libownet/owserver python-ow: python bindings to libow/libowcapi python-ownet: python bindings to libownet/owserver libow-tcl: tcl bindings to libow/libowcapi > I would like to thank Paul Alfille for his work on OWFS, and all the > other contributors for their respective work. I can only say "me too" ;-) > Also, I had to patch the sources for having full compliance to the > Debian Policy, Paul, I will mail you later today or tomorrow to share > these patches. > > If you detect any problem, feel free to mail me, or mail the mailing list. As I told you in the BTS, I would welcome any co-maintainer for the official Debian package. Looking at your site, I can only see the binary packages. The source package would be more interesting. All my packaging work is available here: http://git.debian.org/?p=collab-maint/owfs.git;a=summary I still have a few issues left before uploading my package. Lintian tell me: W: libow-php5: postinst-has-useless-call-to-ldconfig W: libow-php5: postrm-has-useless-call-to-ldconfig W: libownet-perl: manpage-has-bad-whatis-entry usr/share/man/man3/OWNet.3pm.gz W: libow-tcl: postinst-has-useless-call-to-ldconfig W: libow-tcl: postrm-has-useless-call-to-ldconfig W: owfs-doc: manpage-has-bad-whatis-entry usr/share/man/man3/EDS.3.gz And there is a TODO in the debian/ subdirectory. For owfs upstream (mainly Paul if I follow correctly), I think you will be interested by some of the patches I apply. All my patches can be seen here: http://git.debian.org/?p=collab-maint/owfs.git;a=tree;f=debian/patches;hb=master but I will made several separate messages when the packages will be fully ready for each of the issue (some patches are very debian specific and should probably not be applied upstream as they are). Regards, Vincent > Thanks. > > -- > Cyril LAVIER | Systems Administrator | LTU Technologies > 132 Rue de Rivoli - 75001 Paris France > (tel) +33 (0)1 53 43 01 71 | (mail) clav...@ltutech.comh > > > LTU technologies - Making Sense of Visual Content | http://www.LTUtech.com > -- Vincent Danjean GPG key ID 0x9D025E87 vdanj...@debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial packages: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
