[SOLVED ]Updated to Sylvia 18.3 but software sources says Rosa 17.3

[u2rishi]

Hi
I updated to Sylvia but repository do not upgrade
Etc/issue says Rosa. While elsewhere it says 18.3 Rosa

Also key issue appears.

Code.txt

Different commands I used

(4.77 KiB) Downloaded 13 times

[MikeNovember]

Hi
I updated to Sylvia but repository do not upgrade
Etc/issue says Rosa. While elsewhere it says 18.3 Rosa

Also key issue appears.
Code.txt

Hi,

You updated from an obsolete version of Mint, Sylvia, to another obsolete version of Mint, Rosa.

The errors show that Rosa repo is no longer signed (and probably no longer available).

Maintained versions of Mint are 19.x and 20.x. You should update to one of these versions.

Regards,

MN

[u2rishi]

Actually I updated to Sylvia That is 18.3 not to Rosa. To be able to install linuxmint 19 I have to completely install 18.3

[Larry78723]

I suggest you backup personal files in /home then do a clean install of either LM 19 or LM20.

[u2rishi]

Here output of inxi -Sr

Code: Select all

inxi -Sr
System:    Host: rishi-M61PME-S2P Kernel: 4.4.0-21-generic i686 (32 bit) Desktop: Cinnamon 3.6.7
           Distro: Linux Mint 17.3 Rosa
Repos:     Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
           deb http://packages.linuxmint.com rosa main upstream import
           deb http://extra.linuxmint.com rosa main
           deb http://archive.ubuntu.com/ubuntu trusty main restricted universe multiverse
           deb http://archive.ubuntu.com/ubuntu trusty-updates main restricted universe multiverse
           deb http://security.ubuntu.com/ubuntu/ trusty-security main restricted universe multiverse
           deb http://archive.canonical.com/ubuntu/ trusty partner
 

and GPG error

Code: Select all

W: GPG error: http://extra.linuxmint.com rosa Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3EE67F3D0FF405B2
E: The repository 'http://extra.linuxmint.com rosa Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://packages.linuxmint.com rosa Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3EE67F3D0FF405B2
E: The repository 'http://packages.linuxmint.com rosa Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

[karlchen]

Hello, ur2rishi.

As had been explained correctly above, you updated to Linux Mint 17.3 Rosa. Your own inxi output confirms so.

Code: Select all

inxi -Sr
System:    Host: rishi-M61PME-S2P Kernel: 4.4.0-21-generic i686 (32 bit) Desktop: Cinnamon 3.6.7
           Distro: Linux Mint 17.3 Rosa

Liux Mint 17.3 Rosa is as dead as a dead mouse can be.
Please, do as suggested. Choose a still supported release. Test its live desktop in order to make sure that it works on your machine. Only if it does, install the chosen release from scratch.

Regards,
Karl

[all41]

@u2rishi
your upgrade plans are treacherous, tedious, and time-consuming.
Go with the good advice--back up your stuff and do a fresh install of Mint
that is supported thru 2025

[u2rishi]

Hi

Yes! You people know much more but it's my duty to inform and morever I have space constraints
Moreover

Code: Select all

$ hostnamectl
   Static hostname: rishi-M61PME-S2P
         Icon name: computer-desktop
           Chassis: desktop
        Machine ID: 
           Boot ID: 
  Operating System: Linux Mint 18.3
            Kernel: Linux 4.4.0-21-generic
      Architecture: x86

[cliffcoggin]

It really does not matter whether you have Mint 17 or Mint 18. They are both defunct. Trying to update from 17 to 18 when they were both current was always fraught with difficulties; trying to do it when both versions are dead is a waste of time. Do a fresh installation of 19 or 20.

[u2rishi]

Sure
@cliffcoggin

[u2rishi]

Hi!

Thanks for your reprimand! I am now on linuxmint 19
Tara. It was config file issue that caused to retain old Linuxmint name appearance. Now I used the mainter's version.

Thanks anyway.!