Bug 533611 - Please move macros.xemacs into xemacs-common package
Summary: Please move macros.xemacs into xemacs-common package
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xemacs
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-07 20:02 UTC by Jonathan Underwood
Modified: 2009-11-18 14:16 UTC (History)
1 user (show)

Fixed In Version: 21.5.29-8.fc12
Clone Of:
Environment:
Last Closed: 2009-11-18 14:15:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jonathan Underwood 2009-11-07 20:02:53 UTC
Description of problem:
Presently the /etc/rpm/macros.xemacs file is part of the xemacs package rather than the xemacs-common package. Please could you move it to the xemacs-common package for consistency with the emacs packaging, and so that the macros are still defined if a user installs xemacs-nox. It's be nice to push this for F-12 and upwards.

Comment 1 Jerry James 2009-11-09 16:44:23 UTC
Awww, man, I just pushed a fix for another packaging problem.  Can you please find all remaining bugs in XEmacs and its packaging so I can fix them all at once and be done with it? :-)

I'll have a new package out shortly.

Comment 2 Jonathan Underwood 2009-11-09 16:58:47 UTC
(In reply to comment #1)
> Awww, man, I just pushed a fix for another packaging problem.  Can you please
> find all remaining bugs in XEmacs and its packaging so I can fix them all at
> once and be done with it? :-)
> 

Heh. It's far more fun just to drip feed you them one by one :). More seriously, the xemacs package is in great shape I think.

> I'll have a new package out shortly.  

Thanks - there's no urgency to pushing an update, if you wanted to wait until a more severe bug causes a package push. Your call.

Comment 3 Jerry James 2009-11-09 17:04:56 UTC
Well, upstream just told me that my fix for the recently reported TTY font bug was totally bogus and gave me a different patch to try.  I'll go ahead and make a new package to address both problems.

Comment 4 Fedora Update System 2009-11-09 18:12:44 UTC
xemacs-21.5.29-7.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/xemacs-21.5.29-7.fc11

Comment 5 Fedora Update System 2009-11-09 18:12:49 UTC
xemacs-21.5.29-8.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/xemacs-21.5.29-8.fc12

Comment 6 Fedora Update System 2009-11-11 15:03:04 UTC
xemacs-21.5.29-7.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xemacs'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-11364

Comment 7 Fedora Update System 2009-11-11 15:05:08 UTC
xemacs-21.5.29-8.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xemacs'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-11382

Comment 8 Bug Zapper 2009-11-16 15:17:47 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Fedora Update System 2009-11-18 14:15:45 UTC
xemacs-21.5.29-7.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2009-11-18 14:16:34 UTC
xemacs-21.5.29-8.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.


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