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 1000325 - Subpackage evolution-exchange is no longer multilib-clean for s390x vs s390
Summary: Subpackage evolution-exchange is no longer multilib-clean for s390x vs s390
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution-exchange
Version: 6.5
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-23 08:00 UTC by Tomas Pelka
Modified: 2013-11-21 04:55 UTC (History)
2 users (show)

Fixed In Version: evolution-exchange-2.32.3-12.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1000323
Environment:
Last Closed: 2013-11-21 04:55:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1540 0 normal SHIPPED_LIVE Low: evolution security, bug fix, and enhancement update 2013-11-21 00:40:51 UTC

Description Tomas Pelka 2013-08-23 08:00:24 UTC
Description of problem:
12 files now have non-equal 32/64bit content where all matched before:

  /usr/share/gtk-doc/html/evolution-exchange/ximian-connnector-booking.html
  /usr/share/gtk-doc/html/evolution-exchange/ximian-connector-permissions.html
  /usr/share/gtk-doc/html/evolution-exchange/ximian-connector-other-users.html
  /usr/share/gtk-doc/html/evolution-exchange/ximian-connector-freebusy.html
  /usr/share/gtk-doc/html/evolution-exchange/ximian-connector-autoconfig.html
  /usr/share/gtk-doc/html/evolution-exchange/evolution-exchange.devhelp2
  /usr/share/gtk-doc/html/evolution-exchange/evolution-exchange.devhelp
  /usr/share/gtk-doc/html/evolution-exchange/ch05.html
  /usr/share/gtk-doc/html/evolution-exchange/ch04.html
  /usr/share/gtk-doc/html/evolution-exchange/ch03.html
(truncated at 10 files)

details at https://errata.devel.redhat.com/rpmdiff/show/75868?result_id=1578706

Version-Release number of selected component (if applicable):
evolution-2.32.3-21.el6

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:
Not sure if this is an gtk-doc issue or one can force gtk-doc to generate exactly the same doc

Expected results:
doc files must be the same

Additional info:
it might be workarounded by adding noarch subpackage with doc

Comment 1 Milan Crha 2013-08-23 09:59:33 UTC
OK, I'll remove the gtk-doc for evolution-exchange. To be honest, I do not think it's useful at all, especially these days.

Comment 8 errata-xmlrpc 2013-11-21 04:55:35 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.

http://rhn.redhat.com/errata/RHSA-2013-1540.html


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