[lini...@freebsd.org: svn commit: r464924 - head/emulators/rtc]
FYI
- Forwarded message from Mark Linimon <lini...@freebsd.org> -
Date: Sun, 18 Mar 2018 15:26:30 + (UTC)
From: Mark Linimon <lini...@freebsd.org>
To: ports-committ...@freebsd.org, svn-ports-...@freebsd.org,
svn-ports-h...@freebsd.org
Subject: svn commit: r464924 - head/emulators/rtc
Author: linimon
Date: Sun Mar 18 15:26:29 2018
New Revision: 464924
URL: https://svnweb.freebsd.org/changeset/ports/464924
Log:
Mark as broken on FreeBSD 12. This ought to be an easy fix for someone
who has time.
Modified:
head/emulators/rtc/Makefile
Modified: head/emulators/rtc/Makefile
==
--- head/emulators/rtc/Makefile Sun Mar 18 15:21:53 2018(r464923)
+++ head/emulators/rtc/Makefile Sun Mar 18 15:26:29 2018(r464924)
@@ -11,6 +11,8 @@ DISTFILES=# none
MAINTAINER=emulat...@freebsd.org
COMMENT= Kernel module which provides /dev/rtc device support
+BROKEN_FreeBSD_12= fails to compile: rtc.c:166:2: implicit declaration of
function 'MALLOC' is invalid in C99
+
WRKSRC=${WRKDIR}/files
NO_FETCH= yes
- End forwarded message -
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
[lini...@freebsd.org: svn commit: r455174 - head/devel/kBuild]
FYI
- Forwarded message from Mark Linimon <lini...@freebsd.org> -
Date: Thu, 30 Nov 2017 07:08:55 + (UTC)
From: Mark Linimon <lini...@freebsd.org>
To: ports-committ...@freebsd.org, svn-ports-...@freebsd.org,
svn-ports-h...@freebsd.org
Subject: svn commit: r455174 - head/devel/kBuild
Author: linimon
Date: Thu Nov 30 07:08:54 2017
New Revision: 455174
URL: https://svnweb.freebsd.org/changeset/ports/455174
Log:
Replace regex that was particular to armv6 with one that will also
include armv7. This is part of a larger sweep to fix all such regexes
in the tree.
It won't really matter until the build is fixed for armv[67] but the
bad usages need to be removed.
Approved by: portmgr (tier-2 blanket)
Modified:
head/devel/kBuild/Makefile
Modified: head/devel/kBuild/Makefile
==
--- head/devel/kBuild/Makefile Thu Nov 30 07:02:49 2017(r455173)
+++ head/devel/kBuild/Makefile Thu Nov 30 07:08:54 2017(r455174)
@@ -15,7 +15,7 @@ LICENSE= BSD3CLAUSE GPLv3+
LICENSE_COMB= multi
BROKEN_powerpc64= does not build: fatal error: xmmintrin.h: No such file
or directory
-NOT_FOR_ARCHS= aarch64 armv6 mips mips64
+NOT_FOR_ARCHS= aarch64 armv6 armv7 mips mips64
NOT_FOR_ARCHS_REASON= ./kBuild/env.sh: unknown cpu/arch
USE_GCC= any
@@ -26,7 +26,7 @@ CONFLICTS_INSTALL=kBuild-devel-[0-9]*
WRKSRC=${WRKDIR}/${PORTNAME}-${DISTVERSION}
KBUILD_VERSION=0.1.9998
-KBUILD_ARCH=
${MACHINE_ARCH:S/i386/x86/:S/x86_64/amd64/:S/powerpc/ppc32/:S/armv6/arm/}
+KBUILD_ARCH=
${MACHINE_ARCH:S/i386/x86/:S/x86_64/amd64/:S/powerpc/ppc32/:C/armv.*/arm/}
KBUILD_ENV=ACLOCAL=${ACLOCAL} \
AUTOMAKE=${AUTOMAKE} \
AUTORECONF=${AUTORECONF} \
- End forwarded message -
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
[lini...@freebsd.org: svn commit: r440001 - in head: databases/galera databases/mysqlwsrep56-server databases/py-xapian databases/riak2 devel/aws-sdk-cpp devel/clanlib devel/directfb devel/elfutils de
FYI. You do not need to take any action.
/home/linimon/ports/default/databases/mysqlwsrep56-server
i...@galeracluster.com
/home/linimon/ports/default/databases/py-xapian sunp...@freebsd.org
/home/linimon/ports/default/databases/riak2 w...@freebsd.org
/home/linimon/ports/default/devel/aws-sdk-cppar...@freebsd.org
/home/linimon/ports/default/devel/directfb
anatoly.boro...@gmail.com
/home/linimon/ports/default/devel/elfutils c...@freebsd.org
/home/linimon/ports/default/devel/kBuild v...@freebsd.org
/home/linimon/ports/default/devel/pecl-grpc vani...@freebsd.org
/home/linimon/ports/default/devel/raknet
marty...@freebsd.org
/home/linimon/ports/default/devel/rapidjson y...@rawbw.com
/home/linimon/ports/default/graphics/rawtherapee mand...@freebsd.org
/home/linimon/ports/default/graphics/rawtherapee-devel mand...@freebsd.org
mcl
- Forwarded message from Mark Linimon <lini...@freebsd.org> -
Date: Wed, 3 May 2017 05:52:55 + (UTC)
From: Mark Linimon <lini...@freebsd.org>
To: ports-committ...@freebsd.org, svn-ports-...@freebsd.org,
svn-ports-h...@freebsd.org
Subject: svn commit: r440001 - in head: databases/galera
databases/mysqlwsrep56-server databases/py-xapian databases/riak2
devel/aws-sdk-cpp devel/clanlib devel/directfb devel/elfutils devel/kBuild
devel/pe...
Author: linimon
Date: Wed May 3 05:52:55 2017
New Revision: 440001
URL: https://svnweb.freebsd.org/changeset/ports/440001
Log:
Mark some ports failing on aarch64, and, in a few cases, other tier-2
archs.
While here, pet portlint.
Approved by: portmgr (tier-2 blanket)
Modified:
head/databases/galera/Makefile
head/databases/mysqlwsrep56-server/Makefile
head/databases/py-xapian/Makefile
head/databases/riak2/Makefile
head/devel/aws-sdk-cpp/Makefile
head/devel/clanlib/Makefile
head/devel/directfb/Makefile
head/devel/elfutils/Makefile
head/devel/kBuild/Makefile
head/devel/pecl-grpc/Makefile
head/devel/pwlib/Makefile
head/devel/raknet/Makefile
head/devel/rapidjson/Makefile
head/devel/smv/Makefile
head/devel/sourcenav/Makefile
head/graphics/rawtherapee-devel/Makefile
head/graphics/rawtherapee/Makefile
Modified: head/databases/galera/Makefile
==
--- head/databases/galera/Makefile Wed May 3 01:38:07 2017
(r44)
+++ head/databases/galera/Makefile Wed May 3 05:52:55 2017
(r440001)
@@ -18,6 +18,9 @@ BUILD_DEPENDS=checkmk:devel/check \
${PYTHON_PKGNAMEPREFIX}cloud_sptheme>=0:textproc/py-cloud_sptheme
LIB_DEPENDS= libboost_date_time.so:devel/boost-libs
+NOT_FOR_ARCHS= aarch64
+NOT_FOR_ARCHS_REASON= error Please add support for your architecture in
build/build_config.h
+
USES= execinfo python:build scons shebangfix ssl
USE_CXXSTD=c++11
Modified: head/databases/mysqlwsrep56-server/Makefile
==
--- head/databases/mysqlwsrep56-server/Makefile Wed May 3 01:38:07 2017
(r44)
+++ head/databases/mysqlwsrep56-server/Makefile Wed May 3 05:52:55 2017
(r440001)
@@ -19,7 +19,8 @@ RUN_DEPENDS= socat:net/socat lsof:sysuti
DATADIR= ${PREFIX}/share/mysql
-BROKEN_powerpc64= Does not build
+NOT_FOR_ARCHS= aarch64 armv6 powerpc64
+NOT_FOR_ARCHS_REASON= error: Unsupported platform
USES= cmake:outsource libedit shebangfix perl5
USE_PERL5= run
Modified: head/databases/py-xapian/Makefile
==
--- head/databases/py-xapian/Makefile Wed May 3 01:38:07 2017
(r44)
+++ head/databases/py-xapian/Makefile Wed May 3 05:52:55 2017
(r440001)
@@ -18,6 +18,8 @@ LICENSE_FILE= ${WRKSRC}/COPYING
BUILD_DEPENDS= xapian-core>=${PORTVERSION}:databases/xapian-core
LIB_DEPENDS= libxapian.so:databases/xapian-core
+BROKEN_aarch64=fails to build: Fatal Python error:
swig_pythreadstate set in XapianSWIG_Python_Thread_Allow ctor
+
CONFLICTS_INSTALL= xapian-bindings12-
OPTIONS_DEFINE=DOCS
Modified: head/databases/riak2/Makefile
==
--- head/databases/riak2/Makefile Wed May 3 01:38:07 2017
(r44)
+++ head/databases/riak2/Makefile Wed May 3 05:52:55 2017
(r440001)
@@ -28,9 +28,11 @@ SHEBANG_FILES= deps/eper/priv/bin/* \
USE_RC_SUBR= riak
USE_GCC= yes
-BROKEN_i386= Does not build
-BROKEN_powerpc64= Does not build
-BROKEN_sparc64=Does not build: Please implement AtomicPointer
for this platform
+BROKEN_i386= does not build
+BROKEN_powerpc64= does not bui
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: sysutils/linux-nero broken because: Unfetchable build errors: http://beefy1.isc.freebsd.org/bulk/93i386-RELENG_9_3/latest/logs/errors/linux-nero-4.0.0.0_2.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=linux-nero 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: sysutils/linux-nero broken because: Unfetchable build errors: http://beefy2.isc.freebsd.org/bulk/93amd64-RELENG_9_3/latest/logs/errors/linux-nero-4.0.0.0_2.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=linux-nero 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: sysutils/linux-nero broken because: Unfetchable build errors: http://beefy2.isc.freebsd.org/bulk/93amd64-RELENG_9_3/latest/logs/errors/linux-nero-4.0.0.0_2.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=linux-nero 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: sysutils/linux-nero broken because: Unfetchable build errors: http://beefy2.isc.freebsd.org/bulk/93amd64-RELENG_9_3/latest/logs/errors/linux-nero-4.0.0.0_2.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=linux-nero 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: devel/linux_kdump broken because: Fails to build with new linux_base-gentoo-stage3 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux_kdump portname: sysutils/linux-nero broken because: Unfetchable build errors: http://beefy2.isc.freebsd.org/bulk/93amd64-RELENG_9_3/latest/logs/errors/linux-nero-4.0.0.0_2.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=linux-nero 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: audio/linux-f10-nas-libs forbidden because: http://www.freshports.org/vuxml.php?vid=bf7912f5-c1a8-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-f10-nas-libs If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: audio/linux-f10-libaudiofile forbidden because: http://www.freshports.org/vuxml.php?vid=09f47c51-c1a6-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-f10-libaudiofile portname: audio/linux-f10-nas-libs forbidden because: http://www.freshports.org/vuxml.php?vid=bf7912f5-c1a8-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-f10-nas-libs portname: devel/linux-f10-dbus-glib forbidden because: http://www.freshports.org/vuxml.php?vid=77bb0541-c1aa-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-f10-dbus-glib portname: ftp/linux-f10-curl forbidden because: http://www.freshports.org/vuxml.php?vid=9aecb94c-c1ad-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ftpportname=linux-f10-curl portname: graphics/linux-f10-png forbidden because: http://www.freshports.org/vuxml.php?vid=262b92fe-81c8-11e1-8899-001ec9578670 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-f10-png portname: graphics/linux-f10-tiff forbidden because: http://www.freshports.org/vuxml.php?vid=8816bf3a-7929-11df-bcce-0018f3e2eb82 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-f10-tiff portname: net/linux-f10-openldap forbidden because: http://www.freshports.org/vuxml.php?vid=abad20bf-c1b4-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=netportname=linux-f10-openldap portname: security/linux-f10-gnutls forbidden because: http://www.freshports.org/vuxml.php?vid=f645aa90-a3e8-11e3-a422-3c970e169bc2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=securityportname=linux-f10-gnutls portname: security/linux-f10-libgcrypt forbidden because: http://www.freshports.org/vuxml.php?vid=689c2bf7-0701-11e3-9a25-002590860428 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=securityportname=linux-f10-libgcrypt portname: security/linux-f10-nss forbidden because: http://www.freshports.org/vuxml.php?vid=9ccfee39-3c3b-11df-9edc-000f20797ede build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=securityportname=linux-f10-nss portname: textproc/linux-f10-expat forbidden because: http://www.freshports.org/vuxml.php?vid=5f030587-e39a-11de-881e-001aa0166822 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textprocportname=linux-f10-expat portname: textproc/linux-f10-libxml2 forbidden because: http://www.freshports.org/vuxml.php?vid=57f1a624-6197-11e1-b98c-bcaec565249c|7be92050-a450-11e2-9898-001060e06fd4|b8ae4659-a0da-11e1-a294-bcaec565249c build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textprocportname=linux-f10-libxml2 If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: sysutils/linux-nero broken because: Unfetchable build errors: http://beefy2.isc.freebsd.org/bulk/93amd64-RELENG_9_3/latest/logs/errors/linux-nero-4.0.0.0_2.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=linux-nero 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: audio/linux-f10-libaudiofile forbidden because: http://www.freshports.org/vuxml.php?vid=09f47c51-c1a6-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-f10-libaudiofile portname: audio/linux-f10-nas-libs forbidden because: http://www.freshports.org/vuxml.php?vid=bf7912f5-c1a8-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-f10-nas-libs portname: devel/linux-f10-dbus-glib forbidden because: http://www.freshports.org/vuxml.php?vid=77bb0541-c1aa-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-f10-dbus-glib portname: ftp/linux-f10-curl forbidden because: http://www.freshports.org/vuxml.php?vid=9aecb94c-c1ad-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ftpportname=linux-f10-curl portname: graphics/linux-f10-png forbidden because: http://www.freshports.org/vuxml.php?vid=262b92fe-81c8-11e1-8899-001ec9578670 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-f10-png portname: graphics/linux-f10-tiff forbidden because: http://www.freshports.org/vuxml.php?vid=8816bf3a-7929-11df-bcce-0018f3e2eb82 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-f10-tiff portname: net/linux-f10-openldap forbidden because: http://www.freshports.org/vuxml.php?vid=abad20bf-c1b4-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=netportname=linux-f10-openldap portname: security/linux-f10-gnutls forbidden because: http://www.freshports.org/vuxml.php?vid=f645aa90-a3e8-11e3-a422-3c970e169bc2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=securityportname=linux-f10-gnutls portname: security/linux-f10-libgcrypt forbidden because: http://www.freshports.org/vuxml.php?vid=689c2bf7-0701-11e3-9a25-002590860428 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=securityportname=linux-f10-libgcrypt portname: security/linux-f10-nss forbidden because: http://www.freshports.org/vuxml.php?vid=9ccfee39-3c3b-11df-9edc-000f20797ede build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=securityportname=linux-f10-nss portname: textproc/linux-f10-expat forbidden because: http://www.freshports.org/vuxml.php?vid=5f030587-e39a-11de-881e-001aa0166822 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textprocportname=linux-f10-expat portname: textproc/linux-f10-libxml2 forbidden because: http://www.freshports.org/vuxml.php?vid=57f1a624-6197-11e1-b98c-bcaec565249c|7be92050-a450-11e2-9898-001060e06fd4|b8ae4659-a0da-11e1-a294-bcaec565249c build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textprocportname=linux-f10-libxml2 If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: sysutils/linux-nero broken because: Unfetchable build errors: http://beefy2.isc.freebsd.org/bulk/93amd64-RELENG_9_3/latest/logs/errors/linux-nero-4.0.0.0_2.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=linux-nero 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: emulators/virtualbox-ose-legacy description:General-purpose full virtualizer for x86 hardware maintainer: v...@freebsd.org deprecated because: Not staged. See http://lists.freebsd.org/pipermail/freebsd-ports-announce/2014-May/80.html expiration date:2014-08-31 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=virtualbox-ose-legacy If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: sysutils/linux-nero broken because: Unfetchable build errors: http://beefy2.isc.freebsd.org/bulk/93amd64-RELENG_9_3/latest/logs/errors/linux-nero-4.0.0.0_2.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=linux-nero 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: sysutils/linux-nero broken because: Unfetchable build errors: http://beefy2.isc.freebsd.org/bulk/10amd64-quarterly/latest/logs/errors/linux-nero-4.0.0.0_2.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=linux-nero 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: sysutils/linux-nero broken because: Unfetchable build errors: http://beefy2.isc.freebsd.org/bulk/91amd64-quarterly/latest/logs/errors/linux-nero-4.0.0.0_2.log overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutilsportname=linux-nero 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
PR reclassification
Please don't panic about the previous PR message. We are running a test of PR migration. That email should not have been sent. Sorry. mcl ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/190058: emulators/linux-base-f10: kldload linux skipped in script, installing linux-base-f10 package
Synopsis: emulators/linux-base-f10: kldload linux skipped in script, installing linux-base-f10 package Responsible-Changed-From-To: freebsd-ports-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 29 04:21:38 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=190058 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/189097: [hyper-v] [patch] 10-STABLE breaks Windows Azure compatibility [regression]
Synopsis: [hyper-v] [patch] 10-STABLE breaks Windows Azure compatibility [regression] Responsible-Changed-From-To: freebsd-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 4 02:42:58 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=189097 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/170356: [hyper-v] Installing freebsd on Hyper-V server 2008 R2 results in panic
Synopsis: [hyper-v] Installing freebsd on Hyper-V server 2008 R2 results in panic Responsible-Changed-From-To: freebsd-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 4 02:51:17 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=170356 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/162314: [hyper-v] not able to install FreeBSD-8.2-RELEASE-amd64-dvd1 as a guest on Hyper-V
Synopsis: [hyper-v] not able to install FreeBSD-8.2-RELEASE-amd64-dvd1 as a guest on Hyper-V Responsible-Changed-From-To: freebsd-amd64-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 4 02:51:17 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=162314 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/153496: [hyper-v] [install] Install on Hyper-V leaves corrupt filesystems (incl root)
Synopsis: [hyper-v] [install] Install on Hyper-V leaves corrupt filesystems (incl root) Responsible-Changed-From-To: freebsd-amd64-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 4 02:51:17 UTC 2014 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=153496 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/189001: [kvm] FreeBSD 10 i386 installer (pwd_mkdb) crash during install on KVM
Old Synopsis: FreeBSD 10 i386 installer (pwd_mkdb) crash during install on KVM New Synopsis: [kvm] FreeBSD 10 i386 installer (pwd_mkdb) crash during install on KVM Responsible-Changed-From-To: freebsd-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 4 03:00:43 UTC 2014 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=189001 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/164957: [linux] [hang] Linux emulation freezes machine after heavy usage of cpu and memory
Old Synopsis: Linux emulation freezes machine after heavy usage of cpu and memory New Synopsis: [linux] [hang] Linux emulation freezes machine after heavy usage of cpu and memory Responsible-Changed-From-To: freebsd-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun Apr 20 00:21:09 UTC 2014 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=164957 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/186909: [hyper-v] Stable GENERIC kernel panic on hyperv 2012 OS
Synopsis: [hyper-v] Stable GENERIC kernel panic on hyperv 2012 OS State-Changed-From-To: open-open State-Changed-By: linimon State-Changed-When: Sun Apr 20 01:48:45 UTC 2014 State-Changed-Why: cleaning up text of PR. Responsible-Changed-From-To: freebsd-emulation-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun Apr 20 01:48:45 UTC 2014 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=186909 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/185873: [linux] waitpid() in linux threads fails with ECHILD
Old Synopsis: waitpid() in linux threads fails with ECHILD New Synopsis: [linux] waitpid() in linux threads fails with ECHILD Responsible-Changed-From-To: freebsd-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun Apr 20 02:58:16 UTC 2014 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=185873 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/185849: [vmx] TSO in vmx driver broken
Old Synopsis: TSO in vmx driver broken New Synopsis: [vmx] TSO in vmx driver broken Responsible-Changed-From-To: freebsd-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun Apr 20 03:10:29 UTC 2014 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=185849 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/188053: emulators/virtualbox-ose 4.3.10 doesn't build on 9.2
The following reply was made to PR ports/188053; it has been noted by GNATS. From: Mark Linimon lini...@lonesome.com To: bug-follo...@freebsd.org Cc: Subject: Re: ports/188053: emulators/virtualbox-ose 4.3.10 doesn't build on 9.2 Date: Wed, 16 Apr 2014 23:01:22 -0500 - Forwarded message from Lawrence K. Chen, P.Eng. lkc...@ksu.edu - Date: Wed, 16 Apr 2014 16:33:05 -0500 From: Lawrence K. Chen, P.Eng. lkc...@ksu.edu To: freebsd-emulation@freebsd.org Subject: Re: ports/188053: emulators/virtualbox-ose 4.3.10 doesn't build on 9.2 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 Presumably this patch was doesn't break virtualbox-ose building on 9.2 with X11, correct? Since, at first glance there are changes that aren't conditioned on whether X11 is set or not. -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Sr. Unix Systems Administrator For: Enterprise Server Technologies (EST) -- SafeZone Ally - End forwarded message - ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/188053: emulators/virtualbox-ose 4.3.10 doesn't build on 9.2
The following reply was made to PR ports/188053; it has been noted by GNATS. From: Mark Linimon lini...@lonesome.com To: bug-follo...@freebsd.org Cc: Subject: Re: ports/188053: emulators/virtualbox-ose 4.3.10 doesn't build on 9.2 Date: Wed, 16 Apr 2014 23:01:54 -0500 - Forwarded message from Jung-uk Kim j...@freebsd.org - Date: Wed, 16 Apr 2014 17:45:59 -0400 From: Jung-uk Kim j...@freebsd.org To: Lawrence K. Chen, P.Eng. lkc...@ksu.edu, freebsd-emulation@freebsd.org Subject: Re: ports/188053: emulators/virtualbox-ose 4.3.10 doesn't build on 9.2 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2014-04-16 17:33:05 -0400, P.Eng. Lawrence K. Chen wrote: Presumably this patch was doesn't break virtualbox-ose building on 9.2 with X11, correct? Since, at first glance there are changes that aren't conditioned on whether X11 is set or not. Correct. Jung-uk Kim -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (FreeBSD) iQEcBAEBAgAGBQJTTvoWAAoJEHyflib82/FGTKUH/0at7ey+7tmKYOt10TQsvrXe d/yClvjA/soEOOohU3WPMOvgTtuAuydC7HxaH3kSXuHOsEuG/wjj5LyGYrMCr6G5 4RCdtmmfOIVBkPl2Rx5DCPAaPpBK/7Z9MYxWUd5s1o/9KBEQdvusfn0dNaF76nGa z2tUK3Eu75qVD3yrdMgK0VC84BpROsPmMhmU7nQZuTq7o9vIFRn2HdDSpV8yWHat MvEEQxOBaZw2/GQ9BLzn1zNZM4xQLrx/bDlJviGVa92RAQgKyDUypATmtDDCL25h 1JiLaw5ot7ILOL0VbndCIXuhrBjBaQ9GD3OCo8hpgzfgSUcfeZFo1EiqQvLeXYY= =qQ5J -END PGP SIGNATURE- - End forwarded message - ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/186820: [NEW PORTS, UPDATE] Add CentOS 6.5 userland ports
Synopsis: [NEW PORTS, UPDATE] Add CentOS 6.5 userland ports Responsible-Changed-From-To: freebsd-ports-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 31 05:49:11 UTC 2014 Responsible-Changed-Why: assign to mailing list for possible review. http://www.freebsd.org/cgi/query-pr.cgi?pr=186820 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/186232: x11-fonts/linux-f10-fontconfig/Makefile add -f to ln so install works
Synopsis: x11-fonts/linux-f10-fontconfig/Makefile add -f to ln so install works Responsible-Changed-From-To: emulation-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun Mar 23 19:41:00 UTC 2014 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=186232 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/148096: emulators/linux_base-* can not be built from ports on amd64
Synopsis: emulators/linux_base-* can not be built from ports on amd64 State-Changed-From-To: open-feedback State-Changed-By: linimon State-Changed-When: Mon Mar 24 05:06:50 UTC 2014 State-Changed-Why: By now this is a very old PR. To submitter: is it still relevant? Responsible-Changed-From-To: freebsd-emulation-linimon Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 24 05:06:50 UTC 2014 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=148096 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/187006: [hyper-v] dynamic address (dhcp) obtaining doesn't work on HYPER-V OS 2012 R2
Old Synopsis: dynamic address (dhcp) obtaining doesn't work on HYPER-V OS 2012 R2 New Synopsis: [hyper-v] dynamic address (dhcp) obtaining doesn't work on HYPER-V OS 2012 R2 Responsible-Changed-From-To: freebsd-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun Mar 9 15:43:15 UTC 2014 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=187006 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/187203: [hyper-v] CARP protocol not work on HYPER-V 2012 R2
Old Synopsis: CARP protocol not work on HYPER-V 2012 R2 New Synopsis: [hyper-v] CARP protocol not work on HYPER-V 2012 R2 Responsible-Changed-From-To: freebsd-ports-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Mon Mar 10 03:46:19 UTC 2014 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=187203 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/186909: [hyper-v] Stable GENERIC kernel panic on hyperv 2012 OS
Old Synopsis: Stable GENERIC kernel panic on hyperv 2012 OS New Synopsis: [hyper-v] Stable GENERIC kernel panic on hyperv 2012 OS State-Changed-From-To: open-open State-Changed-By: linimon State-Changed-When: Mon Feb 24 06:57:43 UTC 2014 State-Changed-Why: reclassify and assign. Responsible-Changed-From-To: freebsd-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Mon Feb 24 06:57:43 UTC 2014 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=186909 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/184404: [patch] emulators/linux_base-f10: no terminal database installed
Synopsis: [patch] emulators/linux_base-f10: no terminal database installed Responsible-Changed-From-To: emulation-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Mon Dec 2 18:48:42 UTC 2013 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=184404 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: x11-toolkits/linux-f10-gtk description:Gtk library (Linux Fedora 10) maintainer: emulat...@freebsd.org deprecated because: GTK1 is deprecated expiration date:2013-12-01 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-f10-gtk If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/183247: emulators/linux_base-f10 does not build locale archive during installation
Synopsis: emulators/linux_base-f10 does not build locale archive during installation Responsible-Changed-From-To: emulation-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Tue Nov 19 01:45:46 UTC 2013 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=183247 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/183120: x11-toolkits/linux-f10-pango fails to build
Synopsis: x11-toolkits/linux-f10-pango fails to build Responsible-Changed-From-To: freebsd-emulation-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Tue Nov 12 03:05:20 UTC 2013 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=183120 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/183247: emulators/linux_base-f10 does not build locale archive during installation
Synopsis: emulators/linux_base-f10 does not build locale archive during installation Responsible-Changed-From-To: freebsd-emulation-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Tue Nov 12 03:04:52 UTC 2013 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=183247 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/183615: [linprocfs] emulate /proc/sys/kernel/random/uuid
Old Synopsis: linprocfs: emulate /proc/sys/kernel/random/uuid New Synopsis: [linprocfs] emulate /proc/sys/kernel/random/uuid Responsible-Changed-From-To: freebsd-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Wed Nov 6 04:23:39 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=183615 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/180790: devel/linux_kdump prints BSD descriptions of errno names
Synopsis: devel/linux_kdump prints BSD descriptions of errno names Responsible-Changed-From-To: emulation-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Tue Aug 20 00:49:51 UTC 2013 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=180790 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/178955: [virtio] virtio network (if_vtnet) interacts badly with qemu 1.5.0
Old Synopsis: virtio network (if_vtnet) interacts badly with qemu 1.5.0 New Synopsis: [virtio] virtio network (if_vtnet) interacts badly with qemu 1.5.0 Responsible-Changed-From-To: freebsd-bugs-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun May 26 00:09:38 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=178955 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.10.20130313090402.pointyhat/linux_base-fc-4_16.log (Mar 14 00:29:36 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.10.20130313090402.pointyhat/linux_base-fc-4_16.log (Mar 14 00:29:36 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28
Re: kern/177743: [kvm] [panic] kernel panic during `portsnap update` on KVM guest
Old Synopsis: kernel panic during `portsnap update` on KVM guest New Synopsis: [kvm] [panic] kernel panic during `portsnap update` on KVM guest Responsible-Changed-From-To: freebsd-amd64-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Mon Apr 15 01:53:23 UTC 2013 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=177743 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.10.20130313090402.pointyhat/linux_base-fc-4_16.log (Mar 14 00:29:36 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-flashplugin9 forbidden because: CVE-2010-1297 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-flashplugin9 forbidden because: CVE-2010-1297 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/176819: [patch] emulators/linux_base-f10: add symlinks for matlab
Synopsis: [patch] emulators/linux_base-f10: add symlinks for matlab Responsible-Changed-From-To: emulation-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Tue Mar 12 06:54:49 UTC 2013 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=176819 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-flashplugin9 forbidden because: CVE-2010-1297 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
Re: ports/175159: www/linux-f10-flashplugin11 is vulnerable
Synopsis: www/linux-f10-flashplugin11 is vulnerable Responsible-Changed-From-To: emulation-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun Jan 27 10:04:23 UTC 2013 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=175159 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: www/linux-flashplugin9 broken because: unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: www/linux-flashplugin9 broken because: unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: www/linux-flashplugin9 broken because: unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: www/linux-flashplugin9 broken because: unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: www/linux-flashplugin9 broken because: unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/169896: [patch] audio/linux-f10-alsa-lib: use OSS plugin by default
Synopsis: [patch] audio/linux-f10-alsa-lib: use OSS plugin by default Responsible-Changed-From-To: emulation-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Fri Oct 5 03:08:35 UTC 2012 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=169896 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: ports/169988: [PATCH] Update sysutils/linux-procps to 3.2.7; also update to FC10
Synopsis: [PATCH] Update sysutils/linux-procps to 3.2.7; also update to FC10 Responsible-Changed-From-To: emulation-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Fri Oct 5 03:09:13 UTC 2012 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=169988 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: www/linux-flashplugin9 broken because: unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: www/linux-flashplugin9 broken because: unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: www/linux-flashplugin9 broken because: unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: www/linux-flashplugin9 broken because: unfetchable build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.8.2012065352/linux-flashplugin-9.0r289_1.log (_Jun_13_20:34:31_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: kern/169805: [linux] utime() syscall does not work in linuxulator
Old Synopsis: utime() syscall does not work in linuxulator New Synopsis: [linux] utime() syscall does not work in linuxulator Responsible-Changed-From-To: freebsd-i386-freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Mon Jul 16 04:33:51 UTC 2012 Responsible-Changed-Why: reclassify http://www.freebsd.org/cgi/query-pr.cgi?pr=169805 ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked broken
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: www/linux-flashplugin9 broken because: unfetchable build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.8.20120612203020/linux-flashplugin-9.0r289_1.log (_Jun_13_20:34:31_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-flashplugin9 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 lini...@freebsd.org, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: [RFC] Seeking Approval: include bsd.port.pre.mk so SRC_BASE is defined before referenced
Unfortunately certain things need to be defined before bsd.port.pre.mk is included. So, pointy hat to me for giving bad advice. These show up immediately as bad distinfo problems: http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-errorlogs/e.10-exp.20120522050031.pointyhat-west/lsof-4.86,7.log http://pointyhat-west.isc.freebsd.org/errorlogs/amd64-errorlogs/e.10-exp.20120522050031.pointyhat-west/cairo-reference-1.12.2,1.log I have already fixed lsof, but I don't understand cairo-reference. mcl ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
Re: [RFC] Seeking Approval: include bsd.port.pre.mk so SRC_BASE is defined before referenced
Thanks for doing this work. A quick review looks to me to be TRT. I would suggest some minor fixes but only for style: for me, it makes it a bit clearer what's going on if the pre.mk include isn't among the various WITH_* definitions, e.g. net/skystar2. Or maybe just having a blank line before the inclusion would help. Also, for sysutils/fusefs-kmod, I would do the following: - move the MAKE_ENV= definition past the bsd.ports.pre.mk inclusion - throw the SRC_BASE?= line away. mcl ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: accessibility/linux-atk description:Accessibility Toolkit, Linux/i386 binary maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=accessibilityportname=linux-atk portname: archivers/linux-ucl description:RPM of UCL, a lossless data compression library maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-ucl portname: archivers/linux-upx description:RPM of UPX, a high-performance executable packer maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archiversportname=linux-upx portname: audio/linux-esound description:RPM of esound maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-esound portname: audio/linux-libaudiofile description:RPM of audiofile maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-libaudiofile portname: audio/linux-nas-libs description:Runtime libraries for NAS (Linux Fedora Core 4) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audioportname=linux-nas-libs portname: devel/linux-allegro description:Cross-platform game programming library (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-allegro portname: devel/linux-libglade description:RPM of libglade maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libglade portname: devel/linux-libsigc++20 description:Callback Framework for C++ (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-libsigc%2B%2B20 portname: devel/linux-sdl12 description:Cross-platform multi-media development API (linux version) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=develportname=linux-sdl12 portname: emulators/linux_base-fc4 description:Base set of packages needed in Linux mode (for i386/amd64) maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=emulatorsportname=linux_base-fc4 portname: graphics/linux-imlib description:RPM of imlib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-imlib portname: graphics/linux-jpeg description:RPM of the JPEG lib maintainer: emulat...@freebsd.org deprecated because: expiration date:2013-02-28 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-jpeg
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: graphics/linux-tiff description:TIFF library, Linux/i386 binary maintainer: emulat...@freebsd.org status: FORBIDDEN deprecated because: expiration date:2011-10-14 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-f10-flashplugin10 description:Adobe Flash Player NPAPI Plugin maintainer: emulat...@freebsd.org status: FORBIDDEN deprecated because: has vulnerabilities and is EOL expiration date:2012-03-27 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango description:Linux pango binary maintainer: emulat...@freebsd.org status: FORBIDDEN deprecated because: expiration date:2011-10-14 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: graphics/linux-tiff description:TIFF library, Linux/i386 binary maintainer: emulat...@freebsd.org status: FORBIDDEN deprecated because: expiration date:2011-10-14 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-f10-flashplugin10 description:Adobe Flash Player NPAPI Plugin maintainer: emulat...@freebsd.org status: FORBIDDEN deprecated because: has vulnerabilities and is EOL expiration date:2012-03-27 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango description:Linux pango binary maintainer: emulat...@freebsd.org status: FORBIDDEN deprecated because: expiration date:2011-10-14 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: graphics/linux-tiff description:TIFF library, Linux/i386 binary maintainer: emulat...@freebsd.org status: FORBIDDEN deprecated because: expiration date:2011-10-14 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: www/linux-f10-flashplugin10 description:Adobe Flash Player NPAPI Plugin maintainer: emulat...@freebsd.org status: FORBIDDEN deprecated because: has vulnerabilities and is EOL expiration date:2012-03-27 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango description:Linux pango binary maintainer: emulat...@freebsd.org status: FORBIDDEN deprecated because: expiration date:2011-10-14 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently scheduled for deletion
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install correctly from their sources, or otherwise fail in operation. The ports, and the reason and date that they have been scheduled for removal, are listed below. If no one has stepped forward before that time to propose a way to fix the problems (such as via a PR), the ports will be deleted. portname: graphics/linux-tiff description:TIFF library, Linux/i386 binary maintainer: emulat...@freebsd.org status: FORBIDDEN deprecated because: expiration date:2011-10-14 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: x11-toolkits/linux-pango description:Linux pango binary maintainer: emulat...@freebsd.org status: FORBIDDEN deprecated because: expiration date:2011-10-14 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
FreeBSD ports that you maintain which are currently marked forbidden
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users about ports that are marked as forbidden in their Makefiles. Often, these ports are so marked due to security concerns, such as known exploits. An overview of each port, including errors seen on the build farm, is included below. portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphicsportname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkitsportname=linux-pango If this problem is one 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. Thanks for your efforts to help improve FreeBSD. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to freebsd-emulation-unsubscr...@freebsd.org
