Free rc1 software for mac

OpenLieroX 0.57 rc1 brings you an attractive kind of a realtime Worms which based and compatible to the famous LieroX. LieroX is a 2D shooter game. It is an unofficial sequel to Liero, and is the most popular of all the Liero clones. It features online play, fully customizable weapons, levels and characters. Liero Xtreme was created in C++ by Jason 'JasonB' Boettcher, an Australian programmer.

The game is based on a deathmatch setting, where multiple players face off in a closed level. Each player is equipped with five weapons selected out of all the weapons allowed, and with a ninja rope that allows the player to move in any direction. Players begin with a set amount of lives, and whilst the game records the number of kills, the last man standing is usually considered the winner. LieroX also allows team deathmatches, which has made it common for players to form clans.

Because of the huge community, there are dozens of levels and mods available. You also have no problem to find somebody on Internet to play with. Or if you want to play offline, you also can play with bots.

Major Features:

1. Old-fashioned gaming style derived from Worms and Liero
2. Internet/LAN multiplayer games support for endless fun with friends
3. Customizable characters (skins, names, ...)
4. Thousands of maps and custom weapons
5. Custom themes to adjust the game look
6. Built-in level editor
7. And many more, just check them out!

GifToAPNG Converter is a free and open source application that can convert animated gif files into animated apng files.

System requirements:
-

Enhancements
- improved commandline usage since RC1

Bazaar is a distributed version control system available under the GPL that reduces barriers to participation in your project.
Bazaar is designed to support Mac OS, GNU/Linux, UNIX, Windows. In summary, Bazaar gives you fast, distributed revision control that "Just Works", supporting renames of directories and files smoothly.
Bazaar is designed to maximise the level of community participation in your project.
Bazaar branches can be published on any web server, and uploaded over sftp, ftp, or rsync. If you want the fastest possible network performance, there is a smart server.
Bazaar supports flexible work models: centralized like cvs or svn, commit offline, enforced code review when desired, and automatic regression testing.
Decentralized revision control systems give people the ability to collaborate more efficiently over the internet using the bazaar development model and have many other advantages.
When you use Bazaar, you can commit to your own local branches of your favourite free software projects without needing special permission.

Main features:
Good performance:
- Bazaar status in a tree of 5,000 files takes just 0.5 seconds, so almost every open source project can get the advanced features of Bazaar without slowing down its developers. Bazaar is robust in the face of radical tree restructuring, saving you time when it comes to merging from your community.
Safe with your data:
- There have not been any data loss bugs in a Bazaar release in the past two years. Bazaar has a huge test suite that ensures that new file formats can be tested automatically. The development process follows best practice with code review of all core and community code landings.
Friendly:
- Bazaar "Just Works" (which is why the Ubuntu team chose it for their project). Bazaar has a natural feel, you can publish your code on any web server or use a custom server for performance. Bazaar has perfect support for renaming files AND directories, which means you can unleash your community and merge efficiently even from contributors who are radically restructuring the tree.
Free:
- Bazaar is available under the GPL v2 or later.
Easy to integrate:
- Bazaar is designed as a Python API with a plugin system, so it is easy to embed in your tools and projects and easy to extend or integrate with existing infrastructure. Whether you are managing your development, or keeping track of configuration files, or building a new content management system, Bazaar is a great choice if you like to work in Python.

System requirements:
-

Enhancements
Compatibility Breaks:
- Display prompt on stderr (instead of stdout) when querying users so that the output of commands can be safely redirected. (Vincent Ladeuil, #376582)
New Features:
- A new repository format 2a has been added. This is a beta release of the the brisbane-core (aka group-compress) project. This format now suitable for wider testing by advanced users willing to deal with some bugs. We would appreciate test reports, either positive or negative. Format 2a is substantially smaller and faster for many operations on many trees. This format or an updated version will become the default in bzr 2.0.
- This is a rich-root format, so this repository format can be used with bzr-svn. Bazaar branches in previous non-rich-root formats can be converted (including by merge, push and pull) to format 2a, but not vice versa. We recommend upgrading previous development formats to 2a.
- Upgrading to this format can take considerable time because it expands and more concisely repacks the full history.
- If you use stacked branches, you must upgrade the stacked branches before the stacked-on branches. (See )
- --development7-rich-root is a new dev format, similar to --dev6 but using a Revision serializer using bencode rather than XML. (Jelmer Vernooij, John Arbash Meinel)
- mail_client=claws now supports --body (and message body hooks). Also uses configured from address. (Barry Warsaw)
Improvements:
- --development6-rich-root can now stack. (Modulo some smart-server bugs with stacking and non default formats.) (John Arbash Meinel, #373455)
- --development6-rich-root delays generating a delta index for the first object inserted into a group. This has a beneficial impact on bzr commit since each committed texts goes to its own group. For committing a 90MB file, it drops peak memory by about 200MB, and speeds up commit from 7s => 4s. (John Arbash Meinel)
- Numerous operations are now faster for huge projects, i.e. those with a large number of files and/or a large number of revisions, particularly when the latest development format is used. These operations (and improvements on OpenOffice.org) include: branch in a shared repository (2X faster), branch --no-tree (100X faster), diff (2X faster), tags (70X faster) (Ian Clatworthy)
- Pyrex version of bencode support. This provides optimized support for both encoding and decoding, and is now found at bzrlib.bencode. bzrlib.utils.bencode is now deprecated. (Alexander Belchenko, Jelmer Vernooij, John Arbash Meinel)
Bug Fixes:
- Bazaar can now pass attachment files to the mutt email client. (Edwin Grubbs, #384158)
- Better message in bzr add output suggesting using bzr ignored to see which files can also be added. (Jason Spashett, #76616)
- bzr pull -r 123 from a stacked branch on a smart server no longer fails. Also, the Branch.revision_history() API now works in the same situation. (Andrew Bennetts, #380314)
- bzr serve on Windows no longer displays a traceback simply because a TCP client disconnected. (Andrew Bennetts)
- Clarify the rules for locking and fallback repositories. Fix bugs in how RemoteRepository was handling fallbacks along with the _real_repository. (Andrew Bennetts, John Arbash Meinel, #375496)
- Fix a small bug with fetching revisions w/ ghosts into a new stacked branch. Not often triggered, because it required ghosts to be part of the fetched revisions, not in the stacked-on ancestry. (John Arbash Meinel)
- Fix status and commit to work with content filtered trees, addressing numerous bad bugs with line-ending support. (Ian Clatworthy, #362030)
- Fix problem of "directory not empty" when contending for a lock over sftp. (Martin Pool, #340352)
- Fix rule handling so that eol is optional, not mandatory. (Ian Clatworthy, #379370)
- Pushing a new stacked branch to a 1.15 smart server was broken due to a bug in the BzrDirFormat.initialize_ex smart verb. This is fixed in 1.16, but required changes to the network protocol, so the BzrDirFormat.initialize_ex verb has been removed and replaced with a corrected BzrDirFormat.initialize_ex_1.16 verb. 1.15 clients will still work with a 1.16 server as they will fallback to slower (and bug-free) methods. (Jonathan Lange, Robert Collins, Andrew Bennetts, #385132)
- Reconcile can now deal with text revisions that originated in revisions that are ghosts. (Jelmer Vernooij, #336749)
- Support cloning of branches with ghosts in the left hand side history. (Jelmer Vernooij, #248540)
- The bzr diff now catches OSError from osutils.rmtree and logs a helpful message to the trace file, unless the temp directory really was removed (which would be very strange). Since the diff operation has succeeded from the users perspective, no output is written to stderr or stdout. (Maritza Mendez, #363837)
- Translate errors received from a smart server in response to a BzrDirFormat.initialize or BzrDirFormat.initialize_ex request. This was causing tracebacks even for mundane errors like PermissionDenied. (Andrew Bennetts, #381329)
Documentation:
- Added directory structure and started translation of docs in Russian. (Alexey Shtokalo, Alexander Iljin, Alexander Belchenko, Dmitry Vasiliev, Volodymyr Kotulskyi)
API Changes:
- Added osutils.parent_directories(). (Ian Clatworthy)
- bzrlib.progress.ProgressBar, ChildProgress, DotsProgressBar, TTYProgressBar and child_progress are now deprecated; use ui_factory.nested_progress_bar instead. (Martin Pool)
- graph.StackedParentsProvider is now a public API, replacing graph._StackedParentsProvider. The api is now considered stable and ready for external users. (Gary van der Merwe)
- bzrlib.user_encoding is deprecated in favor of get_user_encoding. (Alexander Belchenko)
- TreeTransformBase no longer assumes that limbo is provided via disk. DiskTreeTransform now provides disk functionality. (Aaron Bentley)
Internals:
- Remove weave.py script for accessing internals of old weave-format repositories. (Martin Pool)
Testing:
- The number of cores is now correctly detected on OSX. (John Szakmeister)
- The number of cores is also detected on Solaris and win32. (Vincent Ladeuil)
- The number of cores is also detected on FreeBSD. (Matthew Fuller)

CD and DVD media keep their data only for a finite time (typically for many years). After that time, data loss develops slowly with read errors growing from the outer media region towards the inside.
dvdisaster stores data on CD/DVD (supported media) in a way that it is fully recoverable even after some read errors have developed. This enables you to rescue the complete data to a new medium.
Data loss is prevented by using error correcting codes. Error correction data is either added to the medium or kept in separate error correction files. dvdisaster works at the image level so that the recovery will not depend on the file system of the medium. The maximum error correction capacity is user-selectable.
Common misunderstandings about dvdisaster:
- dvdisaster can not make defective media readable again. Contents of a defective medium can not be recovered without the error correction data.
- Such functions are outside the scope of dvdisasters internal design and goals.

Enhancements
- Documentation and locale cleanup for en, de
- added app bundle creation for Mac OS X
- Graphical bug: red/green sector markings were incorrect when doing
- linear reading with high sector skip numbers. Fixed.
- Speed curve will no longer travel below the x axis.
- fixed rare crash while linear reading due to a race condition
- by improper ClearCrcCache() usage.
- fixed bogus dead sector warning in the linear reader
- after encountering unreadable sectors
- made adaptive reading pursue raw reading more aggressively;
- effectively trading in place re-reads for seeks over
- the medium.
- help output for --defective-dump was complete nonsense. Fixed.
- detection of read errors at the end of track at once disks
- would sometimes cut off too many sectors when doing multiple
- reading passes and a carefully crafted number of extra read
- errors occurred. Fixed.
- fixed crash in command line mode when doing multiple
- reading passes.

POPFile is an email classification tool with a Naive Bayes classifier, POP3, SMTP, NNTP proxies and IMAP filter and a web interface.
POPFile classifies email into categories you define. It can sort into spam and not spam or into any number of categories you like (e.g. work, personal, important project, hobby, etc.).
The classification is done using a native Bayes algorithm. In other words, POPFile uses statistics to track which words are likely to appear in which messages. This means that POPFile will adapt to the kind of mail you receive and needs to be trained.
Out of the box, it doesnt know anything about spam or how messages from your mother differ from those your friends send you. However, if you train it, it will soon learn how to tell these different kinds of messages apart.
POPFile is a cross-platform solution that will run on most platforms and with most email clients.

Enhancements
- Includes a lot of changes, including support for SQLite 3.x, improved versions of the Windows service and system tray programs and, at last, an installer for Mac OS X.