[EMAIL PROTECTED] said:
>> Should I sign his key ?
>
> No. Request that he adds an UID to his key with his name as it appears on
> his documents (the name that he would have in a international travel pass,
> for example), and sign THAT UID (and any others you have verified to be
> completely true)
[EMAIL PROTECTED] said:
>> Should I sign his key ?
>
> No. Request that he adds an UID to his key with his name as it appears on
> his documents (the name that he would have in a international travel pass,
> for example), and sign THAT UID (and any others you have verified to be
> completely true
I have a postinst that does the following:
# get settings from debconf
. /usr/share/debconf/confmodule
db_get pure-ftpd/standalone-or-inetd
SOI="$RET"
db_get pure-ftpd/ftpwho-setuid
SUID="$RET"
db_stop
later, it calls update-inetd, which may
I have a postinst that does the following:
# get settings from debconf
. /usr/share/debconf/confmodule
db_get pure-ftpd/standalone-or-inetd
SOI="$RET"
db_get pure-ftpd/ftpwho-setuid
SUID="$RET"
db_stop
later, it calls update-inetd, which ma
[EMAIL PROTECTED] said:
>> I'm packaging a program for multiple distributions that build-depends on
>> autoconf 2.50. [...]
>
> You might better avoid this if you can. Packages made by autoconf do
> not usually depend on autoconf for the build, that's why the configure
> script is shipped within t
[EMAIL PROTECTED] said:
>> I'm packaging a program for multiple distributions that build-depends on
>> autoconf 2.50. [...]
>
> You might better avoid this if you can. Packages made by autoconf do
> not usually depend on autoconf for the build, that's why the configure
> script is shipped within
I'm packaging a program for multiple distributions that build-depends on
autoconf 2.50. Obviously I have to patch the configure.in to make the
package build on potato; this isn't a problem. And sid uses autoconf
2.50 by default so it's also not a problem. But I was wondering when I
can expect autoc
I'm packaging a program for multiple distributions that build-depends on
autoconf 2.50. Obviously I have to patch the configure.in to make the
package build on potato; this isn't a problem. And sid uses autoconf
2.50 by default so it's also not a problem. But I was wondering when I
can expect auto
[EMAIL PROTECTED] said:
>> Is there a way to have debhelper do that? Or should I just not be using
>> debhelper for this and put correct code in the postinst myself?
> You could add it yourself and use dh_installinit -n, that's what I did for
> xinetd. Or try what Itai suggested.
Itai's suggestion
[EMAIL PROTECTED] said:
>> Is there a way to have debhelper do that? Or should I just not be using
>> debhelper for this and put correct code in the postinst myself?
> You could add it yourself and use dh_installinit -n, that's what I did for
> xinetd. Or try what Itai suggested.
Itai's suggestio
[EMAIL PROTECTED] said:
>> This is weird, because the only thing left in the postinst is:
>> [orr](0) % tail /var/lib/dpkg/info/pure-ftpd.postinst
>> # End automatically added section
>> # Automatically added by dh_installinit
>> if [ -e "/etc/init.d/pure-ftpd" ]; th
[EMAIL PROTECTED] said:
> When I installed pure-ftpd_0.98.4-1_i386.deb , at the end of the
> install pure-ftpd said "Starting ftp server: pure-ftpd" and nothing
> else happened, i.e. I do not have the prompt, "enter" do not give me
> the prompt.If I do a ps I cans see that perl and debconf are stil
[EMAIL PROTECTED] said:
>> This is weird, because the only thing left in the postinst is:
>> [orr](0) % tail /var/lib/dpkg/info/pure-ftpd.postinst
>> # End automatically added section
>> # Automatically added by dh_installinit
>> if [ -e "/etc/init.d/pure-ftpd" ]; t
[EMAIL PROTECTED] said:
> When I installed pure-ftpd_0.98.4-1_i386.deb , at the end of the
> install pure-ftpd said "Starting ftp server: pure-ftpd" and nothing
> else happened, i.e. I do not have the prompt, "enter" do not give me
> the prompt.If I do a ps I cans see that perl and debconf are sti
14 matches
Mail list logo
