aptly v1.0.0 Release Notes
Release Date: 2017-03-27 // about 7 years ago-
🔄 Changes
Contents
index generation was re-implemented to use temporary DB instead of keeping index in memory which should lower memory requirements a lot during publishing.📦 Debian package reader was enhanced to guess correct archive type even if filename is incorrect (e.g.
data.tar.gz
while it's regulartar
archive).👍
.xz
compression format is supported for mirrors (index files).🚀
aptly mirror create
supports new flag-force-architectures
which disables validation of supplied architectures inRelease
file (for mirrors with brokenRelease
files).⚡️
aptly mirror update
supports download retries via new flag-max-tries
.📦
aptly search *
family of commands allows query expression to be missing which means "display all the packages".🆕 New command
aptly publish show
to display detailed information about published repository.🆕 New command
aptly repo create ... from snapshot ...
to initialize local repository with snapshot contents.👍
aptly api serve
supports systemd activation, listening on UNIX sockets and it bails out quickly if root dir is not writable.📦 aptly now supports
-dbgsym
packages while processingaptly repo include
.aptly snapshot show
output was enhanced to include information about snapshot sources (and its current names).👍
aptly graph
supports rendering to output files instead of launching viewer, viewer is now custom per platform. Also additionalvertical
layout is supported which might be useful to get better-looking diagrams.Repo edit API doesn't touch repo fields which are not specified in the request.
🏗
aptly version
command now reports correct version for nightly builds.👍 Extended support for OpenStack environment variables in Swift publisher.
🔖 Versioning
🛠 From now on, aptly release should happen every 3 months. For every release minor version would be bumped (e.g. next release would be
1.1.0
). Bugfix-release will bump patch version (e.g.1.0.1
).🚀 Nightly builds versioning has changed, now version format is following
git describe --tags
format:x.y.z+<N>+<hash>
, wherex.y.z
is previous aptly release (important, before it was next version of aptly) followed by monotonically increasingN
and git commithash
.Development
aptly stopped using gom for vendored dependency management. From now on aptly has all the deps committed to the source tree under
vendor/
directory (standard Go vendoring). Vendored dependency are managed using dep tool.🚀 Go source code is checked using gometalinter, with only some most important checks enabled, more checks to be enabled in the next releases. Use
make check
to check your source code for problems.📦 aptly packages are built with Go 1.8.
Download
📦 Debian packages and binary distributions for various platforms are available at https://www.aptly.info/download/
Previous versions
🔄 Changelog for previous version could be found at aptly website.