Bug 497874 - Plethora of typos in error messages
Summary: Plethora of typos in error messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: avahi
Version: 5.3
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Lennart Poettering
QA Contact: BaseOS QE
URL:
Whiteboard:
: 515115 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-27 17:04 UTC by Jay Turner
Modified: 2015-01-08 00:16 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-22 18:13:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1119 0 normal SHIPPED_LIVE avahi bug fix update 2009-06-22 18:13:43 UTC

Description Jay Turner 2009-04-27 17:04:14 UTC
Description of problem:
With 0.6.16-1.el5_2.1 there's a consistent misspelling of the work "received" in the error messages.  Appears that "response" gets misspelled a few times as well.  Should really do an audit to ensure we're not shipping code with embarrassing spellings.

Version-Release number of selected component (if applicable):
0.6.16-1.el5_2.1

Additional info:

# grep -ri "recieved" *
avahi-autoipd/main.c:                    daemon_log(LOG_INFO, "Recieved conflicting normal ARP packet.");
avahi-autoipd/main.c:                        daemon_log(LOG_INFO, "Recieved conflicting probe ARP packet.");
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:            avahi_log_debug("Recieved conflicting probe [%s]. Local host won.", t);
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:            avahi_log_debug("Recieved conflicting probe [%s]. Local host lost. Withdrawing.", t);
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:                avahi_log_debug("Recieved goodbye record for one of our records [%s]. Refreshing.", t);
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:                avahi_log_debug("Recieved record with bad TTL [%s]. Refreshing.", t);
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:            avahi_log_debug("Recieved conflicting record [%s] with local record to be. Withdrawing.", t);
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:            avahi_log_debug("Recieved conflicting record [%s]. Resetting our record.", t);
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:        avahi_log_warn("Recieved packet from invalid interface.");
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:        avahi_log_warn("Recieved invalid packet.");
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:            avahi_log_warn("Recieved repsonse with invalid source port %u on interface '%s.%i'", port, i->hardware->name, i->protocol);
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:            avahi_log_warn("Recieved response with invalid TTL %u on interface '%s.%i'.", ttl, i->hardware->name, i->protocol);
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:        avahi_log_warn("Recieved invalid packet.");
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:        avahi_log_warn("Recieved legacy unicast response with unknown id");
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:            avahi_log_error("Incoming packet recieved on address that isn't local.");
avahi-core/server.c:            avahi_log_debug("Recieved conflicting probe [%s]. Local host won.", t);
avahi-core/server.c:            avahi_log_debug("Recieved conflicting probe [%s]. Local host lost. Withdrawing.", t);
avahi-core/server.c:                avahi_log_debug("Recieved goodbye record for one of our records [%s]. Refreshing.", t);
avahi-core/server.c:                avahi_log_debug("Recieved record with bad TTL [%s]. Refreshing.", t);
avahi-core/server.c:            avahi_log_debug("Recieved conflicting record [%s] with local record to be. Withdrawing.", t);
avahi-core/server.c:            avahi_log_debug("Recieved conflicting record [%s]. Resetting our record.", t);
avahi-core/server.c:        avahi_log_warn("Recieved packet from invalid interface.");
avahi-core/server.c:        avahi_log_warn("Recieved invalid packet.");
avahi-core/server.c:            avahi_log_warn("Recieved repsonse with invalid source port %u on interface '%s.%i'", port, i->hardware->name, i->protocol);
avahi-core/server.c:            avahi_log_warn("Recieved response with invalid TTL %u on interface '%s.%i'.", ttl, i->hardware->name, i->protocol);
avahi-core/server.c:        avahi_log_warn("Recieved invalid packet.");
avahi-core/server.c:        avahi_log_warn("Recieved legacy unicast response with unknown id");
avahi-core/server.c:            avahi_log_error("Incoming packet recieved on address that isn't local.");
avahi-core/iface.c:     * packet is recieved. We have to work around that limitation by
docs/NEWS:  * Don't disable all static services when SIGHUP is recieved.

# grep -ri "repsonse" *
avahi-core/server.c.0001-Don-t-get-confused-by-UDP-packets-with-a-source-port:            avahi_log_warn("Recieved repsonse with invalid source port %u on interface '%s.%i'", port, i->hardware->name, i->protocol);
avahi-core/server.c:            avahi_log_warn("Recieved repsonse with invalid source port %u on interface '%s.%i'", port, i->hardware->name, i->protocol);

Comment 8 Lennart Poettering 2009-06-08 20:16:49 UTC
These are the same typos as in bug 429138.

This should be merged, but I guess that would upset the errata system, so I am not going to do that.

Comment 18 errata-xmlrpc 2009-06-22 18:13:56 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1119.html

Comment 19 Lennart Poettering 2009-11-14 00:11:16 UTC
*** Bug 515115 has been marked as a duplicate of this bug. ***


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