Uploaded zope 2.1.3-1 (arm) to master
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.6
Date: Tue, 25 Jan 2000 09:54:20 +0100
Source: zope
Binary: zope
Architecture: arm
Version: 2.1.3-1
Distribution: frozen unstable
Urgency: high
Maintainer: jim@federated.com
Description:
zope - The Z Object Publishing Environment
Closes: 46015 54917
Changes:
zope (2.1.3-1) frozen unstable; urgency=high
.
* IMPORTANT CHANGE: Changed the default port to 9673. The former default,
8080, conflicted with proxy servers like squid, wwwoffle etc.
(closes: #46015).
.
ZServer now by default starts its HTTP server on port 9673, use
http://localhost:9673 to access it. The FTP server is started on port
8021, the control monitor on port 8099. To change this, refer to
README.Debian.
.
To the archive maintainer: This should solve many installation problems
that were not recorded in the BTS. Upgrading from a previous release,
the user will be warned!
.
* Also reflected this in the documentation. Added a section "Differences to
upstream" to README.Debian and mention the directory structure in
/var/lib/zope (closes: #54917).
.
* New upstream version, which is only a bug fix release. 2.1.3 fixes one
grave bug, where the database was corrupted when the administrator tried
to pack it (closes: grave #56164, closes: important #56271).
.
The only changes in 2.1.3 are the following things, there is no new code
nor new features:
.
- A race condition in the logic for managing Zope database connections
caused Zope to hang on very busy sites.
- A bug in the packing code that caused records to be nreadable after:
o someone did work in a version
o Someone did an (unrelated) undo
o the version was committed
and the database was packed to a time before the work was done in the
version.
- Fixed a bug that caused packing to raise an
error in the following situation:
o someone modifies and then deletes an object in a version.
o they commit the version
o the database is packed between the time the object is deleted and
the time the version is committed.
- Fixed a bug that caused Zope to sometimes hang instead of shutting
down or restarting when accessed over a fast network.
- It wasn't possible to use a ZClass instance as a method of a ZClass.
Files:
20929370f3bfb83f233612a331d7ea81 1134284 web optional zope_2.1.3-1_arm.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
iQCVAwUBOKKpPjb8oJEootMxAQGmJwP/VV/gnGQMfVv4XQ3JffpSHoKpusqmRfrM
5nhEsJEcnajNytFdG5+ZU61cBRqz0dvdOPpTj96Zy2GitR1ktwLN/aaUN1LDjcPq
gK035BkKlp5u/ZGqTItyltAlVbX9OBkC/C6IaKfSI6RIDTraRn/Nb9qjOEXqZQH9
tRhamTJ5zhk=
=Jlw5
-----END PGP SIGNATURE-----
Reply to: