Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionRed Hat Case Diagnostics
2011-02-22 00:50:50 UTC
This description generated by Andreas from an ABRT report
architecture: x86_64
cmdline:
comment: Pulling status of large repo.
component: mercurial
executable: /usr/bin/hg
kernel: 2.6.32-71.14.1.el6.x86_64
package: mercurial-1.7.3-1.el6.rfx
reason: dispatch.py:40:catchterm:SignalInterrupt
release: Red Hat Enterprise Linux Server release 6.0 (Santiago)
reproduce: 1.Pulling status of large repo.
time: 1298335701
uid: 500
backtrace: dispatch.py:40:catchterm:SignalInterrupt
Traceback (most recent call last):
File "/usr/bin/hg", line 38, in <module>
mercurial.dispatch.run()
File "/usr/lib64/python2.6/site-packages/mercurial/dispatch.py", line 16, in run
sys.exit(dispatch(sys.argv[1:]))
File "/usr/lib64/python2.6/site-packages/mercurial/dispatch.py", line 36, in dispatch
return _runcatch(u, args)
File "/usr/lib64/python2.6/site-packages/mercurial/dispatch.py", line 110, in _runcatch
ui.warn(_("killed!\n"))
File "/usr/lib64/python2.6/site-packages/mercurial/ui.py", line 518, in warn
self.write_err(*msg, **opts)
File "/usr/lib64/python2.6/site-packages/mercurial/ui.py", line 369, in write_err
sys.stderr.write(str(a))
File "/usr/lib64/python2.6/site-packages/mercurial/dispatch.py", line 40, in catchterm
raise error.SignalInterrupt
SignalInterrupt
Local variables in innermost frame:
args: (15, <frame object at 0x6f1b4b0>)
Comment 1Red Hat Case Diagnostics
2011-02-22 00:51:14 UTC
Comment 4RHEL Program Management
2011-02-22 01:18:20 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 6RHEL Program Management
2011-07-06 00:32:35 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
This description generated by Andreas from an ABRT report architecture: x86_64 cmdline: comment: Pulling status of large repo. component: mercurial executable: /usr/bin/hg kernel: 2.6.32-71.14.1.el6.x86_64 package: mercurial-1.7.3-1.el6.rfx reason: dispatch.py:40:catchterm:SignalInterrupt release: Red Hat Enterprise Linux Server release 6.0 (Santiago) reproduce: 1.Pulling status of large repo. time: 1298335701 uid: 500 backtrace: dispatch.py:40:catchterm:SignalInterrupt Traceback (most recent call last): File "/usr/bin/hg", line 38, in <module> mercurial.dispatch.run() File "/usr/lib64/python2.6/site-packages/mercurial/dispatch.py", line 16, in run sys.exit(dispatch(sys.argv[1:])) File "/usr/lib64/python2.6/site-packages/mercurial/dispatch.py", line 36, in dispatch return _runcatch(u, args) File "/usr/lib64/python2.6/site-packages/mercurial/dispatch.py", line 110, in _runcatch ui.warn(_("killed!\n")) File "/usr/lib64/python2.6/site-packages/mercurial/ui.py", line 518, in warn self.write_err(*msg, **opts) File "/usr/lib64/python2.6/site-packages/mercurial/ui.py", line 369, in write_err sys.stderr.write(str(a)) File "/usr/lib64/python2.6/site-packages/mercurial/dispatch.py", line 40, in catchterm raise error.SignalInterrupt SignalInterrupt Local variables in innermost frame: args: (15, <frame object at 0x6f1b4b0>)