[kde-freebsd] FreeBSD ports that you maintain which are currently scheduled for deletion

2008-01-07 Thread linimon
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:   misc/kde3-i18n-id
description:Indonesian messages and documentation for KDE3
maintainer: [EMAIL PROTECTED]
status: BROKEN
deprecated because: Distfile no longer available, outdated
expiration date:2007-12-31
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.2008010321/id-kde-i18n-3.0.5_1.log
 (Jan  1 07:10:22 UTC 2008)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=kde3-i18n-id


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.
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd


[kde-freebsd] FreeBSD ports that you maintain which are currently marked broken

2008-01-07 Thread linimon
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 5.x/6.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:   misc/kde3-i18n-id
broken because: Distfile no longer available, outdated
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.2008010321/id-kde-i18n-3.0.5_1.log
 (Jan  1 07:10:22 UTC 2008)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=kde3-i18n-id


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 <[EMAIL PROTECTED]>, so that he can attempt to fix the
problem in the future.

Thanks for your efforts to help improve FreeBSD.
___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd


[kde-freebsd] Current problem reports assigned to [EMAIL PROTECTED]

2008-01-07 Thread FreeBSD bugmaster
Current FreeBSD problem reports
Critical problems
Serious problems
Non-critical problems

S Tracker  Resp.  Description

o ports/94093  kdeqt/KDE install from ports creates files owned by root 
o ports/107505 kdemultimedia/kdemultimedia: kmix - XF86RaiseVolume, XF86
f ports/107643 kdenet/lanbrowsing lisa don`t start on system boot
o ports/113295 kdenet-im/kopete: pleawse add 'make config' to choose kop
a ports/116484 kde[PATCH] OPTIONS'ify x11/kdelibs3
o ports/117440 kdemisc/kdeedu3 - Request to package README.ephemerides f
o ports/117947 kdedeskutils/kdepim3 - Kmail Disconnected IMAP + Korganiz
o ports/117960 kdePatches to enable webcam support in net-im/kopete
o ports/118046 kdePorts dependent upon devel/qt4-corelib or x11-toolkits

9 problems total.

___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.org/mailman/listinfo/kde-freebsd