e2ebcbb02a
Release file: support Version field
...
https://wiki.debian.org/DebianRepository/Format#Version
The Version field, if specified, shall be the version of the release.
On the other hand, if not set or set to an empty value, the Version
field will not be included in the Release file.
Signed-off-by: Zhang Xiao <xiao.zhang@windriver.com >
2026-03-03 07:38:44 +00:00
49f342878a
Add SOURCE_DATE_EPOCH support for reproducible builds
...
Implement support for the SOURCE_DATE_EPOCH environment variable as
specified by reproducible-builds.org. When set, this variable overrides
the current timestamp in the Release file's Date and Valid-Until fields,
enabling reproducible filesystem publishes.
- Read SOURCE_DATE_EPOCH environment variable in Publish()
- Use the epoch timestamp for both Date and Valid-Until fields
- Gracefully fallback to current time if unset or invalid
- Add comprehensive tests for valid and invalid SOURCE_DATE_EPOCH values
2026-02-20 07:24:52 +01:00
a4cc9211d6
InRelease file: support Signed-By field
...
https://wiki.debian.org/DebianRepository/Format#Signed-By says:
> **Signed-By**
> An optional field containing a comma separated list of
> OpenPGP key fingerprints to be used for validating
> the next Release file. The fingerprints must consist
> only of hex digits and may not contain spaces.
> The fingerprint specifies either the key the Release file
> must be signed with or the key the signature key must be
> a subkey of. The later match can be disabled by appending
> an exclamation mark to the fingerprint.
>
> If the field is present, a client should only accept future updates
> to the repository that are signed with keys listed in the field.
> The field should be ignored if the Valid-Until field is not present
> or if it is expired.
For both the CLI tools and JSON, the field is taken as a string verbatim.
When specified, we must also provide `Valid-Until` field,
and i'm not sure there is an 'infinity' value for it,
so 100 years will have to do?
Fixes https://github.com/aptly-dev/aptly/issues/1497
2025-12-30 06:06:48 +03:00
d2b9adf6f2
Add a test to confirm that skel files added with the same path as a repository file do not override the repository file.
...
Co-authored-by: iofq <cjriddz@protonmail.com >
2024-11-17 14:17:14 +01:00
1357d246d8
rename addon files to skel files
2024-11-17 14:09:37 +01:00
03f189b62c
add first test of addon files
2024-11-17 14:09:37 +01:00
cc4798472f
fix test depending on gpg1 keys
2024-10-02 21:29:28 +02:00
f61514edaf
Allow disabling bzip2 compression for index files
...
Using bzip2 generates smaller index files (roughly 20% smaller Packages
files) but it comes with a big performance penalty. When publishing a
debian mirror snapshot (amd64, arm64, armhf, source) without contents
skipping bzip speeds things up around 1.8 times.
```
$ hyperfine -w 1 -L skip-bz2 true,false -m 3 -p "aptly -config aptly.conf publish drop bullseye || true" "aptly -config aptly.conf publish snapshot --skip-bz2={skip-bz2} --skip-contents --skip-signing bullseye"
Benchmark 1: aptly -config aptly.conf publish snapshot --skip-bz2=true --skip-contents --skip-signing bullseye
Time (mean ± σ): 35.567 s ± 0.307 s [User: 39.366 s, System: 10.075 s]
Range (min … max): 35.311 s … 35.907 s 3 runs
Benchmark 2: aptly -config aptly.conf publish snapshot --skip-bz2=false --skip-contents --skip-signing bullseye
Time (mean ± σ): 64.740 s ± 0.135 s [User: 68.565 s, System: 10.129 s]
Range (min … max): 64.596 s … 64.862 s 3 runs
Summary
'aptly -config aptly.conf publish snapshot --skip-bz2=true --skip-contents --skip-signing bullseye' ran
1.82 ± 0.02 times faster than 'aptly -config aptly.conf publish snapshot --skip-bz2=false --skip-contents --skip-signing bullseye'
```
Allow skipping bz2 creation for setups where faster publishing is more
important then Package file size.
Signed-off-by: Sjoerd Simons <sjoerd@collabora.com >
2022-06-22 11:25:45 +02:00
035d5314b0
Convert tests to Python 3
...
Fix #938
2022-01-27 15:06:33 +01:00
8ecd01be1f
Temporarily skip test failing on CI
2022-01-27 09:30:14 +01:00
4933e3caf4
Try to fix test failing on CI
...
PublishRepo26Test fails to run because something in the CI environment forces
gpg to ask for the user's password. Try to require gpg1 for the test, which
seems to run fine in other environments.
2022-01-27 09:30:14 +01:00
3201244d9b
Fix tests and fixtures relying on expired pgp keys
...
PGP tests relied on expired gpg keys: upgrade with newer Debian keys from
https://ftp-master.debian.org/keys.html .
Download new fixtures files from http://ftp.debian.org/debian/dists/buster/
2021-02-08 10:52:27 +01:00
bb1def2910
Try Travis on xenial workers
2019-07-11 00:16:20 +03:00
61e00b5fbd
Test updates for Travis CI
...
Travis is running Trusty with GPG 2.0.x, which is
much different from 2.1.x.
Add tests for default key signing.
Add test for gpg1/2 in functional.
2018-10-10 01:34:58 +03:00
747b9752ce
Keep checksum of not compressed index file even if it's not uploaded
...
Fixes : #756
2018-07-14 00:17:36 +03:00
5b85522400
Implement 'legacy' Contents indexes to match Ubuntu <=16.04
...
Another index is created which unifies data for all the components.
This certainly requires more resources as we have to build yet another
index.
2018-04-11 00:57:15 +03:00
cbb576cbcc
Fix up system tests
2017-07-28 22:37:20 +03:00
ab20c2d329
Add publishing & repo include tests
2017-07-26 00:31:27 +03:00
c798db8056
Add system's requirements.txt, enforce flake8 linter
...
Fix style issues in functional tests.
2017-04-28 00:05:11 +03:00
7a5be6736d
When contents generation fails, don't bail out
...
This replaces `panic` which aborts aptly execution with warning
message on console. So aptly continues publishing actions, but
`Contents` indexes might be incomplete.
Error will be printed every time contents generation is triggered.
2017-03-31 00:57:18 +03:00
77be7b9e3b
Support for SHA-512 hashes on publishing/downloads.
2016-02-18 12:01:51 +03:00
933b019f71
Fix -skip-contents + system tests. #142
2015-04-05 21:55:41 +03:00
4e3284cd98
Check contents of contents index being generated. #142
2015-04-02 01:19:51 +03:00
61d31ce7c0
Check that contents are generated on repo publish. #142
2015-04-02 00:49:08 +03:00
99f6ffe1ca
Fix system test for content generation. #142
2015-04-02 00:29:49 +03:00
d9b23167bc
Test on publishing repo with .udebs. #108
2014-09-30 21:51:38 +04:00
de32595d29
Fix test. #94
2014-09-01 16:03:35 +04:00
97158ef37b
Support for --passphrase & --passphrase-file arguments on publishing. #94
2014-09-01 15:13:07 +04:00
bb6593d21e
Add -force-overwrite flag to publish update, switch, snapshot and repo commands. #90
...
Includes new and updated system tests.
2014-08-05 17:01:18 +04:00
48d01f5700
Fix reference to home directory. #24
2014-06-27 23:30:04 +04:00
aeecc1ec91
System test on conflicting files when publishing. #65
2014-06-27 22:29:01 +04:00
e554d8befa
Update tests with introduction of Release files under each arch/component. #61
2014-06-07 17:01:37 +04:00
1957c811e8
Tests for multi-component and aptly publish list/snapshot/repo, aptly serve. #36
2014-06-06 02:09:13 +04:00
e1dbab6988
Allow publishing of empty snapshots and local repos. #55
2014-05-31 21:13:30 +04:00
b85f46547b
Allow to customize Origin/Label during publishing. #29
2014-04-15 11:47:21 +04:00
53e73c52a4
Tests for guessing publishing defaults from local repo params. #12
2014-03-26 21:40:17 +04:00
3b16ca156a
Pool as a fixture is not required. #10
2014-03-26 19:48:34 +04:00
22014206d7
System tests for aptly publish repo. #10
2014-03-26 19:44:38 +04:00
Zhang Xiao
Tim Foerster
Roman Lebedev
André Roth
Mauro Regli
Sjoerd Simons
Lorenzo Bolla
Andrey Smirnov