Bug 1956059 - [SPEC] rpm -V failures
Summary: [SPEC] rpm -V failures
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-02 11:52 UTC by Davide Repetto
Modified: 2021-05-11 02:08 UTC (History)
11 users (show)

Fixed In Version: systemd-248.2-1.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-11 02:08:14 UTC
Type: Bug


Attachments (Terms of Use)

Description Davide Repetto 2021-05-02 11:52:32 UTC
Description of problem:
=======================

The following always happens, because the info in the spec file do not match the settings in /lib/tmpfiles.d/systemd.conf

# rpm -V systemd
.M.......  g /var/log/btmp
.M....G..  g /var/log/journal

The same bug was corrected in an errata on RHEL (bug# 1545372)


Version-Release number of selected component:
=============================================

systemd-248-2.fc34.x86_64

Comment 1 Fedora Update System 2021-05-08 09:17:26 UTC
FEDORA-2021-775e2373a1 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-775e2373a1

Comment 2 Fedora Update System 2021-05-09 02:20:04 UTC
FEDORA-2021-775e2373a1 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-775e2373a1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-775e2373a1

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

Comment 3 Fedora Update System 2021-05-11 02:08:14 UTC
FEDORA-2021-775e2373a1 has been pushed to the Fedora 34 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.