Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable filter multi package with version #1294

Open
longbai opened this issue May 23, 2024 · 2 comments
Open

unable filter multi package with version #1294

longbai opened this issue May 23, 2024 · 2 comments
Labels
please confirm resolved We believe the issue is resolved ! if so, please close the issue, thanks ;-)

Comments

@longbai
Copy link

longbai commented May 23, 2024

I want to only mirror the latest package
when i use
aptly mirror create -config="/aptly123/aptly.conf" -filter="containerd.io (>= 1.6.32) | docker-ce (>= 26.1.3) | docker-ce-cli (>= 26.1.3) | docker-buildx-plugin (>= 0.14.0) | docker-ce-rootless-extras (>= 26.1.3) | docker-compose-plugin (>= 2.27.0)" docker_bullseye https://download.docker.com/linux/debian bullseye stable

it doesent work, only the first package match the version, the others ignore the version

Detailed Description

Context

Possible Implementation

Your Environment

linux 1.5.0+115+g4bc2180e

@vindict-gh
Copy link
Contributor

I tried to reproduce your error, I believe your filter is the issue.
On containerd.io, docker-buildx-plugin and docker-compose-plugin the packages are named straightforwardly upstream leading to filter being valid. However for docker-ce-rootless-extras, docker-ce and docker-ce-cli the actual versions are prefixed with a 5.

Changing your filter to this should do the trick:
-filter="containerd.io (>= 1.6.32) | docker-ce (>= 5:26.1.3) | docker-ce-cli (>= 5:26.1.3) | docker-buildx-plugin (>= 0.14.0) | docker-ce-rootless-extras (>= 5:26.1.3) | docker-compose-plugin (>= 2.27.0)"

@neolynx
Copy link
Member

neolynx commented Aug 2, 2024

@vindict-gh thanks for the reply !

@longbai did this solve your issue ?

@neolynx neolynx added the please confirm resolved We believe the issue is resolved ! if so, please close the issue, thanks ;-) label Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
please confirm resolved We believe the issue is resolved ! if so, please close the issue, thanks ;-)
Projects
None yet
Development

No branches or pull requests

4 participants
@longbai @neolynx @vindict-gh and others