-
Notifications
You must be signed in to change notification settings - Fork 11
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
multiple versions of packages #11
Comments
I'm no expert, but I think this $ curl https://openrepo.kumomta.com/kumomta-ubuntu-22-stable/dists/stable/main/binary-any/Packages
Package: kumomta
Architecture: amd64
Version: 2023.03.30.180934.427c74f0
Priority: optional
Section: utils
Maintainer: Wez Furlong <[email protected]>
Depends: libc6 (>= 2.34), libgcc-s1 (>= 4.2), libstdc++6 (>= 12)
Conflicts: kumomta-dev
Filename: pool/main/kumomta.Ubuntu22.04.deb
Size: 11100150
MD5sum: 73b496f2722dd2d8205da400005bfb02
SHA1: 2ed0eeb8f80136d12e877afc0270e71b9025f51e
SHA256: de6d2618eb127c72301063507073c96e16a1267b7c4b7c4ec5327d663c5abada
SHA512: 3b00e8bb24d60692e1ec038fee6baf7ef7141c2d2cff53e29c70cab0a8ab7cd2289d1950f2b1d499b30259633357609616772ca0dd45a0146e20594cf4ae298f
Homepage: https://github.com/KumoCorp/kumomta
Description: A high performance, modern MTA |
I suspect that using the same name on upload to openrepo somehow collides with other versions that use the same uploaded filename. refs: openkilt/openrepo#11
In the build status are there any warnings? I'll bet it's having trouble parsing the version number. Can you post the 4 deb files you're using to make it easy to reproduce? |
I suspect that using the same name on upload to openrepo somehow collides with other versions that use the same uploaded filename. refs: openkilt/openrepo#11
I have a theory that using the same uploaded filename |
Confirmed that using the same filename each time leads to this. I deleted and re-uploaded with varying filenames and things seem happier |
I have an issue where with an apt repo with contents like this:
a simple
apt install kumomta
will install version2023.03.30.180934.427c74f0
instead of the latest2023.06.22.135051.51b72a83
.is there some additional configuration needed for this to work?
The text was updated successfully, but these errors were encountered: