On Wed, Feb 25, 2015 at 12:42:37PM -0800, Rich Shepard wrote:
> >The directory does not exist, but it looks like that's what you have
> >set as "sample_directory", either in the existing main.cf files or
> >in the build configuration.
>
> Yes, there was a samples/ directory in /etc/postfix; I've n
On Wed, 25 Feb 2015, Wietse Venema wrote:
I have added a test to the post-install script so that it terminates with
an error message when a Postfix pathname contains whitespace. To override
a broken pathname in your case one would use:
# make upgrade some_directory=/path/without/space ...
In t
On Wed, 25 Feb 2015, Viktor Dukhovni wrote:
The directory does not exist, but it looks like that's what you have
set as "sample_directory", either in the existing main.cf files or
in the build configuration.
Viktor,
Yes, there was a samples/ directory in /etc/postfix; I've no idea how long
Viktor Dukhovni:
> On Wed, Feb 25, 2015 at 12:13:46PM -0800, Rich Shepard wrote:
>
> > Yes, the problem can be reproduced. There seems to be a directory called
> > /etc/postfix files./, but I cannot access it. Tried a backslash and putting
> > double quotes around the string, but it's not seen. It
On Wed, Feb 25, 2015 at 12:13:46PM -0800, Rich Shepard wrote:
> Yes, the problem can be reproduced. There seems to be a directory called
> /etc/postfix files./, but I cannot access it. Tried a backslash and putting
> double quotes around the string, but it's not seen. It obviously is the
> cause o
On Sun, Feb 22, 2015 at 10:16:12AM -0800, Rich Shepard wrote:
> Copied above to postfix.patch. On my laptop downloaded the SlackBuilds.org
> build files and postfix-2.11.4.tar.gz. Untarred the tarball and copied
> ../src/conf/post-install to the base directory. Applied 'patch post-install
> post
On Wed, 18 Feb 2015, Viktor Dukhovni wrote:
diff --git a/conf/post-install b/conf/post-install
index 7e79c92..35279d0 100644
--- a/conf/post-install
+++ b/conf/post-install
@@ -501,6 +501,7 @@ test -n "$create" && {
# Flag obsolete objects. XXX Solaris 2..9 does not have "test -e".
On Wed, 18 Feb 2015, Wietse Venema wrote:
That means we will need command output from the modified post-install
script to find out what is going on.
Wietse,
As soon as I can.
Rich
Rich Shepard:
> On Wed, 18 Feb 2015, Wietse Venema wrote:
>
> > Or y[o]u can send us the postfix-files file that Postfix 2.11.4
> > wants to install.
>
> $config_directory:d:root:-:755:u
>
Thanks. This is identical to the file as distributed from postfix.org.
That means we will need command
On Wed, 18 Feb 2015, Wietse Venema wrote:
Or y9u can send us the postfix-files file that Postfix 2.11.4 wants to install.
$config_directory:d:root:-:755:u
$data_directory:d:$mail_owner:-:700:uc
$daemon_directory:d:root:-:755:u
$queue_directory:d:root:-:755:uc
$sample_directory:d:root:-:755:o
$
On Wed, Feb 18, 2015 at 11:18:10AM -0500, Wietse Venema wrote:
> > diff --git a/conf/post-install b/conf/post-install
> > index 7e79c92..35279d0 100644
> > --- a/conf/post-install
> > +++ b/conf/post-install
> > @@ -501,6 +501,7 @@ test -n "$create" && {
> > # Flag obsolete objects. XXX So
Viktor Dukhovni:
> On Wed, Feb 18, 2015 at 07:32:38AM -0800, Rich Shepard wrote:
> > On Wed, 18 Feb 2015, Wietse Venema wrote:
> >
> > >This suggests that you have a space in a pathname of some Postfix
> > >configuration pathname parameters such as queue_directory,
> > >command_directory, sendmail
On Wed, 18 Feb 2015, Viktor Dukhovni wrote:
This does not matter, the problem might come from somewhere else. You need
to figure out why that particular path on line "504" is causing the
problem. We can't do that for you.
To do that, you need to edit the post-install shell script to
log the obs
On Wed, Feb 18, 2015 at 07:32:38AM -0800, Rich Shepard wrote:
> On Wed, 18 Feb 2015, Wietse Venema wrote:
>
> >This suggests that you have a space in a pathname of some Postfix
> >configuration pathname parameters such as queue_directory,
> >command_directory, sendmail_path, and so on.
>
> Wietse
On Wed, 18 Feb 2015, Wietse Venema wrote:
This suggests that you have a space in a pathname of some Postfix
configuration pathname parameters such as queue_directory,
command_directory, sendmail_path, and so on.
Wietse,
Here are all directory paths from main.cf; I deleted all other lines:
On Wed, Feb 18, 2015 at 07:23:50AM -0800, Rich Shepard wrote:
> >Oops, I was looking at line 504 in the 3.0.0 source. Indeed in the above
> >line 504, $path should be in quotes, though it if it needs quoting,
> >appending it to "obsolete" still won't work right.
>
> Viktor,
>
> Only the first
On Wed, 18 Feb 2015, Viktor Dukhovni wrote:
Oops, I was looking at line 504 in the 3.0.0 source. Indeed in the above
line 504, $path should be in quotes, though it if it needs quoting,
appending it to "obsolete" still won't work right.
Viktor,
Only the first, unquoted $path needs the quote
On Wed, 18 Feb 2015, Wietse Venema wrote:
Just to be sure we are talking about the same thing, are you referring to
the same line 504 that I have here:
501 # Flag obsolete objects. XXX Solaris 2..9 does not have "test -e".
502 if [ -n "$obsolete_flag" ]
503 then
504 test -r $path -a
Wietse Venema:
> Rich Shepard:
> >When upgrading to -2.11.4 (on Slackware-14.1), a message is displayed
> > that
> > line 504 in /usr/libexec/postfix/post-install has too many arguments. Adding
> > double quotes to $path fixes this problem.
>
> Maintainers sometimes make "improvements" and th
On Wed, Feb 18, 2015 at 09:43:19AM -0500, Wietse Venema wrote:
> Rich Shepard:
> >When upgrading to -2.11.4 (on Slackware-14.1), a message is displayed
> > that
> > line 504 in /usr/libexec/postfix/post-install has too many arguments. Adding
> > double quotes to $path fixes this problem.
>
>
Rich Shepard:
>When upgrading to -2.11.4 (on Slackware-14.1), a message is displayed that
> line 504 in /usr/libexec/postfix/post-install has too many arguments. Adding
> double quotes to $path fixes this problem.
Maintainers sometimes make "improvements" and that can change line
numbers. Just
On Tue, 17 Feb 2015, Viktor Dukhovni wrote:
I am guessing that your shell read and split the whole "postfix-files"
file in one gulp, rather than split each line. Too many tokens from a
single line in that file is implausible.
Viktor,
I passed on your message to the postfix SlackBuilds maint
On Tue, 17 Feb 2015, Viktor Dukhovni wrote:
Before you do, insert debugging code to print the "$path" in question.
Something like:
Viktor,
Thank you; I'll do this.
Rich
On Tue, Feb 17, 2015 at 08:07:00AM -0800, Rich Shepard wrote:
> On Tue, 17 Feb 2015, Viktor Dukhovni wrote:
>
> >This is a symptom of a deeper problem, possibly a bug in the Bourne
> >shell implementation on the system in question.
>
> Victor,
>
> Standard linux bash.
>
> >I am guessing that
On Tue, 17 Feb 2015, Viktor Dukhovni wrote:
This is a symptom of a deeper problem, possibly a bug in the Bourne
shell implementation on the system in question.
Victor,
Standard linux bash.
I am guessing that your shell read and split the whole "postfix-files"
file in one gulp, rather than
On Tue, Feb 17, 2015 at 06:33:08AM -0800, Rich Shepard wrote:
> When upgrading to -2.11.4 (on Slackware-14.1), a message is displayed that
> line 504 in /usr/libexec/postfix/post-install has too many arguments. Adding
> double quotes to $path fixes this problem.
This is a symptom of a deeper pr
When upgrading to -2.11.4 (on Slackware-14.1), a message is displayed that
line 504 in /usr/libexec/postfix/post-install has too many arguments. Adding
double quotes to $path fixes this problem.
Is this an issue with the source for post-install? I don't see any
reference to that file in the S
27 matches
Mail list logo
