FreeBSD ports that you maintain which are currently marked broken

[Philip M. Gollucci]

All,

I no longer use rsyslog at $work.  Are there any interested maintainers and
its 3 dependencies.  Note, you'll want to be familiar with C to debug core
dumps
and svn cp/svn mv to keep up with the release strategy.

devel/libee
devel/libestr
devel/librelp

sysutils/rsyslog5
sysutils/rsyslog5-dbi
sysutils/rsyslog5-gnutls
sysutils/rsyslog5-gssapi
sysutils/rsyslog5-mysql
sysutils/rsyslog5-pgsql
sysutils/rsyslog5-relp
sysutils/rsyslog5-rfc3195
sysutils/rsyslog5-snmp
sysutils/rsyslog6-devel
sysutils/rsyslog6-devel-dbi
sysutils/rsyslog6-devel-gnutls
sysutils/rsyslog6-devel-gssapi
sysutils/rsyslog6-devel-mysql
sysutils/rsyslog6-devel-pgsql
sysutils/rsyslog6-devel-relp
sysutils/rsyslog6-devel-rfc3195
sysutils/rsyslog6-devel-snmp



On Tue, Aug 7, 2012 at 8:28 AM, <linimon at freebsd.org> wrote:

> 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/rsyslog5-snmp
> broken because:     Does not link on i386: can't find symbol snmp_timeout
>                     in libnetsnmp
> build errors:       none.
> overview:
> http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=rsyslog5-snmp
>
>
> portname:           sysutils/rsyslog6-devel-snmp
> broken because:     Does not link on i386: can't find symbol snmp_timeout
>                     in libnetsnmp
> build errors:       none.
> overview:
> http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=rsyslog6-devel-snmp
>
>
> 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 <linimon at FreeBSD.org>, so that he can attempt to fix the
> problem in the future.
>
> Thanks for your efforts to help improve FreeBSD.
>



-- 
---------------------------------------------------------------------------------------------
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci at p6m7g8.com) c: 703.336.9354
Member,                           Apache Software Foundation
Committer,                        FreeBSD Foundation
Consultant,                       P6M7G8 Inc.
Director Operations,      Ridecharge Inc.

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.