Bug#180634: [Kolab-devel] Debian Kolab packages
Op zaterdag 4 februari 2006 14:45, schreef Noèl Köthe: we are happy to announce the Debian Kolab (www.kolab.org) packages: http://pkg-kolab.alioth.debian.org/ We built these packages for one of our customer at work (www.credativ.de) and are happy to give the work completly to Debian and the users. The reason why we don't use the upstream openpkg system is, that we love the Debian package management and don't want to administrate a second package system (openpkg) in the Debian one. See http://wiki.kolab.org/index.php/Kolab2_linux_distribution_integration We will finalize these packages and will then beginn to upload them to experimental. From what I saw from the svn repository, is that you patched quite some files to get this working isn't it? The steps are: 1. add deb http://pkg-kolab.alioth.debian.org/experimental-packages/ ./ to your sources.list 2. apt-get update; apt-get install kolabd 3. Read http://svn.debian.org/wsvn/pkg-kolab/trunk/kolabd/debian/README.Debian?op=f ilerev=0sc=0 4. Tell us problems, bugs, suggestions on our mailinglist http://lists.alioth.debian.org/mailman/listinfo/pkg-kolab-devel Why didn't you use the dist_conf method, just specify all paths and files in http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/dist_conf/debian?rev=1.4content-type=text/vnd.viewcvs-markup and make (actually./configure) kolab with --with-dist=debian --without-openpkg. Now you ontain kolab without need to patch it :) For suse this works now, I guess for debian most of it will work as well. If not the code should be adapted for it (if possible). With the dist_conf method you're also getting the possibility to access kolab at e.g. https://fqdn/kolab/admin iso just https://fqdn/admin. -- Richard Bos Without a home the journey is endless
Bug#297439: run netselect as user
Package: netselect Version: 0.3-4 Severity: wishlist I use netselect version 0.2 already for quite some time on my suse systems and I'm happy with it. As such I adviced suse to have netselect included. Suse is not just picking up the package as netselect can run by root only, or has this changed since version 0.2? Suse is reluctant to include netselect, as they have a traceroute version that can be run by ordinary users and for this reason they expect netselect to be able to run by ordinary users as well. Perhaps can you have a look at suse's traceroute implementation to make netselect capable to be run by ordinary users too? The suse traceroute src rpm can be found at: ftp://ftp.gwdg.de/pub/linux/suse/apt/SuSE/9.2-i386/SRPMS.base/net-tools-1.60-551.src.rpm On Sun, Feb 27, 2005 at 09:44:46PM +0100, Richard Bos wrote: [snip] Suse is reluctant to include netselect, as they have a traceroute version that can be run by ordinary users and for this reason they expect netselect to be able to run by ordinary users as well. Perhaps can you have a look at suse's traceroute implementation to make netselect capable to be run by ordinary users too? thanks for your suggestion, I'll give suse's traceroute a look and see it I can change the relevant code for netselect! filippo -- Richard Bos Without a home the journey is endless -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
