Bug 27092 - dracut; Standard output type syslog is obsolete,
Summary: dracut; Standard output type syslog is obsolete,
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Base system maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-12 13:40 CEST by Bit Twister
Modified: 2020-10-30 13:39 CET (History)
3 users (show)

See Also:
Source RPM: dracut-050-2.mga8.src.rpm
CVE:
Status comment:

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

Description Bit Twister 2020-08-12 13:40:24 CEST 
Description of problem: mga8 dev0

numerous messages with
Standard output type syslog is obsolete, automatically updating to journal.
Please update your unit file, and consider removing the setting altogether.

Standard output type syslog+console is obsolete,
automatically updating to journal+console. Please update your unit file,
and consider removing the setting altogether.

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


How reproducible:


Steps to Reproduce:
1.journalctl --no-hostname | grep -E "obsolete|\+console"
2.
3.
Comment 1 Olav Vitters 2020-08-12 14:39:01 CEST 
Upstream issue. Difficult to determine where to report bugs. Maybe their mailing list?

CC: (none) => olav

Comment 2 Aurelien Oudelet 2020-08-12 18:45:35 CEST 
Confirmed.

This complain comes from time when systemd was updated to 246.

See also Bugs 27092, 27091.


This is non blocker but our Units files should be adapted from these packages.
Assigning to basesystem maintainers.

Assignee: bugsquad => basesystem
CC: (none) => ouaurelien

Comment 3 Martin Whitaker 2020-08-12 19:40:49 CEST 
Already fixed upstream. Please test dracut-050-3.mga8 when it reaches the mirrors.

CC: (none) => mageia

Comment 4 Aurelien Oudelet 2020-10-30 13:39:54 CET 
No longer see since Martin pinged this.
We are at dracut-050-4.mga8 in Cauldron.

Closing this fixed.

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