Differing version numbers of some local and remote packages: Cannot reinstall all installed packages

that must be a remnant of the installer - nothing standard is installed into /opt

install again and we’ll see, won’t we :wink:

1 Like

@BG405

Yes, of course the pacman.log file contains more lines than I have quoted. I just wanted to make sure that the oldest log information in this file not already has been deleted (instead of being rotated).

In this pacman.log file I am not sure for which term(s) I should search for. Would it be worth to inspect this file at this very moment?

Or wouldn’t it be better if I just do another installation of Manjaro? Because maybe I really did something wrong, without my intention.

1 Like

Use:

sudo pacman-mirrors --fasttrack && sudo pacman -Syu

when you perform that update; just in case.

I’d suggest posting the full logs, so we can have a look. :wink:

2 Likes

At this point - and if it isn’t too much trouble - it’s likely very much easier than to go down the rabbit hole of what you currently have.

It would be much less time consuming.

1 Like

Indeed; but also less educational for @anon20541014 …? (And others here).

@soundofthunder

Thanks for your advice regarding the use of

sudo pacman-mirrors --fasttrack && sudo pacman -Syu

having completed the installation of Manjaro + a reboot.

But I will click the update notifier in the KDE task bar because I want to find out if there is something wrong with it.

@Nachlese

So you also think it is better for me to do another Manjaro installation because analyzing the pacman log file would take much more time than a new installation, right?

Yes, I think you are right.

Guys, have you seen this:

It applies to testing branch, nevertheless, before reinstalling I would give the downgrade a try. It’s just one command and the syntax has been provided many times, already. :wink:

3 Likes

I’d suggest… let the man reinstall, and be done with it.

It is said that lightning doesn’t strike twice in the same place (which is actually a falsehood) however, for brevity, let’s just see how a new installation falls into place.

Cheers.

2 Likes

@Wollie

Thanks for your information :wink:

OK, I will try to find this command here. Didn’t I try all commands that have been mentioned here already? Let me have a look in the previous posts in this thread.

AFAIK you didn’t try the one I posted (twice), which solves both issues (the newer packages and existing files).

sudo pacman -Syuu --overwrite '*'
1 Like

And from post 1:

This command failed (at the time) due to an apparent issue with VLC.

1 Like

Subtle difference, there’s an extra u to downgrade the newer packages.

Yes, but it indicates the OP was aware of the command from the onset. Perhaps continued references to downgrading were ignored due to it failing in their hands. :man_shrugging:

@Teo also mentioned downgrading early in the thread; all we could assume is that it had already been sufficiently covered.

Much seems lost in translation.

Yes, but failed to combine the two commands into one that would work.

sudo pacman -Syu --overwrite '*'

Avoids the exists in filesystem error, but did nothing due to the system being up-to-date, and of course the newer packages weren’t downgraded.

sudo pacman -Syuu 

Failed because of the exists in filesystem errors.

That’s why I posted it twice, along with a quote from them asking how to fix it.

I suppose I should’ve explained it better, though to be fair I did say:

I’m sure it’s been mentioned several times how to downgrade, or remove and reinstall “offending” packages, or just wait until Stable catches up with whatever’s been installed!

I think we’ve all covered things adequately.

The only thing I’m missing is the OP’s final choice… is he downgrading or reinstalling? :smile_cat:

I’ve been distracted for the last few posts.

This seems to indicate he’s now following directions – from the thread @Wollie posted – to downgrade:

I just made a bet with myself.

2 Likes

Hey all + especially @dmt :wink:

I did the downgrade - with success! There was no error message in the console output of the command which @dmt provided to me.

Having done an “update-grub” in one of my other local Linux installations (Debian 12), then booting into Manjaro I applied the following two commands:

[<User>@<Hostname> ~]$ sudo checkupdates
[sudo] password for <User>: 
[<User>@<Hostname> ~]$ sudo pacman -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
 there is nothing to do
[<User>@<Hostname> ~]$ 

So now everything seems to work properly :wink: Thanks to the all of you for your input :slight_smile:

Edit: And now the strawberry program starts successfully :wink: Which seems to be a fork of the Clementine audio player, if I look at its GUI :wink:

4 Likes

My transition from Debian (with a detour to Gentoo and even LFS) to Arch was a challenge, too.
But that is now so long ago that I find myself struggling with Mint (Debian based, if you go far enough down the line). :man_shrugging:

1 Like