Date: Fri, 13 Jun 2008 23:22:40 +0300 From: "QA Tindy (Ion-Mihai Tetcu)" <itetcu@FreeBSD.org> To: Philippe Audeoud <jadawin@FreeBSD.org> Cc: cvs-ports@FreeBSD.org, Mark Linimon <linimon@FreeBSD.org>, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/www/nanoblogger Makefile ports/www/nanoblogger/files patch-plugins_entry_format_markdown_sh patch-plugins_page_format_markdown_sh Message-ID: <20080613232240.04e26fbe@it.buh.tecnik93.com> In-Reply-To: <200806131907.m5DJ7WHR003849@repoman.freebsd.org> References: <200806131907.m5DJ7WHR003849@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 13 Jun 2008 19:07:32 +0000 (UTC)
Philippe Audeoud <jadawin@FreeBSD.org> wrote:
> jadawin 2008-06-13 19:07:32 UTC
>
> FreeBSD ports repository
>
> Modified files:
> www/nanoblogger Makefile
> Added files:
> www/nanoblogger/files patch-plugins_entry_format_markdown_sh
> patch-plugins_page_format_markdown_sh
> Log:
> - Use ${PREFIX} for markdown in patches
> - While I'm here use SF macro
>
> PR: ports/124408
> Submitted by: Tobias Rehbein <tobias.rehbein web.de>
> Approved by: tabthorpe (mentor)
>
> Revision Changes Path
> 1.11 +7 -4 ports/www/nanoblogger/Makefile
> 1.1 +11 -0 ports/www/nanoblogger/files/patch-plugins_entry_format_markdown_sh (new)
> 1.1 +11 -0 ports/www/nanoblogger/files/patch-plugins_page_format_markdown_sh (new)
>
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.
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:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes.
The error which triggered this email is bellow followed by the link to the
full log and explanations about the testing process.
building nanoblogger-3.3_2 in directory /var/tinderbox/7-STABLE-FTP
maintained by: ports@FreeBSD.org
building for: 7.0-STABLE amd64
port directory: /usr/ports/www/nanoblogger
Makefile ident: $FreeBSD: ports/www/nanoblogger/Makefile,v 1.11 2008/06/13 19:07:32 jadawin Exp $
prefixes: LOCALBASE=usr/local X11BASE=usr/local
NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes
build started at Fri Jun 13 19:56:49 UTC 2008
.....
====================<phase 7: make package>====================
===> Building package for nanoblogger-3.3_2
tar: share/doc/nanoblogger/COPYING: Cannot stat: No such file or directory
tar: share/doc/nanoblogger/ChangeLog: Cannot stat: No such file or directory
tar: share/doc/nanoblogger/README: Cannot stat: No such file or directory
tar: share/doc/nanoblogger/TODO: Cannot stat: No such file or directory
tar: share/doc/nanoblogger/nanoblogger.html: Cannot stat: No such file or directory
tar: Error exit delayed from previous errors.
pkg_create: make_dist: tar command failed with code 256
Creating package /tmp/packages/All/nanoblogger-3.3_2.tbz
Registering depends: bash-3.2.39_1 gettext-0.17_1 libiconv-1.11_1.
Creating bzip'd tar ball in '/tmp/packages/All/nanoblogger-3.3_2.tbz'
*** Error code 1
Stop in /a/ports/www/nanoblogger.
================================================================
build of /usr/ports/www/nanoblogger ended at Fri Jun 13 19:56:55 UTC 2008
http://t64.tecnik93.com/errors/7-STABLE-FTP/nanoblogger-3.3_2.log
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).
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.
Please use the right pairs like:
%%PORTDOCS%%%%DOCSDIR%%
%%PORTEXAMPLES%%%%EXAMPLESDIR%%
%%PORTDATA%%%%DATADIR%%
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@FreeBSD.org, PGP Key ID 057E9F8B493A297B
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080613232240.04e26fbe>