aptly 0.8 has been released today. For installation instructions, please proceed to Download page.
Most important new features are:
aptly has powerful query language
which allows to select subset of packages. Query language is used
in many commands: pulling packages between snapshots, copying, moving packages
between local repositories, filtering mirror contents, etc.
aptly 0.8 allows to use queries to search mirrors, snapshots and local repos
for packages matching condition. E.g. all packages that have been built
from source package apt:
aptly 0.7 has been released today. aptly is a Debian repository management tool, it allows to mirror remote repositories, create local package repositories, manage repositories snapshots and publish them back as Debian repository. aptly main idea is “owning your own repository”: you can mix and match official repos, 3rd-party repositories, your own packages, creating your own stable/testing/whatever repositories, allowing reproducible package installations along with controlled upgrades. It is available for download as binary executables or from Debian repository:
aptly 0.6 has been released on June, 7th. It is available for download as binary executables or from Debian repository:
deb http://repo.aptly.info/ squeeze main
When installing from repository, don’t forget to import key used to sign the release:
$ gpg --keyserver keys.gnupg.net --recv-keys 2A194991
$ gpg -a --export 2A194991 | sudo apt-key add -
Most important new features are:
aptly is based on concept of list of packages. Snapshots, mirrors and
local repositories are list of packages (more precisely, list of
references to packages). When merging, pulling, copying or moving
packages might move from one list into another. Component is a way to
break down packages into groups, usually these groups make sense only in
published repository. At the same time mapping from package to component
is not universal, there’s Debian way to group packages into main,
contrib and non-free components, Ubuntu uses different schema of
components, some 3rd party repositories use components in place of
different distributions (like squeeze, wheezy etc.) or to separate
stable and testing versions of software.
aptly 0.5 has been released today. It is available for download as binary executables or from Debian repository:
deb http://repo.aptly.info/ squeeze main
When installing from repository, don’t forget to import key used to sign the release:
$ gpg --keyserver keys.gnupg.net --recv-keys 2A194991
$ gpg -a --export 2A194991 | sudo apt-key add -
Most important new features are:
Local repositories could be used in two ways:
For the second case, it is best to create snapshots of local repositories and publish them. However, when testing out new versions, there isn’t much sense in creating snapshot each time repository is updated. So aptly since version 0.5 supports direct publishing of repositories. Moreover, when local repository is updated, published repository could be updated as well in one step.
aptly version 0.4 has been released today. Major feature in this version is local package repository management which allows to manage collection of your own packages, publish, take snapshots, mix with upstream repositories mirrors. Please download it or install from source, raise issues, disscuss in aptly-discuss group, follow me (@smira) to get information about updates.
Other features in 0.4 worth mentioning are: support for source packages for mirrors and local repositories, ability to delete unused package files and DB entries, and memory usage optimizations.
Next aptly version (0.4) would contain some changes to lower memory requirements while doing general operations: memory usage will be decreased by factor of 3. aptly is written in Go language, so this is a short story of optimizing Go program memory usage.
When I have been developing aptly, I suspected that memory usage would be not optimal, as aptly is processing huge amounts of package metadata (for example, when mirroring upstream Debian repositories consisting of 30000 packages). Memory usage went unnoticed until I was testing aptly in virtual machine with just 512 MB of memory, aptly was performing poorly because Linux was busy in swapping. This was something completely unexpected: so much memory? how could that be?
Today I’ve released aptly version 0.3. It’s the first version I would recommend for production usage. Please download it or install from source, raise issues, disscuss in aptly-discuss group, follow me (@smira) to get information about updates.
New features:
-config.Nice picture (actually it’s output of aptly graph command):
Two great things have happened recently:
Slides from my talk about aptly can be downloaded in PDF (English version).