RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2135428 - RHEL8 AppStream and Devel channels missing mecab-devel rpm
Summary: RHEL8 AppStream and Devel channels missing mecab-devel rpm
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: mecab
Version: 8.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Michal Schorm
QA Contact: Jakub Heger
URL:
Whiteboard:
Depends On:
Blocks: 2180411
TreeView+ depends on / blocked
 
Reported: 2022-10-17 15:54 UTC by Cesar Sanchez
Modified: 2023-05-22 12:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2180411 (view as bug list)
Environment:
Last Closed: 2023-05-22 12:27:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-136722 0 None None None 2022-10-17 16:06:02 UTC

Description Cesar Sanchez 2022-10-17 15:54:44 UTC 
Description of problem:
The rpm 'mecab-devel' is missing from the module and the AppStream repository.

This causes an issue when I tried to deploy mecab-python3 in a virtualenv, because:
```
            "                                running install",
            "                                running build",
            "                                running build_py",
            "                                creating build",
            "                                creating build/lib.linux-x86_64-3.6",
            "                                creating build/lib.linux-x86_64-3.6/MeCab",
            "                                copying src/MeCab/__init__.py -> build/lib.linux-x86_64-3.6/MeCab",
            "                                running build_ext",
            "                                error: [Errno 2] No such file or directory: 'mecab-config': 'mecab-config'",

```

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

Module stream: mysql-8.0
Rpm version: mecab-0.996-1.module+el8.3.0+242+87d3366a.9.x86_64

How reproducible:


Steps to Reproduce:
1. Create virtualenv with default python 3.6
2. install mecab-python3 pip module (pip install mecab-python3)
3. check failure

Actual results:
```
            "                                running install",
            "                                running build",
            "                                running build_py",
            "                                creating build",
            "                                creating build/lib.linux-x86_64-3.6",
            "                                creating build/lib.linux-x86_64-3.6/MeCab",
            "                                copying src/MeCab/__init__.py -> build/lib.linux-x86_64-3.6/MeCab",
            "                                running build_ext",
            "                                error: [Errno 2] No such file or directory: 'mecab-config': 'mecab-config'",

```

Expected results:

Package installs successfully

Additional info:
Comment 1 Lukas Javorsky 2022-10-18 10:45:23 UTC 
Hi,

We've rebuilt the mecab package in RHEL-8.6.0, but that shouldn't have any effect on the RHEL-8.3.0 version.

New mecab rpm version is: mecab-0.996-2.module+el8.6.0+16523+5cb0e868

Also, I don't think this is the problem within the mysql-module component you've selected, it looks like something may have been broken in python.
Comment 2 Miro Hrončok 2022-10-18 10:53:51 UTC 
Why was this assigned to python-pip?
Comment 3 Miro Hrončok 2022-10-18 11:00:12 UTC 
In Fedora:

$ repoquery -q --repo=rawhide -f /usr/bin/mecab-config
mecab-devel-0:0.996-3.fc37.4.i686
mecab-devel-0:0.996-3.fc37.4.x86_64

Hence,t he problem is the mecab package is in appstream, but mecab-devel is missing from CRB.
This is a request to include mecab-devel in some RHEL 8 repository, which I consider quite resonable.
Comment 4 Lukas Javorsky 2022-10-18 11:14:30 UTC 
Ah, sorry Miro, 

I misunderstood that this is the request for adding the mecab to the Appstream repo.
Comment 5 Lukas Javorsky 2022-10-18 13:55:50 UTC 
Thank you Cesar for taking the time to report this issue to us. We appreciate the feedback and use reports such as this one to guide our efforts at improving our products. That being said, this bug-tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.

If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution.

For information on how to contact the Red Hat production support team, please visit:
    https://access.redhat.com/support
Comment 7 Cesar Sanchez 2022-10-24 13:39:51 UTC 
Hello Lukas.  This bug is not critical for my system as I was able to re-build the mecab package on my own and add mecab-devel to a private repo to fix the issue, however, it'll be nice if the repos get fixed accordingly. I presume, my next deployments will be fixed when I target 8.6.  I don't need to request support.

Thanks.
Comment 8 Lukas Javorsky 2022-10-24 14:06:32 UTC 
Yes, we are evaluating the request.

Once we have an update, we'll let you know.

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