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.

Bug 771736

Summary: Ubuntu references in core packages
Product: Red Hat Enterprise Linux 6 Reporter: Thomas Zine <tzine3>
Component: upstartAssignee: Lukáš Nykrýn <lnykryn>
Status: CLOSED ERRATA QA Contact: qe-baseos-daemons
Severity: low Docs Contact:
Priority: low    
Version: 6.2CC: azelinka, ovasik, prc
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: upstart-0.6.5-11.el6 Doc Type: Bug Fix
Doc Text:
Previous version of upstart pointed to different places where user can report bugs. This version should send user to https://launchpad.net/upstart/+bugs.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 14:00:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Thomas Zine 2012-01-04 19:25:29 UTC
Description of problem:

Ubuntu references in many packages in /sbin

Version-Release number of selected component (if applicable):
6.2

How reproducible:
always

Steps to Reproduce:
1. /sbin/shutdown --help
2.
3.
  
Actual results:
Report bugs to <upstart-devel.com>

Expected results:
RedHat

Additional info:

Comment 2 Ondrej Vasik 2012-01-05 11:46:17 UTC
Why do you think that referencing upstream mailing list is wrong ? Upstart upstream is hosted on launchpad - and this contact email address is provided by upstream (see http://bazaar.launchpad.net/~upstart-devel/upstart/trunk/view/head:/configure.ac ). I'm quite sure that in the case of other packages with upstream on fedorahosted.org, Ubuntu will reference Fedora - that's open source way of development.

However - upstart upstream developers use references to https://launchpad.net/upstart/+bugs in man page, so probably PACKAGE_BUGREPORT reference in configure script could be changed to that too to reduce confusion...

Comment 10 Lukáš Nykrýn 2012-04-10 12:32:23 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previous version of upstart pointed to different places where user can report bugs. This version should send user to https://launchpad.net/upstart/+bugs.

Comment 12 errata-xmlrpc 2012-06-20 14:00:46 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/RHBA-2012-0863.html