#6134 closed enhancement (fixed)
postfix-3.0.0
Reported by: | Owned by: | Fernando de Oliveira | |
---|---|---|---|
Priority: | normal | Milestone: | 7.7 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
New major version. We need to look closely at this to see if we want to do it before package freeze.
Change History (10)
comment:1 by , 9 years ago
follow-ups: 4 7 comment:2 by , 9 years ago
The install is a PITA if you want to install in a DESTDIR location. You need:
sed -i '/chown/s/chown/true/' libexec/post-install postfix-install conf/post-install sed -i '/chgrp/s/chgrp/true/' libexec/post-install postfix-install conf/post-install
prior to the 'sh postfix-install -non-interactive ...' command and add install_root=$DEST to the list of directories.
That said, the executable programs and directories do not change. There are still no libraries installed.
I do not want to install postfix on this test system, so I will not test the current configuration instructions, but they look OK.
I need to have someone that uses postfix on a regular basis to test this package and take this ticket, but I think the above will help.
follow-up: 8 comment:3 by , 9 years ago
Running '/usr/lib/postfix/post-install daemon_directory=/usr/lib/postfix upgrade-package' may be useful when upgrading.
follow-up: 6 comment:4 by , 9 years ago
Replying to bdubbs@…:
The install is a PITA if you want to install in a DESTDIR location.:
For many packages (sudo is another one), I gave up, and use sudo or your as_root:
install -vdm755 $DESTINODIR && as_root sh postfix-install -non-interactive install_root=$DESTINODIR \ daemon_directory=/usr/lib/postfix \ manpage_directory=/usr/share/man \ html_directory=/usr/share/doc/$PACKAGE/html \ readme_directory=/usr/share/doc/$PACKAGE/readme
I need to have someone that uses postfix on a regular basis to test this package and take this ticket, but I think the above will help.
I don't. When I update, I do install it, with minimal instructions of the page, then install the bootscript, start the application, stop, uninstall the bootscript.
comment:5 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:6 by , 9 years ago
Replying to fo:
Replying to bdubbs@…:
I need to have someone that uses postfix on a regular basis to test this package and take this ticket, but I think the above will help.
I don't. When I update, I do install it, with minimal instructions of the page, then install the bootscript, start the application, stop, uninstall the bootscript.
Partially wrong: it's run every boot. Just don't use it. Bootscripts are always there, no remove, install or reinstall.
comment:7 by , 9 years ago
Replying to bdubbs@…:
The install is a PITA if you want to install in a DESTDIR location. You need:
sed -i '/chown/s/chown/true/' libexec/post-install postfix-install conf/post-install sed -i '/chgrp/s/chgrp/true/' libexec/post-install postfix-install conf/post-install
Thanks for that. No need of root privileges for DESTDIR (install_root) is very good!!!
comment:8 by , 9 years ago
Replying to bdubbs@…:
Running '/usr/lib/postfix/post-install daemon_directory=/usr/lib/postfix upgrade-package' may be useful when upgrading.
I've got an error (broke the line for illustration purposes):
$ sudo /usr/lib/postfix/post-install \ daemon_directory=/usr/lib/postfix upgrade-package /usr/lib/postfix/post-install: Error: /postfix-files is not a file.
comment:9 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
This time the application is better tested than I did before.
Fixed at r15489.
comment:10 by , 9 years ago
I am including this comment, after some recollection came to my mind.
First, never I would have thought of using true. Usually, I change user and group to mine ones, and after I revert.
Sometimes, I do a DESTDIR install, verify that everything is OK, and like to do with the source code a true install. That is the reason I used sudo for DESTDIR. For another package, I did fix the DESTDIR install as Bruce did here, but after the install, I revert the fix, for the reason explained before. So, FWIW, I modified Bruces' instruction of comment:2 for that (other cosmetic modifications are just personal preferences, not relevant):
# Fix for DESTDIR unprivileged install sed -e 's/chown/true &/' -e 's/chgrp/true &/' \ -i {libexec,conf}/post-install postfix-install && # DESTDIR unpriviledged install instructions ... && # Revert fix for DESTDIR unprivileged install sed -e 's/true \(chown\)/\1/' -e 's/true \(chgrp\)/\1/' \ -i {libexec,conf}/post-install postfix-install
I know this must be not relevant for Bruce, but perhaps someone might like it.
There are a lot of major changes, especially to the configuration files. See ftp://ftp.porcupine.org/mirrors/postfix-release/official/postfix-3.0.0.RELEASE_NOTES for details.
We should probably put in a caution about upgrading from 2.x versions of postfix pointing to the above url or the RELEASE_NOTES file in the tarball.
A preliminary check of current instructions, without install, was successful.
The sed for Berkeley DB = 5 is no longer needed.
The sed for the README files is still needed.
I did not test OpenLdap, Sqlite, MySql , PostgreSQL, or CDB.
MariaDB is not mentioned anywhere in the source, but should be OK as a substitute for MySql.