RFS: phpgroupware
Dear mentors, I am looking for a sponsor for the package phpgroupware. * Package name: phpgroupware Version : 1:0.9.16.012+dfsg-1 Upstream Author : Multiple authors of the phpGroupware.org project + FSF (part of the GNU project) * URL : www.phpgroupware.org * License : Most under GNU GPL Section : web It builds these binary packages: phpgroupware - Web based groupware system written in PHP phpgroupware-0.9.16 - Web based groupware system written in PHP phpgroupware-0.9.16-addressbook - phpGroupWare addressbook management module phpgroupware-0.9.16-admin - phpGroupWare administration module phpgroupware-0.9.16-calendar - phpGroupWare calendar management module phpgroupware-0.9.16-core - Core applications of a groupware system based on phpGroupware phpgroupware-0.9.16-core-base - Base components of the phpGroupware application server phpgroupware-0.9.16-doc - Web based groupware system written in PHP phpgroupware-0.9.16-email - phpGroupWare E-Mail client module phpgroupware-0.9.16-filemanager - phpGroupWare filemanager module phpgroupware-0.9.16-manual - phpGroupWare on-line manual module phpgroupware-0.9.16-notes - phpGroupWare notes management module phpgroupware-0.9.16-phpgwapi - library of common phpGroupWare functions phpgroupware-0.9.16-preferences - phpGroupWare preferences management module phpgroupware-0.9.16-setup - phpGroupWare setup III module phpgroupware-0.9.16-todo - phpGroupWare todo list management module The upload would fix these bugs: 464014 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/phpgroupware - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/phpgroupware/phpgroupware_0.9.16.012+dfsg-1.dsc Note that this package is still in stable, but was removed from the distribution recently since maintainer was MIA. More details on the history of the package in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464014 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=453467 This explains why I changed epoch. The binary packages are not as numerous as the ones in he previous package, in order to limit the amount of unmaintained or difficult to maintain code. More details are provided in the enclosed README.Debian files. Note that the binary packages contain 0.9.16 in order to prepare for potential release of phpGroupware 0.9.18 (upstream is optimistic on stabilization ofa release soon) and a coexistence period of both versions in Debian. The package's scripts or patches were not touched compared to previous packaging, and only the build process was changed to produce a different binary packages layout. Also we intend to do collaborative maintenance on the package (together with Christian Bac, in CC:, and any other volunteers), so we hope to be able to use alioth resources maybe. We hope this will help solve some of the problems that occurred on previous packaging of the software. For the records, I have no formal past track record as Debian maintainer, but I have been involved in producing local unofficial packages for our PicoForge software (www.picoforge.org), together with Christian, and am also contributing to testing and fixing bugs on the (official) Sympa package, trying to help its maintainer (racke). Besides that I'm also a Debian fan, and the BTS knows me ;) Btw, I may meet some of you this weekend at the FOSDEM, where it may be more convenient to discuss packaging of phpGroupware. Kind regards Olivier Berger -- Olivier BERGER [EMAIL PROTECTED] (*NEW ADDRESS*) http://www-inf.it-sudparis.eu/~olberger/ - OpenPGP-Id: 1024D/6B829EEC Ingénieur Recherche - Dept INF Institut TELECOM / TELECOM Management SudParis (http://www.it-sudparis.eu/), Evry signature.asc Description: Ceci est une partie de message numériquement signée
Apache umask
Hi all, I am thinking of packaging an application that provides both a web interface (via apache) and a command line interface. This means that both the www-data and the user running the command line interface need write access to the data directories (/var/lib/package) Furthermore new files can be created in this directory by both interfaces. To avoid permission problems it would seem I need to create a new group, add the www-data to it and set the apache umask to 002. I am thinking about doing this by modifying /etc/default/apache2 from my posinst script. Is this allowed ? (this file is _not_ a conffile for apache) If not are there any better ways to do it? Regards, Martin Fuzzey
maintainer script factorization
Hi all, frequently maintainer scripts modify the same files and to avoid duplication of path names etc in all scripts I was wondering if they could be factorized anywhere. The obvious solution of installing something like /usr/share/package/common.sh and sourcing it in the maintainer scripts doesn't work as the package files may already have been removed. Any ideas or is this impossible? Thanks, Martin Fuzzey
Re: Apache umask
Hi, On Friday 22 February 2008, Martin Fuzzey wrote: To avoid permission problems it would seem I need to create a new group, add the www-data to it and set the apache umask to 002. I am thinking about doing this by modifying /etc/default/apache2 from my posinst script. Is this allowed ? (this file is _not_ a conffile for apache) No. You may not change other packages' config files without user interaction, even if they are not conffiles. Besides, /etc/default/apache2 is a conffile in newer versions of apache. And changing apache's umask to make everything group writable is not something that should be done automatically. If not are there any better ways to do it? Change the umask in your application. In most (all?) scripting languages it is possible to do that for one request. Or use suexec or ACLs. Cheers, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: maintainer script factorization
On Fri, Feb 22, 2008 at 07:07:54PM +0100, Martin Fuzzey wrote: Hi all, frequently maintainer scripts modify the same files and to avoid duplication of path names etc in all scripts I was wondering if they could be factorized anywhere. The obvious solution of installing something like /usr/share/package/common.sh and sourcing it in the maintainer scripts doesn't work as the package files may already have been removed. Any ideas or is this impossible? You can include some kind of common script and use .in files parsed as with #DEBHELPER# or such. Perhaps use cpp instead of sed for this, or someone will suggest a better way yet. ./debian/maintscript-common: # Begin debian/maintscript-common shell fragment [...] # End maintscript-common ./debian/postinst.in: #! /bin/sh # Postinstallation script for foo #MAINTSCRIPT-COMMON# [...] ./debian/rules: clean: dh_clean debian/postinst debian/preinst debian/postrm debian/prerm binary: [...] set -e; cd debian; for m in postinst preinst postrm prerm; \ do \ f='maintscript-common'; \ [ ! -e $$m.in ] continue; \ exec $$m.in $$m; \ sed -e s/^#MAINTSCRIPT-COMMON#$$//; T; r $$f; \ done [...] dh_installdeb [...] Colin watson wrote about a scenario where he apparently needed to do this: http://lists.debian.org/debian-devel/2006/12/msg00647.html Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: nettee
On Tue 19 Feb 08 11:46, Cyril Brulebois wrote: On 19/02/2008, Paul Wise wrote: debian/docs: No need to distribute empty files nor a HTML copy of the manual page. As for the HTML copy of the manual page, I wouldn't advise skipping it as a rule of thumb. When it's a long manpage, it might make sense to keep a nice-to-read copy around. I'm also thinking of git manpages, with cross-references and the like, where it's very handy to have them in HTML format. I don't know whether that applies to nettee, though. Hi Cyril, Well, i'll agree now with Paul: nettee is a simple tool that i want to be small and straight. Cheers, -- Cyril Brulebois -- | | Joel Franco Guzmán .''`. | self-powered by : :' : | Debian Linux `. `' | `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: nettee
On Mon 18 Feb 08 13:28, Patrick Schoenfeld wrote: Hi Joel, IANADD, anyways here are some comments about your sponsoring request that might be useful. First of all: On Mon, Feb 18, 2008 at 01:04:48AM -0300, Joel Franco wrote: It builds these binary packages: nettee - a network tee program It would be a good idea to include a long description of the package. Because some DDs say that they won't even consider sponsoring packages, if it is missing. Remember: Your RFS is your advertising of the work you've done. Make it interesting for others. Hi Patrick, A long description is really difficult because the 2 words say all :) I have thinked a lot about it and I' will not add but substract the article, like the your link recomendation. - dget http://mentors.debian.net/debian/pool/main/n/nettee/nettee_0.1.8-3.dsc Now to your package: - debian/changelog General I'm not a fan of multiple changelog entries for one upload, but thats just my opinion. However you should note, that you need to build the package with dpkg-buildpackage -v 0.1.8 so that the other changelog entries get integrated. Otherwise the bug referenced in the first changelog entry (Initial release) will not be closed by the upload. i will do it. - debian/control - lacks a Homepage header to indicate the homepage. See [1] done - Description is not very descriptive. See [2] for some tipps. worked in it too. Is this better now? - debian/copyright - Some copyright holders are missing in that file Sorry. i did not understand. It's the original copyright missing? i have include it. my copyright too? - Its a good idea to include a On Debian systems the license text can be found.. notice to the license of the software, because the link in the packaging is licensed as following-text looks like it *is* for the packaging only on ordinary people IMHO. I have included your text to precede the file location. - debian/dirs is useless. You can change the installation of the binary to be install -D -m755 nettee debian/nettee/usr/bin/nettee and remove both the file and dh_installdirs. done - debian/README.Debian: Hm. I'm unsure if the content is suited for README.Debian. Why? Because it seems like it has no documenting character, more beeing an advertising on how enthusiastic you are about the tool ;) I would like to hear other opinions about this, however. - debian/rules: - configure and configure-stamp target is not required by the policy and you don't need it. so you could remove it. done - you could probably consider adding generating optimized binaries (e.g. -O2)? If you do, please also add support for DEB_BUILD_OPTIONS [3] done - debian/watch is missing, but highly recommended. it enables tracking of new upstream versions via your QA page and even a mail notification if you want. See [4] for more information. I'tried to do it, but i don't have sure that it's correct because it's not clear which data must be in debian/watch. I have included the original upstream version download url. Thats it for now. Feel free to inform me if you did changes on your package and I will have another look at it. Your information is really useful and i'm gladed by your help. Please, look again at my package. Regards, Best Regards, Patrick [1] http://wiki.debian.org/HomepageFieldHOWTO [2] http://www.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-bpp-debian-control [3] http://www.debian.org/doc/debian-policy/ch-files.html [4] http://wiki.debian.org/DEHS -- | | Joel Franco Guzmán .''`. | self-powered by : :' : | Debian Linux `. `' | `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: nettee
On Tue 19 Feb 08 12:47, Paul Wise wrote: On Feb 18, 2008 9:28 PM, Patrick Schoenfeld [EMAIL PROTECTED] wrote: - dget http://mentors.debian.net/debian/pool/main/n/nettee/nettee_0.1.8-3.dsc Some additional comments: Now to your package: - debian/changelog s/rewrited/rewritten/ done - debian/copyright Please move Copyright (C) 2007 David Mathog onto a line on its own and remove the weird angle brackets. done. i've added the other people copyrights. Must i include the mine? The software is GPL2 only, not GPL2 or later. done - debian/README.Debian: Hm. I'm unsure if the content is suited for README.Debian. Why? Because it seems like it has no documenting character, more beeing an advertising on how enthusiastic you are about the tool ;) I would like to hear other opinions about this, however. I agree, perhaps this could be placed in the upstream README? I'm from opinion that this content must be send to the upstream author and, if he find that it must be included in the original content, it will do it. - debian/rules: You don't build it with -D_LARGEFILE64_SOURCE, why is that? It's a bug :) I have added it. It would be good if there were a commented out DH_VERBOSE line in there to enable easy debugging of debian/rules. it's correct now? It would be good if you could write a Makefile with the following targets and send it upstream: all or build, clean, install, dist. Be sure to support CFLAGS, PREFIX and DESTDIR in your Makefile since debian/rules will need them. For extra points it should support checking for solaris and compiling appropriately (see the comments in nettee.c). i will do it slowly and send upstream. - debian/watch is missing, but highly recommended. it enables tracking of new upstream versions via your QA page and even a mail notification if you want. See [4] for more information. debian/docs: No need to distribute empty files nor a HTML copy of the manual page. i have removed the html man file If you want to distribute the pdist scripts, you should at least customize them by using the right path to nettee. You can do this with either sed or a patch system like quilt. i will not distribute it, because they appear to be a author custom scripts useful alone for it. Upstream includes the binary in the tarball, please ask them to fix that. i will do it. Paul, thank you! :) -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- | | Joel Franco Guzmán .''`. | self-powered by : :' : | Debian Linux `. `' | `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
test2
-- | | Joel Franco Guzmán .''`. | self-powered by : :' : | Debian Linux `. `' | `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
test
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
