Update to Solus 4.8

AntoineLaLune

I realise that I haven't had any updates for a long time. Before I realised that Solus 4.8 had been released.
I thought I would have to follow instructions to upgrade to version 4.8, since sudo eopkg up told me that I had no packages to update. (Regardless of which connection I use.)
But I was told that I had to do it via eopkg, and since that doesn't work, I'm stuck on version 4.7.
Is this something that can be fixed? Or would it be better to do a new installation?

AntoineLaLune

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Solus
Description:	Solus 4.7 Endurance
Release:	4.7
Codename:	endurance

brent

eopkg lr(repo should be polaris not shannon---migrating to new repo the 1st step methinks to 4.8)

sudo eopkg check

also install gnome-software (or Discover) and see if it sees updates. If that's a big NO then we are getting closer I suppose

pomon

Check this out: A New Epoch Begins.

Sebastian

I believe manually switching repo should only happen if usr merge was successful, otherwise you run into trouble I think.

AntoineLaLune

Thank you all for your replies, they're already helping me a lot. It seems that there is a process that takes place before changing the repo, which involves moving the executables (If I'm not mistaken.), and I'm not sure that this process was done on my computer (The executables seem to be duplicated? They are in both ‘/bin’ and ‘/usr/bin’, and the same goes for the other folders.).
I may be mistaken, so I will take the time to reread ‘A New Epoch Begins’ when I have more time. If this is what I understand, I just need to create this script at system launch, which performs the process, before I change the repo.

I am indeed still at the Shannon depot:

$ eopkg lr
Solus [actif]
   https://cdn.getsol.us/repo/shannon/eopkg-index.xml.xz

brent

AntoineLaLune

brent

Great, that's what I was looking for! "Opting in" is super obvious, and yet I ignored this section, my English is really bad for missing that! Sorry!

Harvey You no longer need to opt in, everyone was forced to migrate if that migration has not happened for you then something has gone wrong.

But yes, something must be broken somewhere, I don't know yet if I'm going to try the command or not. I don't even know if that will solve the problem or not.
Unfortunately, this is happening in the middle of a lot of homework, so I'll probably have to leave it for now and come back to it later. I'm sorry about that.

Harvey

You no longer need to opt in, everyone was forced to migrate if that migration has not happened for you then something has gone wrong.

brent

Harvey
I did this all earlier than the epoch rollout, I forgot it was automatic after that.

brent

AntoineLaLune
eopkg lr will tell you what repo you are using. try it.

$ eopkg lr
Solus [active]
https://cdn.getsol.us/repo/polaris/eopkg-index.xml.xz

that's mine

also sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall will fix anything broken automtically

if you wind up on Polaris then read this thread: https://discuss.getsol.us/d/10597-latest-update-has-broken-eopkg/6
--lots more stuff to try.
Harvey is right: something is wrong somewhere, as you surmised yourself.

TraceyC

brent eopkg lr will tell you what repo you are using. try it.

They already had, as you can see above. Please don't ask people to do things they have already done, it frustrates people.

brent also sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall will fix anything broken automtically

This command is old, and outdated. To check for broken packages see
https://help.getsol.us/docs/user/troubleshooting/

sudo eopkg check

This is good to try.

brent

TraceyC This command is old, and outdated. To check for broken packages see
https://help.getsol.us/docs/user/troubleshooting/

had no idea we retired that old warhorse of a command for a sequence of smaller commands. nice.