@denisbr
If I want to remove packageX-3.0.0.deb from a published repository, what are the steps required to do so?
you would need to drop package from whatever is being published (snapshot/repo), if that's it snapshot you need to modify snapshot source and create new snapshot, after that depending on snapshot/repo you can do aptly publish switch or aptly publish update
@denisbr PRs are really welcome on that, probably better if that is optional (like
-v flag)
@smira yeah, an optional verbose output would be nice
I'll have a look and see if my skills are up to it
i have a question. i’ve been working on setting up aptly with multi-component publishing to create distro/env repos (trusty-test, trusty-stage, etc…) and publish those to s3. i’ve got this working great publishing to different prefixes, but i’m curious if it’s possible to use the distro as the distro/env switch instead of a prefix and publish everything to the same endpoint/prefix?
yes, you can use different
distributions under common prefix, the only limitation is that there should be no conflicting packages between distributions, as they all would share common package pool
so pros: common package pool, so if two or more distributions share same package, it will be stored only once in the package pool (less S3 storage, less upload bandwidth for you)
cons: if there's a package with same name, arch and version in two distributions but package files are different, on publishing this would lead to a race between two distributions for the same package file path. aptly would complain and abort publish if that condition is detected
What is the way to sign package with gpg?
With debian? Gnupg gnupg2? ( i use latest version, 1.3.0)
I have gnupg1 key, but doesn't work
Stable releases are signed by both the ftp-master automatic archive signing key in use at the time of the release, and a per-release stable key.
I don't think signing with two keys gives any benefit to key rotation procedure
We use aptly in office
where there is no ipv6
I tried -listen="0.0.0.0:80" but still the connection is refused
I tried -listen="192.168.178.17:80" (so with the internal ip of the lxc) but with the same result
I could not find any switch or config option so I thought I ask here to ask what's wrong
anybody any ideas?
so both systemd services
thanks for that fine piece of software
see you
any best practise of aptly for multi-prod lines?
I know this issue must have be mentioned several times before, but ...
Generating metadata files and linking package files will take about 4 hours
Is it possible to do these actions with multi-threading?