# Latest rebuild broken

**URL:** https://meta.discourse.org/t/latest-rebuild-broken/134962
**Category:** Self-hosting
**Created:** [3 december 2019 om 11:06 UTC](https://meta.discourse.org/t/latest-rebuild-broken/134962 "2019-12-03T11:06:55Z")
**Posts on this page:** 4
**Page:** 2

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [27 december 2019 om 07:28 UTC](https://meta.discourse.org/t/latest-rebuild-broken/134962/23 "2019-12-27T07:28:35Z")

</div>

> [@zsero](#):
>
> Sticking to stable and sticking to 2.3.x are very different things. For example stable doesn’t allow you to stay on 2.3.x until 2.4.x matures enough

No, those are the same. Stable is a 2.3.x release until 2.4.x is out of beta.

> [@zsero](#):
>
> Just in this thread there are multiple occasions when stable left rebuild in a broken state, it’s definitely not a first.

This was (as far as I can remember) the first time when stable was broken (for a longer amount of time) _and tests-passed was not_ .

> [@zsero](#):
>
> but is “rebuilt”, always using live versions of external packages.

Most external packages are pinned to a specific version or release using the `Gemfile.lock` mechanism though. Rubygems is really more like an exception here.

---

<div class="post-metadata">

### Author: ![zsero](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zsero/32/64016_2.png) [@zsero](https://meta.discourse.org/u/zsero)
#### Post date: [27 december 2019 om 14:40 UTC](https://meta.discourse.org/t/latest-rebuild-broken/134962/24 "2019-12-27T14:40:20Z")

</div>

> [@RGJ](#):
>
> No, those are the same. Stable is a 2.3.x release until 2.4.x is out of beta.

What I’m saying is that with any production software, I don’t want to run x.0 version in production. No one would use PostgreSQL 13.0 or Node 14.0.0 or macOS 10.16.0 right? We just always wait at least till x.x.2, x.x.3 version gets released, right?

This is not possible with Discourse, except possibly with a git commit id, but that is probably end up being broken the longer we are away from the commits time.

---

<div class="post-metadata">

### Author: ![Johani](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/johani/32/176920_2.png) [@Johani](https://meta.discourse.org/u/Johani)
#### Post date: [27 december 2019 om 15:21 UTC](https://meta.discourse.org/t/latest-rebuild-broken/134962/25 "2019-12-27T15:21:52Z")

</div>

I’m closing this topic now since the issue in the OP has been resolved.

If you have any other issues, then please create separate topics for them.

---

<div class="post-metadata">

### Author: ![Johani](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/johani/32/176920_2.png) [@Johani](https://meta.discourse.org/u/Johani)
#### Post date: [27 december 2019 om 15:21 UTC](https://meta.discourse.org/t/latest-rebuild-broken/134962/26 "2019-12-27T15:21:56Z")

</div>



[Vorige pagina](https://meta.discourse.org/t/latest-rebuild-broken/134962.md?page=1)
