Bug 22237 - Update request: util-linux 2.31.1 (with patch)
Summary: Update request: util-linux 2.31.1 (with patch)
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: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-19 23:22 CET by Stig-Ørjan Smelror
Modified: 2018-04-21 18:23 CEST (History)
1 user (show)

See Also:
Source RPM: util-linux-2.30.1-2.mga7.x86_64
CVE:
Status comment:


Attachments
util-linux 2.31.1 patch (2.19 KB, patch)
2017-12-19 23:23 CET, Stig-Ørjan Smelror
Details | Diff

Description Stig-Ørjan Smelror 2017-12-19 23:22:39 CET
Hi.

Created a patch for util-linux to version 2.31.1 with the two new files included.
The patch also contains an Obsoletes for rfkill.

Have submitted a patch to Shlomi for bash-competions that removes their rfkill section.

Cheers,
Stig
Comment 1 Stig-Ørjan Smelror 2017-12-19 23:23:36 CET
Created attachment 9844 [details]
util-linux 2.31.1 patch
Comment 2 Ben McMonagle 2018-04-18 23:12:02 CEST
update today failed with:

Installation failed:    file /usr/sbin/rfkill from install of util-linux-2.32-1.mga7.x86_64 conflicts with file from package rfkill-1:0.5-6.mga6.x86_64
update of all packages is aborted.

removal of rfkill allows update to proceed.

unfortunately, attempting to reinstall rfkill (# urpmi rfkill) fails with above message.

CC: (none) => westel

Comment 3 Stig-Ørjan Smelror 2018-04-18 23:19:34 CEST
Hi.

Yes, I am aware and have pushed an update that fixes this.
I forgot that rfkill had an epoch when I first tried to obsolete it.

util-linux-2.32-3.mga7 is on its way to the mirrors now.

Cheers,
Stig
Comment 4 Ben McMonagle 2018-04-20 08:39:28 CEST
after latest updates:

# urpmi rfkill
Package util-linux-2.32-4.mga7.x86_64 is already installed


# urpmi rfkill
Package util-linux-2.32-4.mga7.i586 is already installed

looks good

recommend resolved / fixed
Comment 5 David Walser 2018-04-21 18:23:29 CEST
You can mark it as fixed.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


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