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

Sort changelog entries before applying the limit #2363

Closed
dralley opened this issue Jan 19, 2022 · 0 comments · Fixed by #2359
Closed

Sort changelog entries before applying the limit #2363

dralley opened this issue Jan 19, 2022 · 0 comments · Fixed by #2359

Comments

@dralley
Copy link
Contributor

dralley commented Jan 19, 2022

I was hoping this wasn't necessary since both legacy createrepo and createrepo_c use a specific order, but I discovered that Oracle Linux used to use reverse-chronological order (months ago, it seems like they switched tools at some point). I have no idea what tool they used but lets play it safe for now.

dralley added a commit to dralley/pulp_rpm that referenced this issue Jan 19, 2022
* Sort the changelog entries by date first. I was hoping this wasn't
  necessary since both legacy createrepo and createrepo_c use a specific
  order, but I discovered that Oracle Linux used to use
  reverse-chronological order. I have no idea what tool they used but
  lets play it safe for now.
* Apply it at publish time as well, in the event that the user has
  impacted repos but hasn't used the utility script yet.

closes pulp#2363
pulp#2363
dralley added a commit to dralley/pulp_rpm that referenced this issue Jan 19, 2022
* Sort the changelog entries by date first. I was hoping this wasn't
  necessary since both legacy createrepo and createrepo_c use a specific
  order, but I discovered that Oracle Linux used to use
  reverse-chronological order. I have no idea what tool they used but
  lets play it safe for now.
* Apply it at publish time as well, in the event that the user has
  impacted repos but hasn't used the utility script yet.

closes pulp#2363
pulp#2363
dralley added a commit to dralley/pulp_rpm that referenced this issue Jan 19, 2022
* Sort the changelog entries by date first. I was hoping this wasn't
  necessary since both legacy createrepo and createrepo_c use a specific
  order, but I discovered that Oracle Linux used to use
  reverse-chronological order. I have no idea what tool they used but
  lets play it safe for now.
* Apply it at publish time as well, in the event that the user has
  impacted repos but hasn't used the utility script yet.

closes pulp#2363
pulp#2363
dralley added a commit to dralley/pulp_rpm that referenced this issue Jan 20, 2022
Sort the changelog entries by date first. I was hoping this wasn't
necessary since both legacy createrepo and createrepo_c use a specific
order, but I discovered that Oracle Linux used to use reverse
chronological order. I have no idea what tool they used but lets play
it safe for now

closes pulp#2363
pulp#2363
dralley added a commit that referenced this issue Jan 20, 2022
Sort the changelog entries by date first. I was hoping this wasn't
necessary since both legacy createrepo and createrepo_c use a specific
order, but I discovered that Oracle Linux used to use reverse
chronological order. I have no idea what tool they used but lets play
it safe for now

closes #2363
#2363
patchback bot pushed a commit that referenced this issue Jan 20, 2022
Sort the changelog entries by date first. I was hoping this wasn't
necessary since both legacy createrepo and createrepo_c use a specific
order, but I discovered that Oracle Linux used to use reverse
chronological order. I have no idea what tool they used but lets play
it safe for now

closes #2363
#2363

(cherry picked from commit cd7fc14)
patchback bot pushed a commit that referenced this issue Jan 20, 2022
Sort the changelog entries by date first. I was hoping this wasn't
necessary since both legacy createrepo and createrepo_c use a specific
order, but I discovered that Oracle Linux used to use reverse
chronological order. I have no idea what tool they used but lets play
it safe for now

closes #2363
#2363

(cherry picked from commit cd7fc14)
dralley added a commit that referenced this issue Jan 21, 2022
Sort the changelog entries by date first. I was hoping this wasn't
necessary since both legacy createrepo and createrepo_c use a specific
order, but I discovered that Oracle Linux used to use reverse
chronological order. I have no idea what tool they used but lets play
it safe for now

closes #2363
#2363

(cherry picked from commit cd7fc14)
dralley added a commit that referenced this issue Jan 21, 2022
Sort the changelog entries by date first. I was hoping this wasn't
necessary since both legacy createrepo and createrepo_c use a specific
order, but I discovered that Oracle Linux used to use reverse
chronological order. I have no idea what tool they used but lets play
it safe for now

closes #2363
#2363

(cherry picked from commit cd7fc14)
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

Successfully merging a pull request may close this issue.

1 participant