| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
malware's contributions:
* SECURITY: Removed possible format string exploits.
* FIXED: statistics color saving/loading.
* FIXED: a possibly exploitable bug as noticed by S. Esser from e-matters.
* FIXED: exception handling for CString/wxString.
* FIXED: endless loop in CClientUDPSocket::OnSend().
* FIXED: fatal exception handler not to fail in early stages.
* FIXED: endless loop in CListenSocket::KillAllSockets().
* FIXED: Lagloose's Shift+Doubleclick to show really only transfering
sources. Update still does not work.
* Decode %-escaped characters in URL within the ed2k application as
suggested by __JusSx__.
NetBSD team's contributions:
* Work-around not to unlock mutexes not locked.
* Try to increase some resource limits to the permitted maximum.
* FIXED: bug with the mutex protecting calls to gethostbyname.
Un-Thesis' contributions:
* Added support for adding multiple ED2K links.
* Added ED2K link support for GTK2.
FooMan's contributions:
* FIXED: for failing file access during download completion.
|
|
|
|
|
|
${PREFIX}/share/mk before installing into it.
|
|
on tech-pkg@ at various times. This means that regardless of what kind of
GL support comes with X11, if a package depends on GL, Mesa 5.0.1 (or higher)
will be installed into ${LOCALBASE}.
Some troubleshooting after the latest patches by Krister Walfridsson.
|
|
|
|
* New "--gnupg" option (set by default) that disables --openpgp,
and the various --pgpX emulation options. This replaces
--no-openpgp, and --no-pgpX, and also means that GnuPG has
finally grown a --gnupg option to make GnuPG act like GnuPG.
* A number of portability changes to make building GnuPG on
less-common platforms easier.
* Romanian translation.
* Two new %-expandos for use in notation and policy URLs. "%g"
expands to the fingerprint of the key making the signature
(which might be a subkey), and "%p" expands to the fingerprint
of the primary key that owns the key making the signature.
* New "tru" record in --with-colons --list-keys listings. It
shows the status of the trust database that was used to
calculate the key validity in the listings. See doc/DETAILS for
the specifics of this.
* New REVKEYSIG status tag for --status-fd. It indicates a valid
signature that was issued by a revoked key. See doc/DETAILS for
the specifics of this.
|
|
|
|
in June of this year, but for which I got no response.
1) Sourceforge PR #72673: Get the program name for the usage statement
in the most portable fashion possible, using argv.
2) Sourceforge PR #762825, which is a rework of PR #504855, by Adam
Lewandowski. Add a "table of contents" command, included a "+v"
option to dump absolutely all of the information in the par file.
Bump ${PKGREVISION}.
I think it's safe to say that this is the final release. The current
"par2", for version 2 parity files, is now backwards compatible with
the version 1 parity files that this program generates. It does not,
however, seem to have the cool "table of contents" feature.
|
|
|
|
Changes:
* fix a problem with handling of exceptions that was uncovered by
Python 2.3.
* disable assigning to unknown attributes on stub instances. Saves
a little memory too.
* add CORBA.ORB.work_pending() and CORBA.ORB.perform_work() methods.
|
|
|
|
Changes:
* Fix up a duplicate symbol bug in the atk module, that was causing
build problems on MacOS X (hopefully the last such problem).
* add gtk.glade.set_custom_handler() API, that provides more info to
the custom widget callback. Deprecate set_custom_widget_callbacks().
* some other bug fixes.
|
|
build.
|
|
library. -lxxx sometimes fails for strange reasons
|
|
OK'ed by drochner@
|
|
an operating system does not have a 'make' (ie only bmake), or if the OS
supplied 'make' is sufficiently broken (Irix), this will cause the build to
fail (interestingly enough apparently only if build as a dependency, not
if build from this directory).
Patch Makefiles to use @MAKE@, which then, after patching, is substituted with
the actual ${MAKE} (can't use "MAKE= ${MAKE} -f Makefile.ssl").
While here, tweak Irix configure a bit.
|
|
Following suggestions by Martin Husemann and Todd Vierling.
|
|
PR #22566
|
|
|
|
|
|
sector chunks. this flag has already been included by the upstream and
will be in the next release of bchunk.
|
|
to make it easier to track new versions.
|
|
changes2html script
|
|
changes are basically bugfixes, and improvements in the FPGA synthesis
area
|
|
|
|
|
|
|
|
changes:
- Updated for current autoconf/gcc build environment.
- Some uninitialized memory references were found by 'valgrind'.
- Slightly improved writeout/commit performance.
- Explicitly yields to other threads during long running RVM operations.
- More portable detection of fdatasync availability.
- Some more memory initialization fixes, and passing an actual iov
struct to readv/writev instead of something that looks like it.
|
|
changes (partial):
- Updated for current autoconf/gcc build environment.
- Some cleanups for the code generated by the rp2gen stub generator.
- Hopefully improved 'timeout' behaviour on asynchronous links (ADSL).
Fixes memory corruptions that typically hit during reintegration, andperformance
problems when writing data to the servers.
- Now internally supports >2GB files, however we're not really using
this new capability in Coda yet.
- Re-added a lost lseek that was causing truncated backup files.
Small files that got piggybacked on the outgoing RPC2 packets were
only sent to one server in a replicated group. The operation on the
other servers fails and the client disconnected. The next time the
servers are accessed this inconsistency was detected and
automatically resolved. But doing it right in the first place is
somewhat more efficient and reliable.
The RPC2 random number generator was not initialized correctly. Not
sure how much effect this had on connection handling and other
places that liked random numbers to be unique.
Removed MultiRPC pool allocator, now we can have more than 8 concurrent RPC
operations. And because the per-user limit got removed in Coda-6.0.2, this is
more likely to happen.
A packet with random data could easily trigger an assertion in the MultiRPC
decoding. Now we simply drop it and avoid the possible DoS.
IPv6 support, it is just waiting for the right flag from userspace. As a
result the 1.19 API is binary compatible for older clients and servers.
Removed sftp listener and timeout threads. We always run what was previously
called 'masqueraded'. This works fine as long as our peer uses rpc2-1.9
or later.
|
|
changes:
- Updated for current autoconf/gcc build environment.
- Some uninitialized memory references were found by 'valgrind'.
|
|
|
|
dependent package.
|
|
refer /usr/pkg/include/pthread.h
|
|
|
|
|
|
|
|
Better compatibility with Mozilla/MSIE behaviour.
==== Changes since 3.27 ====
2003-08-19 Gisle Aas <gisle@ActiveState.com>
Release 3.31
The -DDEBUGGING fix in 3.30 was not really there :-(
2003-08-17 Gisle Aas <gisle@ActiveState.com>
Release 3.30
The previous release failed to compile on a -DDEBUGGING perl
like the one provided by Redhat 9.
Got rid of references to perl-5.7.
Further fixes to avoid warnings from Visual C.
Patch by Steve Hay <steve.hay@uk.radan.com>.
2003-08-14 Gisle Aas <gisle@ActiveState.com>
Release 3.29
Setting xml_mode now implies strict_names also for end tags.
Avoid warning from Visual C. Patch by <gsar@activestate.com>.
64-bit fix from Doug Larrick <doug@ties.org>
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=195500
Try to parse similar to Mozilla/MSIE in certain edge cases.
All these are outside of the official definition of HTML but
HTML spam often tries to take advantage of these.
- New configuration attribute 'strict_end'. Unless enabled
we will allow end tags to contain extra words or stuff
that look like attributes before the '>'. This means that
tags like these:
</foo foo="<ignored>">
</foo ignored>
</foo ">" ignored>
are now all parsed as a 'foo' end tag instead of text.
Even if the extra stuff looks like attributes they will not
be reported if requested via the 'attr' or 'tokens' argspecs
for the 'end' handler.
- Parse '</:comment>' and '</ comment>' as comments unless
strict_comment is enabled. Previous versions of the parser
would report these as text. If these comments contain
quoted words prefixed by space or '=' these words can
contain '>' without terminating the comment.
- Parse '<! "<>" foo>' as comment containing ' "<>" foo'.
Previous versions of the parser would terminate the comment
at the first '>' and report the rest as text.
- Legacy comment mode: Parse with comments terminated with a
lone '>' if no '-->' is found before eof.
- Incomplete tag at eof is reported as a 'comment' instead
of 'text' unless strict_comment is enabled.
2003-04-16 Gisle Aas <gisle@ActiveState.com>
Release 3.28
When 'strict_comment' is off (which it is by default)
treat anything that matches <!...> a comment.
Should now be more efficient on threaded perls.
|
|
|
|
|
|
Various fixes including:
* Fix grepping of standard input.
* Fix -Z.
* Correctly determine whether to output filenames when only one argument.
* Make output with -A,-B,-C flags consistent with GNU grep.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
