# \`repos.yaml\` has been moved to \`lsst/repos\`

**URL:** <https://www.rubin.community/t/repos-yaml-has-been-moved-to-lsst-repos/2159>\
**Category:** DM Notifications\
**Tags:** lsstsw, repos, reposyaml\
**Created:** [August 9, 2017, 7:48pm UTC](https://www.rubin.community/t/repos-yaml-has-been-moved-to-lsst-repos/2159 "2017-08-09T19:48:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![josh](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/josh/32/72_2.png) [@josh](https://www.rubin.community/u/josh)\
**Post date:** [August 9, 2017, 7:48pm UTC](https://www.rubin.community/t/repos-yaml-has-been-moved-to-lsst-repos/2159/1 "2017-08-09T19:48:57Z")

</div>

Per [RFC-318](https://jira.lsstcorp.org/browse/RFC-318), the `repos.yaml` configuration file, which had been living in the `lsst/lsstsw` repo as `etc/repos.yaml`, has been migrated to a new repo named `lsst/repos` at the same path of `etc/repos.yaml`. The `lsst/repos` repo has a mangled version of `lsst/lsstsw`'s history in order to preserve the log of changes that have been made to `repos.yaml` by developers.

The “self merge” upon passing CI checks now applies to `lsst/repos` and is enforced by GH branch protection.

See:

- [https://github.com/lsst/repos](https://github.com/lsst/repos)
- [https://raw.githubusercontent.com/lsst/repos/master/etc/repos.yaml](https://raw.githubusercontent.com/lsst/repos/master/etc/repos.yaml)

---

<div class="post-metadata">

**Author:** ![parejkoj](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/parejkoj/32/138_2.png) [@parejkoj](https://www.rubin.community/u/parejkoj)\
**Post date:** [August 9, 2017, 7:54pm UTC](https://www.rubin.community/t/repos-yaml-has-been-moved-to-lsst-repos/2159/2 "2017-08-09T19:54:51Z")

</div>

> [@josh](#):
>
> etc/repos.yaml. The lsst/repos repo has a mangled version of lsst/lsstsw’s history in order to preserve the log of changes that have been made to repos.yaml by developers.

What does this mean for those of us living with existing lsstsw installs? Do we need to do a completely new install, or can we just clone repos over the top of the existing file?

---

<div class="post-metadata">

**Author:** ![josh](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/josh/32/72_2.png) [@josh](https://www.rubin.community/u/josh)\
**Post date:** [August 9, 2017, 8:05pm UTC](https://www.rubin.community/t/repos-yaml-has-been-moved-to-lsst-repos/2159/3 "2017-08-09T20:05:46Z")

</div>

@parejkoj I was just writing a note about that

Users with an existing `lsstsw` install should pull from the current `master` branch. Re-running `deploy` will now fetch an updated copy of `repos.yaml` in addition to the previous method of running `rebuild -u <...>`. If `rebuild -u` is run without first updating the `lsstsw` clone, the fetch of `repos.yaml` will fail.