cvs commit: ports/comms/smstools pkg-plist ports/comms/smstools/files patch-install.sh

[Ion-Mihai Tetcu]

On Thu, 5 Jun 2008 08:59:28 +0000 (UTC)
Pav Lucistnik <pav at FreeBSD.org> wrote:

> pav         2008-06-05 08:59:28 UTC
> 
>   FreeBSD ports repository
> 
>   Modified files:
>     comms/smstools       pkg-plist 
>     comms/smstools/files patch-install.sh 
>   Log:
>   Dont overwrite conf file on upgrades
>   
>   Revision  Changes    Path
>   1.4       +1 -1      ports/comms/smstools/files/patch-install.sh
>   1.7       +1 -1      ports/comms/smstools/pkg-plist
> 
Hi,


You receive this email if you are either the maintainer of the port or if you
recently committed to it. If the error is already fixed please ignore this
email; if you submit a PR to fix it CC me and I'll commit it ASAP.

These emails are generated in one of the following cases:
- an automated build was scheduled because the port was touched in CVS
- the periodic QA build has reached it.
- the port was scheduled because it is a dependency of a port from the cases
above.
There is no fixed interval for this; if other ports depend on it you will
receive this emails more often since testing those other ports is made
impossible by this port being broken. Efforts are made to restrict the number
of outgoing emails to one/port/week for QA or dependency builds (but not for
commit-triggered builds; if you commit 3 times in 5 minutes to the same port
and the first 2 versions fail you'll receive 2 emails).

The builds are done under tinderbox-2.4.3, on 7-STABLE on amd64, with
tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the
official up-to-date Ports Tree (for commit-triggered builds the files are
fetched via CVSWeb), with the following vars set:
FORCE_PACKAGE=yes, NOPORTDOCS=yes,  NOPORTEXAMPLES=yes, NOPORTDATA=yes.

When you fix install/plist errors please bear in mind that each of the 3 NO*
vars controls the installation of different type of files, so constructs like:
.ifndef NOPORTDOCS
        @${MKDIR} ${DATADIR}
        ...
.endif
        or
%%PORTDOCS%%%%EXAMPLESDIR%%/some_example_file
are wrong, WRONG, _WRONG_.

The error which triggered this email is bellow:


====================<phase 7: make package>====================
===>  Building package for smstools-2.2.20_1
Creating package /tmp/packages/All/smstools-2.2.20_1.tbz
Registering depends: mm-1.4.2.
Registering conflicts: smstools-3.*.
Creating bzip'd tar ball in '/tmp/packages/All/smstools-2.2.20_1.tbz'
Deleting smstools-2.2.20_1
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
If you are permanently removing smstools, you should also:
'rm -rf /var/spool/sms'
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
================================================================

=== Checking filesystem state
list of extra files and directories in / (not present before this port was installed but present after it was deinstalled)
7141284        4 -r--r--r--    1 root             wheel                 167 Jun  5 09:01 usr/local/etc/smsd.conf
Deleting mm-1.4.2
Deleting gmake-3.81_2
Deleting gettext-0.16.1_3
Deleting libiconv-1.11_1

=== Checking filesystem state after all packages deleted
================================================================
list of extra files and directories in / (not present on clean system but present after everything was deinstalled)
7141284        4 -r--r--r--    1 root             wheel                 167 Jun  5 09:01 usr/local/etc/smsd.conf
================================================================
build of /usr/ports/comms/smstools ended at Thu Jun  5 09:01:06 UTC 2008


http://t64.tecnik93.com/logs/7-STABLE-FTP/smstools-2.2.20_1.log


Thanks for your work on making FreeBSD better,


-- 
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> itetcu at FreeBSD.org, PGP Key ID 057E9F8B493A297B