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 1765208 - Rebuild emacs due to ImageMagick rebase
Summary: Rebuild emacs due to ImageMagick rebase
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: emacs
Version: 7.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks: 1764595
TreeView+ depends on / blocked
 
Reported: 2019-10-24 14:17 UTC by Jan Horak
Modified: 2020-03-31 20:11 UTC (History)
3 users (show)

Fixed In Version: emacs-24.3-23.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 20:10:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1180 0 None None None 2020-03-31 20:11:11 UTC

Description Jan Horak 2019-10-24 14:17:45 UTC
We need to rebuild this package in order to rebase ImageMagick.

Comment 3 Leos Pol 2019-10-25 06:24:03 UTC
I'm going to ack this even though Franta is on PTO today. If I understand correctly only regression testing is required.

Comment 4 Jan Synacek 2019-10-25 06:25:26 UTC
(In reply to Jan Horak from comment #0)
> We need to rebuild this package in order to rebase ImageMagick.

I'm pretty sure it's the other way around. And you really should do that automatically as an atomic operation, otherwise dependencies of IM will break.

Comment 5 Tomas Pelka 2019-10-25 07:41:49 UTC
(In reply to Leos Pol from comment #3)
> I'm going to ack this even though Franta is on PTO today. If I understand
> correctly only regression testing is required.

That is correct no code change in emacs just a matter of rebuild against new IM.

Comment 6 Tomas Pelka 2019-10-25 07:42:30 UTC
(In reply to Jan Synacek from comment #4)
> (In reply to Jan Horak from comment #0)
> > We need to rebuild this package in order to rebase ImageMagick.
> 
> I'm pretty sure it's the other way around. And you really should do that
> automatically as an atomic operation, otherwise dependencies of IM will
> break.

The plan is to build everything in side tag so we can push to compose all in one.

Comment 11 errata-xmlrpc 2020-03-31 20:10:51 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:1180


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