Yes I did a release just to fix one bug: #2038862 - compress_sparse assert when 100%. The assert happened to me two times in a row so I thought it important enough to fix immediately.
Please remember the Feature Requests and Bug tracker are under the Objectify project also on SourceForge: http://sourceforge.net/projects/objectify
There are still a couple of bugs listed in the New World OS Bug tracker, but please file any new bugs in the Objectify project. Thanks!... read more
The major change in this version is that I reversed the encryption so that blowfish runs first and then the data is scrambled. My theory is that makes it more secure because there aren't any clues as to how to unscramble it. In the old order if someone were to break through the blowfish encryption there would be clues as to where the bytes should go.
The only change in the Alpha_28.4 release is that disc logging can now deal with subdirectories on the disc. Prior to this all files had to be in root directory of the disc and there could not be any subdirectories.
Please note: I am in the process of moving Objectify (which is an implementation of some of my OS ideas which runs on top of another OS) to it's own project: http://sourceforge.net/projects/objectify. The CVS and release files are still under the New World OS project. There are a few old bugs also still under the NWOS tracker. The new bugs and Feature Requests are under the Objectify tracker.... read more
This release was to fix several problems after restoring (expand_sparse) a compressed file that was created with version Alpha_26 (0026).
Also fixed to import a file that had been previously put in the system via a disc_list.
Please remember that the Feature Requests are in the Objectify project: http://sourceforge.net/projects/objectify
Thanks for trying it out, please report any problems you find (I am now doing the Bug Tracker on the Objectify project too: http://sourceforge.net/projects/objectify
This release fixed a few Bugs (#2015898, #2004217, and #2001629) and added a couple of Feature Requests (#1996867 and #1993875). Note: Feature Request #1993875 and Bug #2001629 were duplicates.
It should now terminate if it cannot open the backup file.
Verify_file -r should work now even if files (as opposed to directories) are listed on the command line.
And lastly, export_c_structs will not fail when the public_objects file is read_only.... read more
I have put a new release of Objectify up, it has a couple of bug fixes, including the normalization of paths when doing import_file -r or verify_file -r. For example it will take a path like "./whatever///junk/..//xyzzy" and normalize it to "whatever/xyzzy".
I however have not made any changes for the problem of importing recursively and the backup .dif files. I do not know yet how I am going to deal with the backup files when you are importing large amounts of files. What I am recommending you do for now, if you need to do a large amount of data (over say 20-30 megabytes) is to do a backup (using compress_sparse), turn off backups (.dif files), do the import_file -r, do a new backup with compress_sparse, and turn backups (.dif files) back on. Sorry for the extra hassle.
I will try to come up with a better solution soon.... read more
I have never used import_file --recursive with backup (.dif) files enabled before. It turns out that it can generate huge file that take a long time to sort.
I recommend not using the --recursive feature until I can fix this and the path problems. I intend to release a new version with fixes tomorrow or the next day.
I have discovered a bad thing happens if you recursively import a directory with import_file and include the slash on the directory name. For example if you do this:
import_file -r xyzzy/
It will store the file paths with an extra slash (xyzzy//twisty_maze.jpg) and then verify_file won't match it up.
I will be checking in a fix in the next few days.
Please avoid having the slash on any directories you import until then. This should work fine:... read more
I forgot and left the two Gobuntu-8.04 .iso files out of the previous (080614-0028) release. They have been added in this release.
I don't plan to update the Public Objects again in the next few days so feel free to update them. I'm sorry I ended up doing so many releases in the past few days.
I thought I had added all of the Ubuntu, Kubuntu, Edubuntu, Xubuntu, Ubuntu Studio, Mythbuntu, etc. release 8.04 .iso files. However, I just realized while I was creating this release that I did the same thing that I did with the 7.10 release and forgot to include the Gobuntu files.
So once again I don't recommend updating your Public Objects yet, because I will be releasing a new version that includes the Gobuntu 8.04 .iso files either later today or tomorrow.... read more
I forgot to add the Gobuntu 7.10 files:
to yesterdays (080611-0028) release. The only changes in this release are the addition of those files.
I don't recommend spending time updating right now because I should be adding all of the files for the Ubuntu 8.04 release in the next day or two. If you are going to upgrade the public objects, it makes sense to just wait and upgrade when the 8.04 files are in too.
Added all of the Ubuntu 7.10 release .iso files (including Ubuntu, Kubuntu, Edubuntu, Xubuntu, Ubuntu Studio, etc.).
I have updated the Public Objects with the Ubuntu source .iso files from 5.04 to 6.06.1.
Please remember the Feature Requests for Objectify are under the Objectify project: http://sourceforge.net/projects/objectify.
Fixed Bug #1954154 - this required moving the file revision links from the FILE objects into the PATH AND FILE ASSOCIATION objects.
To signify that the objects changed I changed the version string from 0027 to 0028. To upgrade the archive you will need to do a compress sparse, expand_sparse, and then run the new upgrade_files_0028 program to move the file revision links. You will need to run upgrade_files_0028 for every pass phrase you use.
I decided to do a May release WITHOUT a fix for Bug #1954154: Assert when creating disc_list. That bug only occurs under certain circumstances (using --add-revision with a file that has multiple names) and should happen rarely. The fix is complicated and I hope to have a fix in the next release.
This release has a few new features, such as import_file and verify_file have a recursive option and list_discs will take a disc ID with wild cards on the command line.... read more
While the fix for Bug #1954154 isn't in itself complicated, repairing the objects that have already been created is.
I am also wondering if this is a good point in time to fix another problem: forking a file. Currently the system cannot handle two files being derived from another file.
In any case it may be another week or two before I have a fix.
I normally try to do a release on the 4th of each month. However, a couple of bugs have surfaced in the past few days:
1957144 Bad data checksum when doing list_files --revision
1954154 Assert when creating disc_list
I have decided to implement a fix for these before doing the May release.
Please note: The New World OS and Objectify projects are intertwined. Currently the CVS, file releases, and bug tracker are done under the New World OS project: http://sourceforge.net/projects/nwos and the Feature Requests tracker is done under the Objectify project: http://sourceforge.net/projects/objectify.
I have updated the public objects for Objectify. The only changes in this release (from the 080405 release) are the addition of some more Ubunutu, Kubuntu, Edubuntu, and Xubuntu .iso file checksums. All of the MD5, SHA1, SHA256, and SHA512 checksums for the above Linux distributions are entered up through 6.06.2.
Putting all of this information in is proving much more time consuming than I had expected. I am going to keep adding all of the Ubuntu Linux .iso checksums for versions 6.10, 7.04, 7.10 and 8.04 as time permits.... read more
The new public objects for use with the Objectify Alpha_27.1 release have the Ubuntu, Kubuntu, and Edubuntu .iso file MD5, SHA1, SHA256, and SHA512 checksums from 4.10 (Warty Warthog) to 6.06.02 (Dapper Drake).
I will be adding the remaining Ubuntu .iso files (6.10, 7.04, and 7.10) as soon as I can get them done.
You can now use the Objectify verify_file --public option to verify the download of these files. You can also output the MD5, SHA1, SHA256, SHA512 checksums using the list_files --public --md5 (or --sha1 --sha256 --sha512) options.... read more
I released Alpha_27.1 last night and intended to release new public objects immediately afterwards. However, I decided to try to squeeze a few more files in and so it will be another hour or so before the new Public Objects are ready.
The only major change in the Alpha_27.1 release is that the public file checksum support is now in verify_file and disc_list.
If you add --public on the verify_file program it will verify the files against the public file checksums.... read more
False alarm. I believe Alpha_26.6 and Alpha_27 are okay. I mistakenly mixed up the versions and had a 0027 version of the public objects that was marked 0026 and it caused some unhappiness.
I am having some problems using Alpha_26.6 and Alpha_27 with my older archive. I am investigating, but you may want to hold off upgrading to either Alpha_26.6 or Alpha_27 until I can find the source of the problems I am currently having. Sorry for the inconvenience.
New release with the addition of SHA512 checksums to files. It now stores MD5, SHA1, SHA256, and SHA512. Files imported or logged prior to Alpha_27 will still work, but will not have SHA512 checksums.
Because of the change to the FILE class, I changed the version number in the storage headers to 0027.
The public objects have the new FILE class revision and new SHA512 class.
PLEASE NOTE: the public-080314-0027 objects DO NOT have the Ubuntu .iso file information that the public-080216-0026 objects had. This is because I added the SHA512 checksums to the file objects after the public-080216-0026 objects were created. Therefore I am going to re-input the information on the Ubuntu .iso files so they will have the SHA512 checksums. Hopefully in the next week or two.
I swear I checked this, but there is apparently a make problem in version Alpha_26.6. When you do the
You get the following error from make:
cp: cannot stat `gnu/md5.o': No such file or directory
I will be making a new release later today or tomorrow but until then you can do a build by doing the following:
I originally wanted to finish a couple of features that I had started for this release. But I've decided that I need to make some more changes before those features can be completed and that will take at least a couple of weeks.
So then the question became, should I just skip March and not do a release this month? I decided that since there were a couple of bug fixes I would go ahead and do this release.... read more