Software update available sign remains active

Using Zynthian
1

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

2

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 :slight_smile:

3

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

4

Thanks.

5

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

zyncoder: oram-2409 (71de6d2)
zynthian-ui: oram-2409 (bbc7246)
zynthian-sys: oram-2409 (f742b18)
zynthian-data: oram (ddfa009)
zynthian-webconf: oram-2409 (7c396b9)

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?

6

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

Regards

1 Like
7

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

1 Like
8

Now I changed to Vangelis, rebooted and changed back to oram2409 configuration (NO custom configuration).
The zynthian repositories are now
zyncoder: oram-2409 (71de6d2)
zynthian-ui: oram-2409.001 (df2facc)
zynthian-sys: oram-2409.002 (4c4ce51)
zynthian-data: oram-2409 (ddfa009)
zynthian-webconf: oram-2409.001 (88fc358)

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

9

The update procedure worked for me too. Thanks.

10

Agreed! We plan to improve this.

11

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.

12

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

13

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


 ##########################       ----------------------------------------
#                          #      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:

(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?

14

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

Regards,

15

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

 ##########################       ----------------------------------------
#                          #      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?

16
  • 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.

17

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.

18

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.