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

Uses the oldest .deb in archive instead of the newest #30

Closed
jriddell opened this issue Nov 3, 2016 · 3 comments
Closed

Uses the oldest .deb in archive instead of the newest #30

jriddell opened this issue Nov 3, 2016 · 3 comments

Comments

@jriddell
Copy link

jriddell commented Nov 3, 2016

In KDE neon we are running appstream-generator over our archive which includes many old builds. Appstream-generator seems to take the oldest build in the archive and ignore newer ones. This means fixes to the appstream files don't get used.
http://build.neon.kde.org/view/mgmt/job/mgmt_appstream-generator/97/console
18:59:05 2016-11-02 18:58:51 - INFO: Processed minuet/16.04.3-0neon+16.04+build8/amd64, components: 0, hints: 1
But minuet is on 16.08.2-0neon+16.04+build17 which includes many fixes in the appstream file.

@hsitter
Copy link
Contributor

hsitter commented Nov 7, 2016

@ximion is this intentional? and if so can we get a flag to override this via the config?

@ximion
Copy link
Owner

ximion commented Nov 7, 2016

@apachelogger If there are multiple packages with different versions but the same name, the components from all of them are included in the final output at time. The client-side however will only pick one, and might pick the older one until it has expired and been removed from the archive.
This usually happens rather quickly, so this wasn't an issue for us so far and we didn't need to do version comparisons and filtering on the input data yet.

@ximion ximion closed this as completed in cae35aa Feb 27, 2017
@ximion
Copy link
Owner

ximion commented Feb 27, 2017

Please test if this works for you :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants