I understand. What I'm saying is that I think that an old version of a
non-essential package was made part of the compose so their would be
something to update in the case of someone running the test on the day
the compose was nominated for test.
That's impossible by definition in Rawhide, because there's only a single package version available in a repository and there is only a single repository for Rawhide. For stable releases or Branched, you can often install an older version from the 'fedora' repo. But in a compose, all packages are always the latest ones.
In any case it was handy because you didn't have to run the test day
after day until their was something to update. I'm curious how Coconut
runs this test when there isn't something to update.
You can have a look:
_______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
