On Tue, Aug 01, 2006 at 07:20:31PM +0200, Daniel Holbach wrote:
thanks Bart for CCing me. It'd be nice to have libnet-dbus-perl in
Debian too. So if you want to take over maintenance, I'm only too happy.
I packaged it because system-tools-backends (part of the
gnome-system-tools stack) uses
On Mon, Jun 12, 2006 at 11:44:43PM +0100, Stephen Gran wrote:
You have dh-make-perl cruft in debian/rules, copyright and control -
please fix those up. This is mostly harmless boilerplate and extra
comments that aren't needed, but I like to see all the files have what
you need and no more.
On Sat, Jun 10, 2006 at 12:50:49PM +0100, Stephen Gran wrote:
Can you tell me where it was downloaded from? I prefer to test against
the upstream tarball. I am somewhat interested in this, a I would like
to be able to script some dbus queries for desktop use, and this seems
like a
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=292684
http://cgi.sfu.ca/~jdbates/debian/pool/libnet-dbus-perl/
Net::DBus provides a Perl API for the DBus message system.
The DBus Perl interface is currently operating against
the 0.32 development version of DBus, but should work with
later
On Apr 23, 2005, at 7:46 AM, Andreas Barth wrote:
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) [050412 08:00]:
On Apr 11, 2005, at 3:09 AM, Andreas Barth wrote:
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) [050411 04:10]:
Both Chad I really look forward to making this package part of
Debian
On Apr 17, 2005, at 6:04 PM, Craig Small wrote:
On Mon, Apr 11, 2005 at 10:56:16PM -0700, [EMAIL PROTECTED] wrote:
Both Chad I really look forward to making this package part of
Debian
- please consider sponsoring it : )
What's happened to the website for the project? It's still down.
Yeah - it's
On Apr 11, 2005, at 3:09 AM, Andreas Barth wrote:
Hi,
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) [050411 04:10]:
Both Chad I really look forward to making this package part of
Debian
- please consider sponsoring it : )
Actually, I would really like to sponsor this package. However, on a
first
PHP iCalendar is based on v2.0 of the IETF specification. It displays
iCal/vCalendar files in a nice logical clean manner with day, week,
month, year navigation. It is available in 13 languages includes
support for printing, searching, RSS news feeds.
Supported applications include Apple
On Jan 16, 2005, at 1:40 PM, Ghe Rivero wrote:
El dom, 16-01-2005 a las 10:40 -0800, [EMAIL PROTECTED] escribió:
Yo, I hadn't been following your work on an Apache2 package. Please
let
me know if I can help.
Just take a look to my solution and see what of yours can be added or
changed to
Yo, I hadn't been following your work on an Apache2 package. Please let
me know if I can help.
Regards,
Jack
Just take a look this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=264231
Since libapache-* and libapache2-* share exactly the same code, it
should be a a multibinary source package.
mod-auth-kerb is a terrific Apache module to authenticate connections
using Kerberos; it even supports GSSAPI negotiation (SPNEGO) - ie.
single sign on authentication using Apache2 Kerberos!
I repackaged mod-auth-kerb for Apache2 added some more documentation:
Why is debhelper using debian/tmp/ as build directory, instead of
debian/package/?
The debhelper documentation agrees with my experience, that it uses
debian/package/ by default, but one of my packages is using
debian/tmp/, without -P or --tmpdir options anywhere. Has anyone
else
On Oct 28, 2004, at 9:06 AM, Sven Mueller wrote:
Adrian 'Dagurashibanipal' von Bidder [u] wrote on 28/10/2004 11:02:
[EMAIL PROTECTED]:
If a package creates a user when it is installed, should it remove
this
user when it is removed, on only when it is purged?
I think not removing the user is the
How to use variables in postinst scripts?
Currently, I use a variable for the upstream version with these lines
in debian/rules:
[...]
# Get the upstream version from the changelog.
upstream := $(shell head -1 debian/changelog | sed
's/^.*(\(.*\)-.*).*$$/\1/')
[...]
install -o root -g root
On Oct 28, 2004, at 9:06 AM, Sven Mueller wrote:
Adrian 'Dagurashibanipal' von Bidder [u] wrote on 28/10/2004 11:02:
[EMAIL PROTECTED]:
If a package creates a user when it is installed, should it remove
this
user when it is removed, on only when it is purged?
I think not removing the
How to use variables in postinst scripts?
Currently, I use a variable for the upstream version with these lines
in debian/rules:
[...]
# Get the upstream version from the changelog.
upstream := $(shell head -1 debian/changelog | sed
's/^.*(\(.*\)-.*).*$$/\1/')
[...]
If a package creates a user when it is installed, should it remove this
user when it is removed, on only when it is purged?
I couldn't find this topic in either the Policy Manual or Developers
Reference.
I did find some interesting information about packages creating
removing users, but it
I am packaging a package - A - which conflicts with only some files in
another package - B - (A depends on the rest of B's files). If A also
contained the files in B with which it conflicts, I think I would tag A
Replaces: B and be done; but A doesn't contain these files, it simply
conflicts
I am packaging a package - A - which conflicts with only some files in
another package - B - (A depends on the rest of B's files). If A also
contained the files in B with which it conflicts, I think I would tag A
Replaces: B and be done; but A doesn't contain these files, it simply
conflicts
I sent this message to the sasl2-bin package maintainer, but I suspect
he's really busy. I haven't received a response.
I'm not sure whether to open a bug, because I don't understand the
problem. I can't reproduce the problem with the sasl2-bin binary
package, compiling the source package on
On Jul 1, 2004, at 11:50 PM, Andreas Metzler wrote:
On 2004-07-02 [EMAIL PROTECTED] wrote:
[...]
I've tried for many months to get saslauthd working with PAM - I
happen to use the pam_krb5 module. Now it's working when I build it
myself - but I don't know why. I have a pretty stock
On Jul 1, 2004, at 11:50 PM, Andreas Metzler wrote:
On 2004-07-02 [EMAIL PROTECTED] wrote:
[...]
I've tried for many months to get saslauthd working with PAM - I
happen to use the pam_krb5 module. Now it's working when I build it
myself - but I don't know why. I have a pretty stock installation of
I sent this message to the sasl2-bin package maintainer, but I suspect
he's really busy. I haven't received a response.
I'm not sure whether to open a bug, because I don't understand the
problem. I can't reproduce the problem with the sasl2-bin binary
package, compiling the source package on
How do I invoke make-kpkg to cross compile a kernel for powerpc?
I've built and installed gcc-3.3-powerpc-linux. I tried make-kpkg
--revision 200406241 --rootcmd fakeroot --arch powerpc kernel_image,
without success. Apparently the Specified GNU system type
powerpc-linux does not match gcc
How do I invoke make-kpkg to cross compile a kernel for powerpc?
I've built and installed gcc-3.3-powerpc-linux. I tried make-kpkg
--revision 200406241 --rootcmd fakeroot --arch powerpc kernel_image,
without success. Apparently the Specified GNU system type
powerpc-linux does not match gcc
I am packaging source which builds two binary packages; however, each
package has different build dependancies. In fact, the packages' build
dependancies conflict.
I don't think the dpkg tools have the facility to build one binary but
not the other. Nor do I think one can specify different
I am packaging source which builds two binary packages; however, each
package has different build dependancies. In fact, the packages' build
dependancies conflict.
I don't think the dpkg tools have the facility to build one binary but
not the other. Nor do I think one can specify different
My problem is really starting an arbitrary number...
Perhaps I am guilty of some abuse of language; sorry. There is only one
daemon, which I am trying to start an arbitrary number of copies of,
with an arbitrary number of - possibly - different options. I'd like to
be able to do something
My problem is really starting an arbitrary number...
Perhaps I am guilty of some abuse of language; sorry. There is only one
daemon, which I am trying to start an arbitrary number of copies of,
with an arbitrary number of - possibly - different options. I'd like to
be able to do something
The skeleton init.d file is a great default for starting _one_
daemon, complete with the $DAEMON_OPTS variable. It's not clear,
however, what this newbie package developer should do to start an
arbitrary number of daemons, each with - potentially - different
$DAEMON_OPTS.
It's nice to be
30 matches
Mail list logo
