Bug 34869 - Untrusted files on mageia 9 to mageia10 upgrade
Summary: Untrusted files on mageia 9 to mageia10 upgrade
Status: RESOLVED DUPLICATE of bug 34853
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: RPM stack maintainers
QA Contact:
URL:
Whiteboard:
Keywords: 10alpha1
Depends on:
Blocks:
 
Reported: 2025-12-17 17:53 CET by Daniel Tartavel
Modified: 2025-12-18 18:44 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Daniel Tartavel 2025-12-17 17:53:54 CET 
Description of problem:
upgrading mageia 9 up-to-date to Mageia10 alpha1
installer make errors :
Header V4 RSA/SHA256 Signature, key ID 80420f66: NOTTRUSTED
So installer loop on installation of packages that we can't cancel and we must force stop the computer

Version-Release number of selected component (if applicable):
Mageia10-alpha1-x86_64

How reproducible:
upgrade Mageia 9  to Mageia 10
Frédéric "LpSolit" Buclin 2025-12-17 17:59:33 CET

Keywords: (none) => 10alpha1

Comment 1 Marja Van Waes 2025-12-18 15:53:02 CET 
(In reply to Daniel Tartavel from comment #0)
> Description of problem:
> upgrading mageia 9 up-to-date to Mageia10 alpha1
> installer make errors :
> Header V4 RSA/SHA256 Signature, key ID 80420f66: NOTTRUSTED
> So installer loop on installation of packages that we can't cancel and we
> must force stop the computer
> 
> Version-Release number of selected component (if applicable):
> Mageia10-alpha1-x86_64
> 
> How reproducible:
> upgrade Mageia 9  to Mageia 10

Assigning to the RPM stack maintainers. IIUC, this must be solved  with a Mageia 9 update and can't be solved in the installer. CC'ing Thierry and Martin.

CC: (none) => mageia, marja11, thierry.vignaud
Assignee: bugsquad => rpmstack

Comment 2 katnatek 2025-12-18 18:44:45 CET 
I think this is duplicated from bug#34853

*** This bug has been marked as a duplicate of bug 34853 ***

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.