On Sat, 28 Jan 2006 02:34:47 +0100, Daniel Knabl
<[EMAIL PROTECTED]> wrote:
>Am Fri, 27 Jan 2006 18:08:38 -0500 schrieb [EMAIL PROTECTED]:
>> Nearly all Debian packages should be pristine; if you can do that, you
>> should. If upstream *only* exists in CVS, then you can't really, and
>> you can ru
On Fri, 27 Jan 2006 16:21:47 -0500, [EMAIL PROTECTED] wrote:
>On Fri, Jan 27, 2006 at 10:09:56PM +0100, Daniel Knabl wrote:
>> Sorry, my mistake. I had to remove CVS dirs from the tarball. Now this
>> should be correct.
>Thats not a sufficient reason to repack the tarball; it is more
>important tha
Am Fri, 27 Jan 2006 18:08:38 -0500 schrieb [EMAIL PROTECTED]:
> Nearly all Debian packages should be pristine; if you can do that, you
> should. If upstream *only* exists in CVS, then you can't really, and
> you can run that command before creating your orig tarball. If
> upstream has a real tar
On Fri, Jan 27, 2006 at 11:58:49PM +0100, Daniel Knabl wrote:
> Am Fri, 27 Jan 2006 16:21:47 -0500 schrieb [EMAIL PROTECTED]:
>
> > Thats not a sufficient reason to repack the tarball; it is more
> > important that it is pristine (if applicable). Perhaps the clean
> > target can remove them, and
Am Fri, 27 Jan 2006 16:21:47 -0500 schrieb [EMAIL PROTECTED]:
> Thats not a sufficient reason to repack the tarball; it is more
> important that it is pristine (if applicable). Perhaps the clean
> target can remove them, and then you don't have to look at them nearly
> as much (instead, the "dpkg
On Fri, Jan 27, 2006 at 10:09:56PM +0100, Daniel Knabl wrote:
> Am Fri, 27 Jan 2006 13:24:49 -0500 schrieb Justin Pryzby
> <[EMAIL PROTECTED]>:
>
> > Could you please build your package as nonnative, and preferrably
> > pristine? Otherwise I don't know where to start looking at your work.
> >
>
Am Fri, 27 Jan 2006 13:24:49 -0500 schrieb Justin Pryzby
<[EMAIL PROTECTED]>:
> Could you please build your package as nonnative, and preferrably
> pristine? Otherwise I don't know where to start looking at your work.
>
> nonnative means that an .orig.tar.gz of the expected name exists in
> the
Could you please build your package as nonnative, and preferrably
pristine? Otherwise I don't know where to start looking at your work.
nonnative means that an .orig.tar.gz of the expected name exists in
the parent directory, and pristine means that the tarball is identical
to upstreams (not just
Am Fri, 27 Jan 2006 17:27:09 +0100 schrieb Marc 'HE' Brockschmidt
<[EMAIL PROTECTED]>:
> Yes. The problem is that the Debian policy specifies other targets in
> the maintainer script. Normally, most people don't implement them and
> do a 'abort-upgrade|bla|baz) #do nothing'. You don't do so, your
Daniel Knabl <[EMAIL PROTECTED]> writes:
> The main target in postinst, when someone initially installs the
> software, is "configure", and in postrm, when someone purges it, it is
> "purge". For these two targets I found examples by looking at some
> other packages (phpmyadmin, album, ...) that do
Am Fri, 27 Jan 2006 11:37:42 + schrieb Stephen Gran
<[EMAIL PROTECTED]>:
> Disclaimer: I have not looked at your packaging.
>
> The standard way to do this sort of thing is look through the
> reference for all the arguments your script can be called with, and
> handle them.
>
> so something
Daniel Knabl <[EMAIL PROTECTED]> wrote:
> The main target in postinst, when someone initially installs the
> software, is "configure",
No, not only upon initially installing it. On every upgrade.
> and in postrm, when someone purges it, it is
> "purge".
No, if the package is purged, postrm i
This one time, at band camp, Daniel Knabl said:
> Am Fri, 27 Jan 2006 10:44:47 +0100 schrieb Marc Haber
> <[EMAIL PROTECTED]>:
>
> > How many times have you been pointed to Debian policy?
>
> Do you mean "after I already read it"? Then the answer is "too many
> times"...
>
> > And you are still
Am Fri, 27 Jan 2006 10:44:47 +0100 schrieb Marc Haber
<[EMAIL PROTECTED]>:
> How many times have you been pointed to Debian policy?
Do you mean "after I already read it"? Then the answer is "too many
times"...
> And you are still asking questions that neatly show that you didn't
> read it? And t
On Thu, 26 Jan 2006 14:11:27 +0100, Daniel Knabl
<[EMAIL PROTECTED]> wrote:
>Einst schrieb Marc 'HE' Brockschmidt <[EMAIL PROTECTED]>:
>>* postinst is sometimes called with other values (*not* only
>> configure). Though these are perfectly OK, your postinst script will
>> fail.
>
>Could you descr
Einst schrieb Marc 'HE' Brockschmidt <[EMAIL PROTECTED]>:
>* Doesn't build in my pbuilder chroot
http://lists.debian.org/debian-mentors/2006/01/msg00416.html
http://lists.debian.org/debian-mentors/2006/01/msg00417.html
Neither in mine ... :/
>* Instead of setting an insecure default password an
On Mon, 23 Jan 2006 16:25:11 +, Stephen Gran <[EMAIL PROTECTED]>
wrote:
>This one time, at band camp, Daniel Knabl said:
>> Am Sun, 22 Jan 2006 14:44:59 -0500 schrieb Justin Pryzby
>> > How do you deal with the exim4 "conf.d" model vs the exim4.conf model?
>>
>> Please look at the previous par
> Well, maybe it "seems", but indeed I DID read it. Not just read, I also
Ok, you have to understand that this is borderline possible to do
right, and exim4 is probably one of only a handful of packages that
will allow this, because its configuration is in a separate package.
> In one point you ar
This one time, at band camp, Daniel Knabl said:
> Am Sun, 22 Jan 2006 14:44:59 -0500 schrieb Justin Pryzby
> > How do you deal with the exim4 "conf.d" model vs the exim4.conf model?
>
> Please look at the previous paragraphs. ;-)
Why don't you just create an entire seperate conf.d structure and t
Marc Haber <[EMAIL PROTECTED]> writes:
> On Mon, 23 Jan 2006 00:16:25 +0100, Daniel Knabl <[EMAIL PROTECTED]>
> wrote:
[..]
>> cat /usr/share/doc/vexim/setup/mysql.sql |\
>> sed s/@@PASS@@/$dc_vexim_pass/g |\
[...]
> I am not sure whether maintainer scripts are allowed to rely on
> informatio
Am Mon, 23 Jan 2006 08:24:58 +0100 schrieb Marc Haber
<[EMAIL PROTECTED]>:
> In exim4's README.Debian, it is mentioned how to replace exim4-config,
> and the exim4 svn has two examples of packages which do this in a
> greaceful matter. Daniel has been pointed to that README.Debian file
> multiple
On Sun, 22 Jan 2006 20:55:09 -0500, Justin Pryzby
<[EMAIL PROTECTED]> wrote:
>What is exim4-config-2 anyway?
We had to change the exim4-config "API" early in the development
process, so exim4-config-2 is a "virtual" dependency for the current
version of the exim4-config "API" as described in READM
On Mon, 23 Jan 2006 00:16:25 +0100, Daniel Knabl <[EMAIL PROTECTED]>
wrote:
>case "$1" in
> configure)
> db_get vexim/dc_vexim_pass || true
> dc_vexim_pass=$RET
> db_get vexim/dc_vexim_myip || true
> dc_vexim_myip=$RET
> db_get vexim/dc_vexim_fdqn || true
> dc_vexim_fdqn=$RET
> cat /usr/sha
On Sun, 22 Jan 2006 14:44:59 -0500, Justin Pryzby
<[EMAIL PROTECTED]> wrote:
>You can't just overwrite exim4-config's conffiles. I *think* you can
>Provide: exim4-config, but only if you also Conflict: exim4-config.
The exim4 maintainer insists that vexim completely replaces
exim4-config, so that
On Mon, Jan 23, 2006 at 12:16:25AM +0100, Daniel Knabl wrote:
> Am Sun, 22 Jan 2006 14:44:59 -0500 schrieb Justin Pryzby
> <[EMAIL PROTECTED]>:
>
> > > if there is anyone willing and/or able to help me with the next
> > > steps i would be very happy. right now i have some questions on how
> > > to
On Mon, Jan 23, 2006 at 12:16:25AM +0100, Daniel Knabl wrote:
> > Are you planning on providing fully generalized "maintainer script"
> > handling of the config files, or are conffiles sufficient?
> I am trying this right now in ./debian/postinst:
> cat /usr/share/doc/vexim/setup/mysql.sql |\
>
Am Sun, 22 Jan 2006 14:44:59 -0500 schrieb Justin Pryzby
<[EMAIL PROTECTED]>:
> > if there is anyone willing and/or able to help me with the next
> > steps i would be very happy. right now i have some questions on how
> > to get debconf and templates working,
> Read debconf-devel(7), and google ab
On Sun, Jan 22, 2006 at 05:22:46PM +0100, Daniel Knabl wrote:
> Hi there,
>
> as i use this piece of software already on my own host, i would like to
> provide it to any other users.
>
> for the first steps i have created a directory "vexim-2.2.rc1". it
> includes all of the used files (most are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
as i use this piece of software already on my own host, i would like to
provide it to any other users.
for the first steps i have created a directory "vexim-2.2.rc1". it
includes all of the used files (most are *.php files). next i did
"dh_
Hi there,
as i use this piece of software already on my own host, i would like to
provide it to any other users.
for the first steps i have created a directory "vexim-2.2.rc1". it
includes all of the used files (most are *.php files). next i did
"dh_make" on it.
as i think it is a single binary
> <[EMAIL PROTECTED]>:
...
> PGP Fingerprint [EMAIL PROTECTED]
I am sorry for this maybe confusing usage of Email adresses.
So I would like to explain:
At the moment I am using 3 different Email adresses, but all of them
with only one pgp/gpg key:
A069 671B 39F2 E9B9 FB34
31 matches
Mail list logo
