Bug 82731 – GPG key question in up2date not translated

Bug 82731 - GPG key question in up2date not translated

Summary:	GPG key question in up2date not translated

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	up2date (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Adrian Likins
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	79579 82264
	Show dependency tree / graph

Reported:	2003-01-25 10:40 EST by Christian Rose
Modified:	2007-04-18 12:50 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2003-04-07 12:48:07 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Christian Rose 2003-01-25 10:40:33 EST

Tested with beta4 and sv_SE.

The question:

"Your GPG keyring does not contain the Red Hat, Inc. public key.\n"
"Without it, you will be unable to to verify that packages Update Agent "
"downloads are securely signed by Red Hat."
"\n"
"Your Update Agent options specify that you want to use GPG.\n"
"\n"
"Install key?"

isn't translated at all, although up2date is 100% translated. Perhaps this
message  wasn't marked for translation by accident?

Comment 1 Adrian Likins 2003-01-28 00:42:07 EST

I think this is the case of a stale .pot file, should be
fixed now, with translations to follow.

Comment 2 Adrian Likins 2003-02-12 16:59:09 EST

should be fixed in latest 3.1.15 or so

Comment 3 Jay Turner 2003-02-13 00:44:43 EST

I'm still not getting translated message with up2date-3.1.15-7.  Don't know if
you meant the po file would be fixed up or if you meant the translations would
be in with this cut of the code.

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