# Software update available sign remains active

**URL:** <https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491>\
**Category:** Using Zynthian\
**Tags:** oram\
**Created:** [November 10, 2024, 5:37pm UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491 "2024-11-10T17:37:07Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![BertB](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/b/ebca7d/32.png) [@BertB](https://discourse.zynthian.org/u/BertB)\
**Post date:** [November 10, 2024, 5:37pm UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/1 "2024-11-10T17:37:07Z")

</div>

Hi,  
The last week, the Software update available signs remains in the status bar.  
Tried updating several times, but the issue stays.  
How can I solve this?

Thanks,  
Bert

---

<div class="post-metadata">

**Author:** ![Aethermind](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/aethermind/32/9208_2.png) [@Aethermind](https://discourse.zynthian.org/u/Aethermind)\
**Post date:** [November 10, 2024, 8:34pm UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/2 "2024-11-10T20:34:29Z")

</div>

Hi @BertB,

Your issue was detected recently, because of one of the latest Oram updates.

Please, execute this command (from a thread now closed and resolved), with this patch courtesy of @jofemodo:

cd $ZYNTHIAN\_SYS\_DIR; git pull

Afterwards, having installed the official September 2024 Oram release, select in Webconf \> Software \> Repositories the Oram stable 09 2024 OS.

Best regards 🙂

---

<div class="post-metadata">

**Author:** ![riban](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/riban/32/2331_2.png) [@riban](https://discourse.zynthian.org/u/riban)\
**Post date:** [November 10, 2024, 9:44pm UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/3 "2024-11-10T21:44:25Z")

</div>

I am hoping this will be fixed in another update. I have experienced it a few times and had to reboot to clear it.

---

<div class="post-metadata">

**Author:** ![BertB](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/b/ebca7d/32.png) [@BertB](https://discourse.zynthian.org/u/BertB)\
**Post date:** [November 11, 2024, 7:31am UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/4 "2024-11-11T07:31:56Z")

</div>

Thanks.

---

<div class="post-metadata">

**Author:** ![gitnob](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/gitnob/32/11827_2.png) [@gitnob](https://discourse.zynthian.org/u/gitnob)\
**Post date:** [November 11, 2024, 9:41pm UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/5 "2024-11-11T21:41:56Z")

</div>

I must say that I have the same issues with the stable Oram relase (also with oram(staging) ).

zyncoder: [oram-2409 (71de6d2)](https://github.com/zynthian/zyncoder/commit/71de6d2b5c58c84f0b9526c339bd4b131b3ff415)  
zynthian-ui: [oram-2409 (bbc7246)](https://github.com/zynthian/zynthian-ui/commit/bbc7246597e86f020efad4d2f354b8e24cd64b95)  
zynthian-sys: [oram-2409 (f742b18)](https://github.com/zynthian/zynthian-sys/commit/f742b187cc168d7a70148b9b28d0408d48f54636)  
zynthian-data: [oram (ddfa009)](https://github.com/zynthian/zynthian-data/commit/ddfa009f7ff55c455c7a07d0349f645ee8219354)  
zynthian-webconf: [oram-2409 (7c396b9)](https://github.com/zynthian/zynthian-webconf/commit/7c396b98291aee749a2e0cf7dc2568f627727a66)

I updated because I had the update sign, but after updating and also doing the git pull “hack” as described by @Aethermind (@jofemodo ) in zynthian sys dir, after rebooting the update sign is still on.  
This is confusing, because a “regular” oram user (which is the stable release) shouldn’t get this. Also there is another oram2409.001 release.  
IMHO this is not resolved yet. Or am I the only one?

---

<div class="post-metadata">

**Author:** ![jofemodo](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/jofemodo/32/2_2.png) [@jofemodo](https://discourse.zynthian.org/u/jofemodo)\
**Post date:** [November 11, 2024, 10:04pm UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/6 "2024-11-11T22:04:21Z")

</div>

Please, note your zynthian is not fully in stable. Check your repos and changer tú vangeiis and them changer back to stable.

Regards

---

<div class="post-metadata">

**Author:** ![gitnob](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/gitnob/32/11827_2.png) [@gitnob](https://discourse.zynthian.org/u/gitnob)\
**Post date:** [November 11, 2024, 11:02pm UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/7 "2024-11-11T23:02:57Z")

</div>

thanks @jofemodo.  
OK, I see zynthian-data is not in stable oram-2409, but I didn’t choose this custom configuration, I’ve chosen the stable repository release in the drop-down menu in webconf.  
This is confusing, sorry. I try to figure it out tomorrow.  
Regards

---

<div class="post-metadata">

**Author:** ![gitnob](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/gitnob/32/11827_2.png) [@gitnob](https://discourse.zynthian.org/u/gitnob)\
**Post date:** [November 12, 2024, 8:44am UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/8 "2024-11-12T08:44:20Z")

</div>

Now I changed to Vangelis, rebooted and changed back to oram2409 configuration (NO custom configuration).  
The zynthian repositories are now  
zyncoder: [oram-2409 (71de6d2)](https://github.com/zynthian/zyncoder/commit/71de6d2b5c58c84f0b9526c339bd4b131b3ff415)  
zynthian-ui: [oram-2409.001 (df2facc)](https://github.com/zynthian/zynthian-ui/commit/df2facc017e4a4aa5a788f9ac427346be14dd984)  
zynthian-sys: [oram-2409.002 (4c4ce51)](https://github.com/zynthian/zynthian-sys/commit/4c4ce511cb25e0528ba7585f4eb1dc0c2bc1a5dd)  
zynthian-data: [oram-2409 (ddfa009)](https://github.com/zynthian/zynthian-data/commit/ddfa009f7ff55c455c7a07d0349f645ee8219354)  
zynthian-webconf: [oram-2409.001 (88fc358)](https://github.com/zynthian/zynthian-webconf/commit/88fc358998bfac3529df271f11e33b364b6b1747)

It is working now (no update recommendation loop anymore), but the different branch names in the stable oram-2409 configuration are still confusing. Anyway …  
Regards

---

<div class="post-metadata">

**Author:** ![BertB](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/b/ebca7d/32.png) [@BertB](https://discourse.zynthian.org/u/BertB)\
**Post date:** [November 12, 2024, 9:31am UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/9 "2024-11-12T09:31:22Z")

</div>

The update procedure worked for me too. Thanks.

---

<div class="post-metadata">

**Author:** ![riban](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/riban/32/2331_2.png) [@riban](https://discourse.zynthian.org/u/riban)\
**Post date:** [November 12, 2024, 10:59am UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/10 "2024-11-12T10:59:37Z")

</div>

> [@gitnob](#):
>
> but the different branch names in the stable oram-2409 configuration are still confusing

Agreed! We plan to improve this.

---

<div class="post-metadata">

**Author:** ![BertB](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/b/ebca7d/32.png) [@BertB](https://discourse.zynthian.org/u/BertB)\
**Post date:** [January 18, 2025, 4:51pm UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/11 "2025-01-18T16:51:35Z")

</div>

I am sorry to say that the problem came back with the latest oram stable update.  
I did all the tricks mentioned above, including going to Vangelis and back, but nothing helped. The sign remains.

---

<div class="post-metadata">

**Author:** ![LagoonCity](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/lagooncity/32/12742_2.png) [@LagoonCity](https://discourse.zynthian.org/u/LagoonCity)\
**Post date:** [January 18, 2025, 7:14pm UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/12 "2025-01-18T19:14:21Z")

</div>

I came here to say the same thing. Back since the most recent update.

---

<div class="post-metadata">

**Author:** ![hannesmenzel](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/hannesmenzel/32/13014_2.png) [@hannesmenzel](https://discourse.zynthian.org/u/hannesmenzel)\
**Post date:** [January 22, 2025, 9:21am UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/13 "2025-01-22T09:21:33Z")

</div>

Sorry, I cannot resolve this. My current system is like this:

```auto

 ########################## ----------------------------------------
# # ZynthianOS ORAM-2409
# ## # Timestamp: 2024-10-02
# ## # # ## # Built from RaspberryPiOS Bookworm (aarch64)
# # # # # # # # ----------------------------------------
### # # # # # # ### Kit: Custom
# # # # # # # # # # Display: Generic HDMI/DSI Display
# ## # # # # ## # Soundcard: Generic USB device
# ## ## # Wiring Layout: DUMMIES
# # ----------------------------------------
 ##########################
                                  zynthian-ui: oram-2409.4 (5dfe2b)
                                  zynthian-webconf: oram-2409.3 (25cda9)
                                  zyncoder: oram-2409.2 (36691b)
                                  zynthian-sys: oram-2409.4 (9cf56b)
                                  zynthian-data: oram-2409.3 (305b30)
                                  ---------------------------------------

Linux zynthian 6.6.47-v8-16k+ #1794 SMP PREEMPT Thu Aug 29 16:30:28 BST 2024 aar ch64

```

The above mentioned workaround produces this:

```auto
(venv) root@zynthian:/zynthian/zynthian-sys# git pull
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.

    git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

    git branch --set-upstream-to=origin/<branch> oram-2409.4

```

Webconf says I might be in the oram-2409.4 branch.

Can somebody help a noob out please?

---

<div class="post-metadata">

**Author:** ![jofemodo](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/jofemodo/32/2_2.png) [@jofemodo](https://discourse.zynthian.org/u/jofemodo)\
**Post date:** [January 22, 2025, 9:45am UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/14 "2025-01-22T09:45:53Z")

</div>

Please, try moving to oram staging and then, if you think it’s not “reliable-enough”, go back to stable.

Regards,

---

<div class="post-metadata">

**Author:** ![hannesmenzel](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/hannesmenzel/32/13014_2.png) [@hannesmenzel](https://discourse.zynthian.org/u/hannesmenzel)\
**Post date:** [January 22, 2025, 9:54am UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/15 "2025-01-22T09:54:29Z")

</div>

Cool, no update loop anymore in staging. Versions now all “oram” like this:

```auto
 ########################## ----------------------------------------
# # ZynthianOS ORAM-2409
# ## # Timestamp: 2024-10-02
# ## # # ## # Built from RaspberryPiOS Bookworm (aarch64)
# # # # # # # # ----------------------------------------
### # # # # # # ### Kit: Custom
# # # # # # # # # # Display: Generic HDMI/DSI Display
# ## # # # # ## # Soundcard: Generic USB device
# ## ## # Wiring Layout: DUMMIES
# # ----------------------------------------
 ##########################
                                  zynthian-ui: oram (d58dfb)
                                  zynthian-webconf: oram (6552a7)
                                  zyncoder: oram (6af1b4)
                                  zynthian-sys: oram (707355)
                                  zynthian-data: oram (ef38af)
                                  ---------------------------------------

Linux zynthian 6.6.47-v8-16k+ #1794 SMP PREEMPT Thu Aug 29 16:30:28 BST 2024 aar ch64

```

May be a dumb question, but is staging still always ahead of stable since these new point releases?

---

<div class="post-metadata">

**Author:** ![riban](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/riban/32/2331_2.png) [@riban](https://discourse.zynthian.org/u/riban)\
**Post date:** [January 22, 2025, 10:02am UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/16 "2025-01-22T10:02:59Z")

</div>

- Stable should be the most stable release.
- Staging should only have changes ready to be merged into stable when sufficiently tested. You can consider it similar to beta or release candidate testing of the next stable release.
- Testing has possibly breaking changes. It is the bleeding edge development - not for the faint hearted.

Currently, stable is less stable that we would like and staging is in a bit of an interim state. We hope to move staging to a proper staging state this week to support user testing for the next stable (point) release.

---

<div class="post-metadata">

**Author:** ![BertB](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/b/ebca7d/32.png) [@BertB](https://discourse.zynthian.org/u/BertB)\
**Post date:** [January 22, 2025, 2:55pm UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/17 "2025-01-22T14:55:27Z")

</div>

As per your recommendation, I ‘went’ to staging and the update sign was gone.  
Then I went to stable again, and the update sign was back again.

I’ll be in staging. Thanks.

---

<div class="post-metadata">

**Author:** ![riban](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/riban/32/2331_2.png) [@riban](https://discourse.zynthian.org/u/riban)\
**Post date:** [January 22, 2025, 2:58pm UTC](https://discourse.zynthian.org/t/software-update-available-sign-remains-active/10491/18 "2025-01-22T14:58:21Z")

</div>

Beware that staging will be updated this week (probably Friday) with the next release staging version. There will be changes that may change workflows but there should not be substantial bugs. We welcome as many testers as we can muster but anyone using for production purpose should consider the risk and may prefer to stick with stable.