Due to lack of contribution lately we have decided to temporarily stop adding new packages to the repository in an effort to refocus our efforts and try to get a more sound approach together regarding the repository.
We will continue to keep the current repositories live so that you may draw from them but will not be making future repos until further notice.
We recently of David Dragondisk to version 0.88. This includes a minor fix from version 0.87
We also have uploaded version 0.87 though both of these versions were uploaded and went live at the same time. Version 0.88 should be installed. We merely uploaded 0.87 in case there was a problem with the latest version.
Alternatively, we have discovered Fedora 15 a possible issue when trying to install Dragondisk from our repository. On our test system trying to install Dragondisk from the repository forces a Yum to complain that the public key for our repository is not installed, were not sure what causes this error or even if it exists on another system other than our test system. If you received this message when trying to install or update Dragondisk simply re-run Yum Using the switch “—nogpg”. As soon as we determine what causes this we will correct it. Again, were not even sure if this error is present on every system or if there’s just something funky on our test system.
I have run into some computer troubles and I am restoring from a backup, while this will not affect the current Repository, updating it will be delayed.
Dragondisk has had an update which will be the first new update to the repository once my system is fully restored. I apologize for the delay and thank you for your patience
We are in the process of updating the RPM we have to the latest Dragondisk version please stay tuned as we update it. You can expect to see the new version live within the week we apologize for the delay.
We have updated Dragondisk to the newest version below are the changes
Fixed : Folder browser dialog does not work with DNS-incompatible
named bucket (regression introduced in 8.0)
Additionally we had to add some files back to the package that were stripped out and thus the delay for the update.
In case your computer refuses to update you can download the file here dragondisk 0.8.5 This could happen because the versioning of the package changed (based on the way the author numbered it) so it now has 3 decimal places instead of 2 I.E 0.8.5 instead of 0.85 . To counter this we plan to re-package this rpm using the old numbering scheme (0.85) in the near future.
We are aware that the current version of Dragondisk is .85 and that the version in the repositories is .81.
Were in the process of getting ready to update this package, please stay tuned. You should see the new package live in the repositories within a week
We had to change the signing key so all packages have been re-signed. Please run Yum Update to get the latest repo rpm with the new key.
If your not able to update due to a GPG conflict you can download directly from here rpmme-2-2.noarch.rpm
Dragon Disk was updated to version 0. 81
The new RPM should be live now.
Changes:
* New : Encryption support (OpenSSL : AES256, AES128, Blowfish, TripleDES)
* New : Compression support (gzip)
* Added : “Copy URL”/”Copy Key” to the context menu
The synchronization algorithm has been improved, and now it works
faster and more reliable.
Note: Yum will say Dragondisk 0.81 is not signed, this is true we are having an issue with our private key for the repository and will most likely need to generate new gpg keys and resign the entire repository! Until we get something set you can ignore the error as the package is safe, if unsure just wait to upgrade we will have it up soon.
We are happy to announce we have gone live with Fedora 15 support, please note that their are not alot of packages to place in there currently so we are open to more submissions!
We are happy to announce that the support for Fedora 15 is going to be going live, it may take us a few days however to transition so please be patient!
An update will be posted as soon as we have finished
Bad Behavior has blocked 46 access attempts in the last 7 days.
