Hi
I'm trying to setup ldap/sasl/php to enable modification of an ldap
record from a php web page
Do you have a simple example able to do this
and what i should do in all the config files
I don't want to install kerberos
I would like to use SASL authentication.
How to create a user/credential tha
On Thu, Sep 06, 2001 at 04:00:25PM +0200, peter karlsson wrote:
> Colin Watson:
>
> > If you can't build the Debian package as part of the process of
> > generating the tarball from CVS, I suppose you could use -b and hack the
> > .changes by hand to include the source, although that's rather ugly
On Thu, Sep 06, 2001 at 02:07:35PM +0200, peter karlsson wrote:
> I *could* do that, but that would still not solve the problem of the
> files in the tarball being owned by peter/users instead of
> root/root, as the tarball I build now is.
If you *really* want the files to be root/root (why?), the
On Thu, Sep 06, 2001 at 04:00:25PM +0200, peter karlsson wrote:
> Colin Watson:
>
> > If you can't build the Debian package as part of the process of
> > generating the tarball from CVS, I suppose you could use -b and hack the
> > .changes by hand to include the source, although that's rather ugl
Hi,
Thanks everyone for your answers!
Since I wasn't counting on making it into the current frozen, and there
isn't a great many people asking for kvirc to be part of stable, I am not in
a great hurry to make that happen. I was just wondering whether it required
any special effort on my part to g
On Thu, Sep 06, 2001 at 02:07:35PM +0200, peter karlsson wrote:
> I *could* do that, but that would still not solve the problem of the
> files in the tarball being owned by peter/users instead of
> root/root, as the tarball I build now is.
If you *really* want the files to be root/root (why?), th
Hi,
Thanks everyone for your answers!
Since I wasn't counting on making it into the current frozen, and there
isn't a great many people asking for kvirc to be part of stable, I am not in
a great hurry to make that happen. I was just wondering whether it required
any special effort on my part to
peter karlsson:
> Santiago Vila:
>
> > Oops! I understand. My suggestion is that you arrange things so that
> > dpkg-buildpackage creates the one and only source tarball, instead of
> > creating it in advance by hand.
>
> I *could* do that, but that would still not solve the problem of the files
>
Robin <[EMAIL PROTECTED]> writes:
> What are the conditions for a package to be included in stable?
You can't get your package into the current stable (potato) unless it
is tremendously important, and another point release is made. So I'll
assume your talking about the next stable release (woody)
* peter karlsson
| Colin Watson:
|
| > If you can't build the Debian package as part of the process of
| > generating the tarball from CVS, I suppose you could use -b and hack the
| > .changes by hand to include the source, although that's rather ugly.
|
| I tried hacking the changes file by ha
On Thu, Sep 06, 2001 at 03:47:15PM +0200, Martin F Krafft wrote:
> awesome! i attached it because my debian server is currently
> inconsistent as it's being rsync'd through 64kbit/s isdn, which si
> *darn* slow. hope this is fine...
I'll sponsor Martin - I've taken the rest of this conversation to
Colin Watson:
> If you can't build the Debian package as part of the process of
> generating the tarball from CVS, I suppose you could use -b and hack the
> .changes by hand to include the source, although that's rather ugly.
I tried hacking the changes file by hand, but my upload got rejected th
Robin schrieb:
> What are the conditions for a package to be included in stable?
> I have looked through the policy document to find any clues on this but
> I couldn't find anything.
It's actually quite well described...
An existing "stable" will only be changed for security and critical updates.
also sprach Colin Watson (on Wed, 05 Sep 2001 06:55:36PM +0100):
> Ah, and if you can ask for no bandwidth restrictions then you can do
> easy port forwarding without ssh too. Cool ... I'll sponsor you if you
> like. Send me the URL to your Debianized source package.
awesome! i attached it because
On Wed, Sep 05, 2001 at 10:49:51PM +0200, peter karlsson wrote:
> How do I get dpkg-buildpackage not to re-build the source tarball when
> building a native package? No matter what I do, it rebuilds it, which
> prevents me from keeping the tarball I created from my CVS tree, which
> also is what I
peter karlsson:
> Santiago Vila:
>
> > Oops! I understand. My suggestion is that you arrange things so that
> > dpkg-buildpackage creates the one and only source tarball, instead of
> > creating it in advance by hand.
>
> I *could* do that, but that would still not solve the problem of the files
>
On Wed, Sep 05, 2001 at 07:19:27PM -0600, Robin wrote:
> Hi,
>
> What are the conditions for a package to be included in stable?
> I have looked through the policy document to find any clues on this but
> I couldn't find anything.
>
that happens automatically when a freeze takes place, your packag
Robin <[EMAIL PROTECTED]> writes:
> What are the conditions for a package to be included in stable?
You can't get your package into the current stable (potato) unless it
is tremendously important, and another point release is made. So I'll
assume your talking about the next stable release (woody
Santiago Vila:
> Including MSWIN and OS/2 specific stuff in a Debian source tarball
> should not be a problem.
Well, the packages structure are different on the different platforms, and
also my MSWIN/OS2 source packages also contain binaries, plus that the
source is CRLF formatted there, and that
Santiago Vila:
> Oops! I understand. My suggestion is that you arrange things so that
> dpkg-buildpackage creates the one and only source tarball, instead of
> creating it in advance by hand.
I *could* do that, but that would still not solve the problem of the files
in the tarball being owned by
* peter karlsson
| Colin Watson:
|
| > If you can't build the Debian package as part of the process of
| > generating the tarball from CVS, I suppose you could use -b and hack the
| > .changes by hand to include the source, although that's rather ugly.
|
| I tried hacking the changes file by h
Colin Watson:
> If you can't build the Debian package as part of the process of
> generating the tarball from CVS, I suppose you could use -b and hack the
> .changes by hand to include the source, although that's rather ugly.
I tried hacking the changes file by hand, but my upload got rejected t
Robin schrieb:
> What are the conditions for a package to be included in stable?
> I have looked through the policy document to find any clues on this but
> I couldn't find anything.
It's actually quite well described...
An existing "stable" will only be changed for security and critical updates.
also sprach Colin Watson (on Wed, 05 Sep 2001 06:55:36PM +0100):
> Ah, and if you can ask for no bandwidth restrictions then you can do
> easy port forwarding without ssh too. Cool ... I'll sponsor you if you
> like. Send me the URL to your Debianized source package.
awesome! i attached it becaus
I said:
> peter karlsson wrote:
> > so I don't want dpkg-buildpackage to overwrite it.
> Why does dpkg-buildpackage overwrite it? [...]
Oops! I understand. My suggestion is that you arrange things so that
dpkg-buildpackage creates the one and only source tarball, instead of
creating it in advance
peter karlsson wrote:
> Santiago Vila:
> > I would first create the Debian source and binary packages for upload,
> > and then distribute the resulting tar.gz elsewhere, in that order.
>
> The problem is that I am generating the tar from my CVS (not all of the CVS
> is exported, there are some MSWI
Santiago Vila:
> I would first create the Debian source and binary packages for upload,
> and then distribute the resulting tar.gz elsewhere, in that order.
The problem is that I am generating the tar from my CVS (not all of the CVS
is exported, there are some MSWIN and OS/2 specific stuff there
Mike Markley:
> You probably don't want to do this... since a native package has no
> .diff.gz, the source tarball must contain everything used to generate the
> set of binary packages you're uploading.
It does, I just untarred it to a directory and ran dpkg-buildpackage there.
I don't wnat dpkg-
On Wed, Sep 05, 2001 at 07:19:27PM -0600, Robin wrote:
> Hi,
>
> What are the conditions for a package to be included in stable?
> I have looked through the policy document to find any clues on this but
> I couldn't find anything.
>
that happens automatically when a freeze takes place, your packa
On Wed, Sep 05, 2001 at 07:19:27PM -0600, Robin wrote:
> What are the conditions for a package to be included in stable?
> I have looked through the policy document to find any clues on this but
> I couldn't find anything.
>
> Currently, I maintain the kvirc (and kvirc-doc, kvirc-dev) packages
> w
Santiago Vila:
> Including MSWIN and OS/2 specific stuff in a Debian source tarball
> should not be a problem.
Well, the packages structure are different on the different platforms, and
also my MSWIN/OS2 source packages also contain binaries, plus that the
source is CRLF formatted there, and tha
Santiago Vila:
> Oops! I understand. My suggestion is that you arrange things so that
> dpkg-buildpackage creates the one and only source tarball, instead of
> creating it in advance by hand.
I *could* do that, but that would still not solve the problem of the files
in the tarball being owned by
I said:
> peter karlsson wrote:
> > so I don't want dpkg-buildpackage to overwrite it.
> Why does dpkg-buildpackage overwrite it? [...]
Oops! I understand. My suggestion is that you arrange things so that
dpkg-buildpackage creates the one and only source tarball, instead of
creating it in advance
peter karlsson wrote:
> Santiago Vila:
> > I would first create the Debian source and binary packages for upload,
> > and then distribute the resulting tar.gz elsewhere, in that order.
>
> The problem is that I am generating the tar from my CVS (not all of the CVS
> is exported, there are some MSW
Santiago Vila:
> I would first create the Debian source and binary packages for upload,
> and then distribute the resulting tar.gz elsewhere, in that order.
The problem is that I am generating the tar from my CVS (not all of the CVS
is exported, there are some MSWIN and OS/2 specific stuff there
Mike Markley:
> You probably don't want to do this... since a native package has no
> .diff.gz, the source tarball must contain everything used to generate the
> set of binary packages you're uploading.
It does, I just untarred it to a directory and ran dpkg-buildpackage there.
I don't wnat dpkg
36 matches
Mail list logo
