Bug 29024 - Update port sysutils/ipa (by maintainer)
Summary: Update port sysutils/ipa (by maintainer)
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-07-16 18:20 UTC by simon
Modified: 2001-07-31 18:44 UTC (History)
0 users

See Also:


Attachments
file.diff (148 bytes, patch)
2001-07-16 18:20 UTC, simon
no flags Details | Diff
file.diff (259 bytes, patch)
2001-07-16 18:20 UTC, simon
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description simon 2001-07-16 18:20:00 UTC
Update port sysutils/ipa from version 1.1.3 to 1.1.4

Fix: PORTNAME=	ipa
-PORTVERSION=	1.1.3
+PORTVERSION=	1.1.4
 CATEGORIES=	sysutils
 MASTER_SITES=	http://www.simon.org.ua/ipa/
How-To-Repeat: 
Patch is included.
Comment 1 dwcjr 2001-07-18 04:34:35 UTC
 >> Building for FreeBSD system
cc -O -pipe -march=k6 -march=k6  -o ipa.o -c ipa.c
cc -O -pipe -march=k6 -march=k6  -o cmd.o -c cmd.c
In file included from kip6fw.h:45,
                 from debug.h:35,
                 from cmd.c:52:
/usr/include/netinet6/ip6_fw.h:98: syntax error before `LIST_ENTRY'
Comment 2 dwcjr freebsd_committer freebsd_triage 2001-07-18 04:34:38 UTC
Responsible Changed
From-To: freebsd-ports->dwcjr

I'll handle this one.
Comment 3 Andrey Simonenko 2001-07-18 12:38:24 UTC
I can't reproduce this error at least on FreeBSD 4.3-STABLE (3 Jul 2001).
I looked on sources of just CVSUPed FreeBSD STABLE branch and
can't find differences, which can cause this problem.
Comment 4 dwcjr freebsd_committer freebsd_triage 2001-07-23 03:25:06 UTC
Responsible Changed
From-To: dwcjr->freebsd-ports

Back to ports, can't compile this one.
Comment 5 Mario Sergio Fujikawa Ferreira freebsd_committer freebsd_triage 2001-07-31 18:42:49 UTC
State Changed
From-To: open->closed

Committed, thanks! However, please take a look the Porter's Handbook entry on why PREFIX safeness is important since this port was not. Everything fixed now.