On Fri, Jun 11, 2021 at 7:26 AM redbaronbrowser via CentOS-devel <centos-devel at centos.org> wrote: > > On Friday, June 11th, 2021 at 6:12 AM, Neal Gompa <ngompa13 at gmail.com> wrote: > > > On Fri, Jun 11, 2021 at 6:56 AM redbaronbrowser via CentOS-devel > > > > centos-devel at centos.org wrote: > > > > > I am curious about composes.centos.org and it's intended use case or guidance on what it should/can be used for. If it is reasonable, I would like to try to write a dnf plugin to simplify using it for package rollbacks. Is someone else already working on this? Is there a better way to go about doing this? > > > > > > Ultimately, I would like it so when submitting a bug about a regression, it is easy for the user to specify between what compose dates the regression first appeared. > > > > This shouldn't be necessary since older packages are merged into the > > > > repositories now: > > > > https://lists.centos.org/pipermail/centos-devel/2021-May/076839.html > > > > The composes are mainly useful for getting older ISOs. > > That indicates due to space limitations there may be packages that have only one previous version. I was looking to be able to go back more than one version and it seem like composes could allow doing that? Not all issues are discovered right away and may already exist in the previous version. Composes may give you that ability, but they are not retained indefinitely. They will be removed after some time for similar space reasons. If a user would like to retain all versions of packages that are released, they essentially need to create a local repository with all the versions included. josh