Bug 2022652 - cmsfs-fuse: Could not initialize conversion table CP1047->UTF-8
Summary: cmsfs-fuse: Could not initialize conversion table CP1047->UTF-8
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: s390utils
Version: 36
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-12 09:56 UTC by Jan Stodola
Modified: 2022-02-11 16:26 UTC (History)
1 user (show)

Fixed In Version: s390utils-2.19.0-1.fc36
Clone Of:
: 2022702 (view as bug list)
Environment:
Last Closed: 2022-02-11 16:26:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Stodola 2021-11-12 09:56:16 UTC
Description of problem:
cmsfs-fuse fails to mount a CMS disk when the --ascii option is used and the glibc-gconv-extra package is not installed:

[root@rtt6 ~]# rpm -q glibc-gconv-extra
package glibc-gconv-extra is not installed
[root@rtt6 ~]# cmsfs-fuse --ascii /dev/disk/by-path/ccw-0.0.0191 /mnt/cms/
cmsfs-fuse: Could not initialize conversion table CP1047->ISO-8859-1.
[root@rtt6 ~]# echo $?
1
[root@rtt6 ~]# yum install glibc-gconv-extra
.
.
.
[root@rtt6 ~]# cmsfs-fuse --ascii /dev/disk/by-path/ccw-0.0.0191 /mnt/cms/
[root@rtt6 ~]# echo $?
0
[root@rtt6 ~]#


Version-Release number of selected component (if applicable):
s390utils-cmsfs-fuse-2.18.0-2.fc36.s390x

How reproducible:
always

Steps to Reproduce:
1. see above

Actual results:
Failed to mount the disk.

Expected results:
s390utils-cmsfs-fuse requires glibc-gconv-extra if it needs it.
The disk is mounted successfully.

Comment 1 Dan Horák 2021-11-12 10:18:22 UTC
glibc-gconv-extra is only Recommended by main glibc package, let's make it a full dep for the cmsfs-fuse subpackage

Comment 2 Ben Cotton 2022-02-08 21:28:17 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.


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