Bug 1495264
Summary: | Missing icons in emacs | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Stephen John Smoogen <smooge> |
Component: | emacs | Assignee: | Jan Synacek <jsynacek> |
Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.4 | CC: | dbasant, fkrska, jss, jwright, nomad, riehecky, vorpal |
Target Milestone: | rc | Keywords: | Patch |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-09 09:01:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1551061 |
Description
Stephen John Smoogen
2017-09-25 16:00:24 UTC
Nothing changed in Emacs. As you say, this is likely due to GTK rebase. That patch has 31 hunks out of which roughly half fails to apply. https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=3f4c6d52d345999938bc2d4a53246af4c61ef176 Yeah.. it applies cleanly to 24.5 versus 24.3 and it looks like 24.4 and 24.5 have various gtk3 code added in so I am not sure the patch itself can be applied without that code also. So my guess is that emacs may need to be bumped or a lot of backporting (to the point where 24.3 is 24.5) may be needed. Weeeeee. software is fun! Possibly a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1477745. Oh. I'm not authorised to access: https://bugzilla.redhat.com/show_bug.cgi?id=1551061 Thanks very much RedHat, for making it impossible for me to understand what is responsible for holding up this fix. Brilliant. The referenced bug is used for internal tracking purposes, and has no relevant information in regards to progress of this bug. (In reply to Joe Wright from comment #6) > The referenced bug is used for internal tracking purposes, and has no > relevant information in regards to progress of this bug. Sorry, WHAT? Are you insane? Do you not understand that listing a bug as a blocker indicates that this bug here cannot be resolved until the blocking bug is first resolved?? It therefore discourages people from making any attempt to actually resolve this bug. AND IF PEOPLE CANNOT EVEN SEE THE CONTENTS OF THE BUG THAT BLOCKS THIS ONE< HOW MUCH PROGRESS DO YOU THINK IS GOING TO BE MADE EH? Open up bug 1551061 so we can see what is in it, and remove it from the list of blockers. It should NOT be listed there. Hi John, BugMasta, please don't worry. It's the other way round - this bug blocks the internal tracker/list. Bugs that would block this one would be listed in "Depends On" field, which is empty in our case. (In reply to Jan Synacek from comment #4) > Possibly a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1477745. It actually is a duplicate, closing this one. (In reply to BugMasta from comment #5) > Oh. I'm not authorised to access: > https://bugzilla.redhat.com/show_bug.cgi?id=1551061 It's a tracker bug, you don't have to worry about it. You have already expressed yourself in https://bugzilla.redhat.com/show_bug.cgi?id=1477745#c20, which is a real duplicate of this bug. (In reply to John from comment #7) > Are you insane? No, but thanks for asking. As mentioned above, this issue is tracked and scheduled to fix in 7.6 in bug 1477745. *** This bug has been marked as a duplicate of bug 1477745 *** (In reply to Filip Krska from comment #8) > Hi John, BugMasta, please don't worry. It's the other way round - this bug > blocks the internal tracker/list. Bugs that would block this one would be > listed in "Depends On" field, which is empty in our case. Woops. I humbly stand corrected. Sorry for my little dummy spit there. And, as it looks like there has been some progress and there might be a fix released soon, let me take this opportunity to offer my humble thanks to everyone who has helped fix this bug. Let's hope it gets released asap. (In reply to Jan Synacek from comment #9) Also, extra apologies to Jan. Much soz. |