Release Notes
We've moved! Please visit our new wiki and update your bookmarks.
Several new features and bug fixes.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
Several new features and bug fixes.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
Several new features and bug fixes.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
Note that Acquire-by-hash metadata will be generated on the next reindex of the repository. Users who want to take advantage of this feature will need to either upload a package to their repository or trigger a reindex using packagecloud-ctl.
Minor feature tweak.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
Bug fix.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
OpenSSL security release.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
Bug fix and a new feature.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
Several bug fixes and new features.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
Numerous performance enhancements, bug fixes, and new features.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
Update for OpenSSL version 1.0.1t.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
Added the ability to specify repository collaborations in users.yml.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
Fix for a very rare display bug and the reindex deb task.
No special tasks required for upgrade. You should follow the normal upgrade procedures.
If you are installing packagecloud:enterprise for the first time, you do not need to perform any of the procedures listed below.
If you are upgrading to packagecloud:enterprise 1.0.33, you should follow the normal upgrade procedures.
Once that has been completed, there are two tasks you should run:
-
sudo packagecloud-ctl update-rubygems-checksums-- This rake task will download each RubyGem file from your S3 bucket and re-process it to store additional checksums in the database. We've expanded the number of checksums we track and are now tracking SHA256 and SHA512. The length of time this process will take depends on your S3 connection speed and the number of RubyGems you have. Our production instance completed this operation for approximately 5000 RubyGems in about 10 minutes. -
sudo packagecloud-ctl clear-xz-files-- This rake task will remove all APT XZ compressed metadata files for each repository. We've decided to make this change as a result of a serious bug in APT which causes APT to fail to correctly decompresse XZ-compressed metadata resulting in confusing errors for users. You can read more about this bug on our blog. This process will iterate through each repository on the system with XZ-compressed metadata first reindexing it, then deleting the left over XZ files from S3 and their records in the database. The time this operation takes depends on the number of packages in the repository and the number of repositories on the system.