From owner-freebsd-eclipse@FreeBSD.ORG Mon Nov 21 10:01:16 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D153016A421 for ; Mon, 21 Nov 2005 10:01:16 +0000 (GMT) (envelope-from fenner+portsurvey@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9725643D5A for ; Mon, 21 Nov 2005 10:01:14 +0000 (GMT) (envelope-from fenner+portsurvey@FreeBSD.org) Received: from freefall.freebsd.org (fenner@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jALA1Ek2077351 for ; Mon, 21 Nov 2005 10:01:14 GMT (envelope-from fenner+portsurvey@freefall.freebsd.org) Received: (from fenner@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jALA1Ept077350; Mon, 21 Nov 2005 10:01:14 GMT (envelope-from fenner+portsurvey) Date: Mon, 21 Nov 2005 10:01:14 GMT Message-Id: <200511211001.jALA1Ept077350@freefall.freebsd.org> From: fenner@freebsd.org (Bill "distfiles" Fenner) To: freebsd-eclipse@freebsd.org Subject: FreeBSD ports: 1 unfetchable distfile: java/eclipse-vep-examples X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ports@freebsd.org List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2005 10:01:17 -0000 Dear freebsd-eclipse@freebsd.org, You are listed as the FreeBSD port maintainer for 1 port whose distfiles are not fetchable from their MASTER_SITES. Could you please visit http://people.freebsd.org/~fenner/portsurvey/freebsd-eclipse@freebsd.org.html and correct the problems listed there? The individual port with a problem is java/eclipse-vep-examples. If you have already corrected the problems and submitted a PR, please accept my thanks and apologies for the delay in getting the fixes into the tree. This reminder is created automatically and does not (yet) have a way to know if a PR fixing the problem has been submitted. Please do *NOT* send your response to me directly; I do not necessarily have time to commit your fix; please instead submit a PR via 'send-pr' so it doesn't get lost. Problems are usually of two types: 1. The software package has been upgraded and the version in the port has been removed. The best solution to this problem is to upgrade the port to the most current version of the software package. If you are a FreeBSD committer, then you can just upgrade the port directly. If not, you should create the updated port on your own machine, test it (and maybe even run "portlint" on it), and then use "send-pr" to submit a "diff -uNr old-port updated-port". If you added or deleted any files, please make an explicit note of it. 2. The mirror site being used no longer contains the software package in question, or no longer exists. Solutions include: a) If there are other mirror sites, just remove the bad site from the list. (Make sure that what appears to be a bad site isn't actually a problem of type 1, upgrade) b) If the README or other support files in the software documentation mention where to get the software package, use one of those sites. c) Use a search engine to find another place to get the original DISTFILES. Make sure that you don't pick a FreeBSD distfiles mirror -- if you can't find any other places where the file exists, it can be a LOCAL_PORT or you can simply comment out the MASTER_SITES= line, with a comment explaining why. Once you have a solution, use "send-pr" to submit a "diff -u" of the Makefile. Note that this isn't an urgent issue, as people who try to build the port now will just fall back to the FreeBSD distfiles mirror. Please just put it on your list to do and get to it when you have time. These messages will continue to arrive twice a month until the fix is committed, as a reminder. Thanks, Bill "distfiles" Fenner. From owner-freebsd-eclipse@FreeBSD.ORG Mon Nov 21 11:02:30 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A86B16A41F for ; Mon, 21 Nov 2005 11:02:30 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F36443D5E for ; Mon, 21 Nov 2005 11:02:28 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jALB2R1H089990 for ; Mon, 21 Nov 2005 11:02:27 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jALB2R7I089984 for freebsd-eclipse@freebsd.org; Mon, 21 Nov 2005 11:02:27 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 21 Nov 2005 11:02:27 GMT Message-Id: <200511211102.jALB2R7I089984@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-eclipse@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2005 11:02:30 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/11/10] ports/88777 eclipse eclipse crashes java machine on indexing 1 problem total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2005/11/07] ports/88603 eclipse [maintainer update] java/eclipse-log4e o [2005/11/07] ports/88604 eclipse [maintainer update] java/eclipse-lomboz 2 problems total. From owner-freebsd-eclipse@FreeBSD.ORG Sat Nov 26 22:03:58 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47E1D16A41F for ; Sat, 26 Nov 2005 22:03:58 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from mail.droso.net (koala.droso.net [193.88.12.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8CF043D5A for ; Sat, 26 Nov 2005 22:03:57 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by mail.droso.net (Postfix) with ESMTP id E9E8C22ADA for ; Sat, 26 Nov 2005 23:03:56 +0100 (CET) Received: from koala.ipv6.droso.net (localhost [IPv6:::1]) by mail.droso.net (Postfix) with ESMTP id E241222AD9 for ; Sat, 26 Nov 2005 23:03:55 +0100 (CET) From: linimon@FreeBSD.org To: freebsd-eclipse@freebsd.org Message-Id: <20051126220355.E241222AD9@mail.droso.net> Date: Sat, 26 Nov 2005 23:03:55 +0100 (CET) X-Virus-Scanned: by amavisd 0.1 Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Nov 2005 22:03:58 -0000 Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we are attempting to notify maintainers of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc3.4, which is much stricter about such things as function declarations, literal strings constants that continue over several physical lines, and forcing the deprecation of antique header files such as varargs.h (we should now be using stdargs.h). The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. If you need help in one or more build environments that you do not have access to, please ask for help on the freebsd-ports mailing list. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 4.x/5.x/6.x with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: java/eclipse-viplugin broken because: Unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2005101122/eclipse-viPlugin-1.13.0.log (Nov 20 23:51:57 UTC 2005) overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=eclipse-viplugin If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD.