Update Dec 03rd 2022?

joluveba

What the title says, I would like to ask if there will be updates today. We can't live without our updates 🙂

Thank you in advance

WetGeek

joluveba We can't live without our updates

So true. I understand the first part of us to go is our patience.

ReillyBrogan

Maybe the real update was the updates we made along the way

joluveba

So, no sync this week?

ReillyBrogan

joluveba nobody said that. As far as I'm aware it's just late.

Staudey

Yeah, there's no plan to skip this week's sync. The updates must flow 🤖

WetGeek

Staudey Yeah, there's no plan to skip this week's sync

The package database was just updated ... it won't be long now.

putzerstammer

Staudey even if there are no updates on Fridays we will all survive,just don't stress take the time you need when done then done 😄

tomscharbach

WetGeek The package database was just updated ... it won't be long now.

Tick ... tick ... tick ... tick ... tick ... tick ... tick ,,, 😆

WetGeek

tomscharbach Tick ... tick ... tick ... tick ... tick ... tick ... tick ,,,

Normally the result from my checkUpgrades macro looks like this until the sync begins:

Updating repository: Solus
eopkg-index.xml.xz.sha1sum     (40.0  B)100%      0.00 --/- [--:--:--] [complete]
Solus repository information is up-to-date.
No packages to upgrade.

And that's the same result, over and over again, until this:

Updating repository: Solus
eopkg-index.xml.xz.sha1sum     (40.0  B)100%      0.00 --/- [--:--:--] [complete]
eopkg-index.xml.xz             (3.4 MB)100%      0.00 --/- [--:--:--] [complete]
Package database updated.
No packages to upgrade.

The difference is the line "Package database updated." Always before, when that appeared, within a few more minutes the sync was finished and ready to download. This time, it's apparently different.

Obviously, you need to keep on ticking, just like a Timex watch. Sooner or later we'll see results.

WetGeek

WetGeek Sooner or later we'll see results.

It turned out to be sooner, as it happens. The unusual delay probably had to do with the size of the sync this week. Downloading it now.

MintSpider

Updates as usual went extremely smoothly.
Thank you for Linux Kernel 6.0.11

brent

MintSpider same for me. 35 packages and a reboot.

Cloak

Again, systemd interventions required.

ReillyBrogan

Cloak Oh? I'm not familiar with the issue you're talking about.

Cloak

ReillyBrogan I run a media server on the Solus machine and most updates I need to re activate targets and services.

ReillyBrogan

Cloak Do you have a link somewhere to troubleshooting steps and diagnostics you've done?

Cloak

I use this sometimes https://systemd.network/index.html to make sure I have the correct syntax in fstab etc.

ReillyBrogan

Cloak No, what I mean is that you shouldn't have to reactivate targets and services on updates and I'm curious what steps you've taken to troubleshoot the issue or if you've reported it anywhere (where I can take a look at what you've done).

Cloak

ReillyBrogan Ok, I reboot after this and previous syncs and see none of my smb fstab mounts have happened so mount manually and all is good. sudo systemctl enable remote-fs.target then reboot and all is good again with the mounts. look at the media server and see it's not running so 'enable' that as well and reboot again... All works as expected. So I've seen this on other distros before, seemed to occur a while ago after a systemd update but to be clear I find the docs on systemd to be shambolic and so expect weird things from the project.. No biggie actually...

putzerstammer

Thanks to the team Updates as always with me without errors