Bug 27091 - ostree: Standard output type syslog is obsolete
Summary: ostree: 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: https://github.com/ostreedev/ostree/i...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-12 13:35 CEST by Bit Twister
Modified: 2020-10-30 13:43 CET (History)
2 users (show)

See Also:
Source RPM: ostree-2020.4-2.mga8.src.rpm
CVE:
Status comment:

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

Description Bit Twister 2020-08-12 13:35:29 CEST 
Description of problem:  mga8 dev0

Standard output type syslog is obsolete, automatically updating to journal.
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 'syslog is obsolete'
2.
3.
Comment 1 Olav Vitters 2020-08-12 13:49:26 CEST 
Upstream problem, reported it at https://github.com/ostreedev/ostree/issues/2169

CC: (none) => olav
URL: (none) => https://github.com/ostreedev/ostree/issues/2169

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

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

See also Bugs 27092, 27096.

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

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

Aurelien Oudelet 2020-08-24 11:30:16 CEST

CC: ouaurelien => (none)

Comment 3 Aurelien Oudelet 2020-08-24 11:34:03 CEST 
Upstream has merged patch 3 days ago.
https://github.com/ostreedev/ostree/issues/2169
Comment 4 Aurelien Oudelet 2020-10-30 13:43:03 CET 
Fixed upstream in ostree 2020.6 and we are at 2020.7 in Cauldron.

Closing this.

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