setuid root bit, which is off by default. The purpose is to avoid
having users who don't use kcheckpass become vulnerable to a root
exploit. For more details see the actual pkg-message. Bump PORTREVISION
to reflect this change in the package.
As a side note, I'm a little wary about adding something like this so
close to the ports freeze for 4.4-RELEASE. However, I decided that it
was a minimal risk and went ahead with it in the hopes of avoiding the
need for users to run into this "problem" themselves...
Bump PORTREVISION just in case this is needed.
From Mikhail Teterin:
> Well, for the same reason the xslt.cpp sometimes works -- in fact, it
> worked for everyone, until someone tried it on current.
>
> In essence, the code reads the whole file into a buffer. It then tries
> to turn that buffer into one of qt's string-objects (QCString). The
> class' constructor they chose assumes, it is passed a valid (aka
> \0-terminated) string and goes through the buffer looking for the first
> 0-byte. The file itself does not contain any, so it happily wonders
> behind the real end of the buffer until it either finds a stray 0-byte,
> or seg-faults, trying to read a wrong page.
>
> Apparently, more often than not, some stray 0-byte is there -- no
> surprise. But it will usually create a string that's longer than the
> file size -- unless the 0-byte happens to be right there at the end of
> the buffer. Apparently, the lamer, who wrote it, noticed something
> strange, so he/she explicitly truncates the created QCString object to
> the known size of the file after instantiation:
>
> contents.truncate(xmlFile.size())
>
> My patch modifies the code to use the correct QCString constructor --
> the one, that accepts the maximum size of the string. This does the
> right thing -- once it reaches the end of the buffer, it stops,
> allocates the private storage (I hate C++ for all this buffer copying),
> appends the 0-byte and creates the object of the expected size. No
> truncation is needed....
Thanks to Mikhail for his debugging on this problem; this patch further
removes the hazard of meinproc coredumps.
Submitted by: mi
gets unresolved symbols when accessing fb routines at server startup.
Note, this is apparently already in the mainline XFree86 sources,
so this patch may need to be removed when the port is updated for
the next release of XFree86
Tested by: "Eric S. Van Gyzen" <eric@stat.Duke.EDU>
problem is is that there are a few sloppy pieces of code in xslt.cpp.
Bump PORTREVISION to account for recent changes (I had intended to do this
much earlier, but wanted to include these patches first, and there was
a problem getting them together correctly).
Submitted by: mi
Tested by: dwcjr, petef
when KDE (N+1).x (N = radix 2, shift 1, order 1) is installed to
pre-extract so one can still download the distfiles for (N+1).x.
PR: 30167
Submitted by: Thierry Thomas <thierry@thomas.as>
maintain and improve QT/KDE on FreeBSD. This group (at this time)
consists of: demon, olgeni, kevlo, lauri@kde.org, rwatson, and will.
While I'm here, fail build of kdelibs11 if kdelibs2 is installed. This
was originally supposed to be committed with the 2.2 update, but...
shared among all epplets that should be created and "owned" by the
libepplet port, but they aren't. They are created and owned by the
epplets port, so depend on epplets again until that is fixed.
no-op script. This prevents the port from appending content to
/etc/pam.conf, which is known to break kscreensaver's password
verification, without asking first. Binary packages already left
/etc/pam.conf alone.
