| Summary: | man can't read bcd files | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Daniel Tartavel <contact> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, sysadmin-bugs, tarazed25 |
| Version: | 6 | Keywords: | advisory, validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA6-64-OK MGA6-32-OK | ||
| Source RPM: | bcd-3.7-10.mga6.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Daniel Tartavel
2017-10-08 23:14:46 CEST
commit d645815b1d83871303fd5ac36bcb1ddbeaec76bd
Author: Jani Välimaa <wally@...>
Date: Mon Oct 9 17:11:54 2017 +0300
Compress man pages with xz (mga#21822)
---
Commit Link:
http://gitweb.mageia.org/software/build-system/bcd/commit/?id=d645815b1d83871303fd5ac36bcb1ddbeaec76bd
Pushed bcd-3.7-10.1.mga6 to core/updates_testing. It should fix the issue, please test. Assignee:
bugsquad =>
qa-bugs Hi, tested, all is running fine, man pages are well displayed. Thanks $ man bcd man: warning: /usr/share/man/man1/bcd.1.lzma.xz: ignoring bogus filename No manual entry for bcd $ man conf.xml man: warning: /usr/share/man/man1/conf.xml.1.lzma.xz: ignoring bogus filename No manual entry for conf.xml Updated to bcd-3.7-10.1.mga6 for x86_64 $ man bcd Now working fine. $ man conf.xml CONF.XML(1) User Contributed Perl Documentation CONF.XML(1) ................. OK for 64 bits. CC:
(none) =>
tarazed25
Len Lawrence
2017-10-10 22:10:57 CEST
Whiteboard:
(none) =>
MGA6-64-OK Don't know if a 32-bit test is necessary with this noarch package but am doing it anyway. mga6 in i586 virtualbox man displays the reported fault before the update of bcd and it is gone after the update.
Len Lawrence
2017-10-10 22:28:49 CEST
Whiteboard:
MGA6-64-OK =>
MGA6-64-OK MGA6-32-OK
Lewis Smith
2017-10-11 21:17:09 CEST
Keywords:
(none) =>
advisory, validated_update Closing as Mageia robot failed to do so due to lack of permissions, which has now been fixed. Resolution:
(none) =>
FIXED An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2017-0096.html |