Bug 1899808 - Unable to install from Server or Everything netinstall images due to problem with installation of cppcheck RPM
Summary: Unable to install from Server or Everything netinstall images due to problem ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cppcheck
Version: 33
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: c72578
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-20 05:14 UTC by Pat Barron
Modified: 2020-12-02 01:38 UTC (History)
9 users (show)

Fixed In Version: cppcheck-2.2-5.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-02 01:38:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Pat Barron 2020-11-20 05:14:57 UTC
User-Agent:       Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36
Build Identifier: 

Upon trying to do a network install using either the Fedora Server or Fedora Everything netinstall images, the installation downloads all of the necessary RPMs, begins installing them, but eventually fails with the following message:

+--------------
|
|  The following error occurred while installing.  This is a fatal error and
|  installation will be aborted.
|
|  DNF error: Error in POSTIN scriptlet in rpm package cppcheck
|
+---------------

The only option for recovery that I'm given at this point is "Exit Installer".

During these installation attempts, I am trying to install as "Development and Creative Workstation", with a number of additional package subgroups selected.

Reproducible: Always

Steps to Reproduce:
1.  Attempt to use Fedora Server or Fedora Everything netinstall image to install new system.
2.  Choose "Development and Creative Workstation" installation.
3.  Set other parameters in the installer (disk partitioning, date and time, root password and user setup, etc.) as appropriate for the installation.
Actual Results:  
Installation fails as described above.

Expected Results:  
Installation succeeds and produces a bootable, usable Fedora 33 system.

Comment 1 Pat Barron 2020-11-20 11:05:39 UTC
As additional information, this problem does not occur if I install as "Fedora Workstation", rather than "Development and Creative Workstation", choosing the same sets of additional software to install.

Comment 2 Vendula Poncova 2020-11-23 11:04:47 UTC
All RPM errors are fatal during the installation (see the bug 1565123). Reassigning.

Comment 3 c72578 2020-11-23 11:19:29 UTC
Thanks for your bug report.
I will prepare a new build of cppcheck for F33, based on the current commit in rawhide, which does not use %post anymore.
https://src.fedoraproject.org/rpms/cppcheck/c/60fb1138096d4ba9158cf9f2278ee133e7dd2028?branch=master

Comment 4 Fedora Update System 2020-11-23 18:29:25 UTC
FEDORA-2020-3c37e5ea7d has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3c37e5ea7d

Comment 5 Fedora Update System 2020-11-24 01:26:34 UTC
FEDORA-2020-3c37e5ea7d has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3c37e5ea7d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3c37e5ea7d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Pat Barron 2020-11-30 04:30:08 UTC
I've tested this by performing a network install using the Fedora Server 33 netinstall ISO image, in the same way I did before, except that I added the updates-testing repo as an additional repository during the installation.  I can confirm that the RPM error on cppcheck during installation no longer occurs.

Comment 7 Fedora Update System 2020-12-02 01:38:09 UTC
FEDORA-2020-3c37e5ea7d has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.