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 1723283 - nautlus should not require brasero-nautilus on ppc64 and s390x
Summary: nautlus should not require brasero-nautilus on ppc64 and s390x
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nautilus
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.8
Assignee: Ondrej Holy
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1722135
Blocks: 1738389
TreeView+ depends on / blocked
 
Reported: 2019-06-24 07:28 UTC by Tomas Pelka
Modified: 2020-03-31 19:40 UTC (History)
2 users (show)

Fixed In Version: nautilus-3.26.3.1-7.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 19:39:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1021 0 None None None 2020-03-31 19:40:27 UTC

Description Tomas Pelka 2019-06-24 07:28:52 UTC 
Description of problem:
we do not ship brasero on s390x and ppc64, nautilus should not depend on nautilus-brasero on mantioned arches

Version-Release number of selected component (if applicable):
nautilus-3.26.3.1-6.el7

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Ondrej Holy 2019-06-26 12:41:00 UTC 
It should not be a problem to fix this and would be nice to do so as I suppose that it breaks dependencies for yum...
Comment 2 Tomas Pelka 2019-06-26 13:15:41 UTC 
We need blocker granted at this point. On the other hand is it there for some time and nobody complained yet.
Comment 3 Tomas Pelka 2019-06-26 13:17:09 UTC 
(In reply to Tomas Pelka from comment #2)
> We need blocker granted at this point. On the other hand is it there for
> some time and nobody complained yet.

Let's have 7.7.z as plan B and 7.8 as plan C.
Comment 4 Ondrej Holy 2019-06-27 13:09:54 UTC 
Just note that brasero-nautilus dependency is in RHEL-only, so it should be enough to fix it here by "%ifnarch s390x ppc64".
Comment 6 Ondrej Holy 2019-08-08 13:06:49 UTC 
Hmm, I've pushed the fix, but meson is obviously broken in the buildroot.
Comment 8 Pavlin Georgiev 2019-08-26 13:11:02 UTC 
TEST SETUP
Distro: RHEL 7.7 Server PPC64
Component version: nautilus-3.26.3.1-6.el7.ppc64


TEST PROCEDURE
1. List dependencies of nautilus:
    yum deplist nautilus
    
  ...
    dependency: brasero-nautilus
   provider: brasero-nautilus.ppc64 3.12.2-5.el7
  dependency: brasero-nautilus
   provider: brasero-nautilus.ppc64 3.12.2-5.el7

2. Download and install Brew build:
    nautilus-3.26.3.1-7.el7
3. Check dependencies:
    # rpm -q nautilus 
    nautilus-3.26.3.1-7.el7.ppc64
    # rpm -q --requires nautilus


RESULT
Dependency between brasero and nautilus does not exist.
Comment 9 Pavlin Georgiev 2019-08-26 13:11:37 UTC 
TEST SETUP 2
Distro: RHEL 7.7 Server s390x
Component version: nautilus-3.26.3.1-6.el7.s390x


TEST PROCEDURE 2
1. List dependencies of nautilus:
    yum deplist nautilus
    
  ...
    dependency: brasero-nautilus
   provider: brasero-nautilus.s390x 3.12.2-5.el7
  dependency: brasero-nautilus
   provider: brasero-nautilus.s390x 3.12.2-5.el7

2. Download and install Brew build:
    nautilus-3.26.3.1-7.el7
3. Check dependencies:
    # rpm -q nautilus 
    nautilus-3.26.3.1-7.el7.s390x
    # yum deplist nautilus


RESULT 2
Dependency between brasero and nautilus does not exist.
Comment 10 Pavlin Georgiev 2019-08-26 13:11:51 UTC 
OUTCOME
Upgrading component: nautilus
    from: 3.26.3.1-6.el7
      to: 3.26.3.1-7.el7
has fixed the bug.
Comment 12 errata-xmlrpc 2020-03-31 19:39:43 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1021
Note You need to log in before you can comment on or make changes to this bug.