My Favorites

Close

Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

"Installation of package /suse/noarch/suse-build-key-1.0-685.6.noarch.rpm failed." during product installation

This document (3257992) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 10
SUSE Linux Enterprise Desktop 10

Situation

Issue

During installation of a SUSE Linux Enterprise 10 product the Package Installation process halts giving the following error:

ERROR: Installation of package /suse/noarch/suse-build-key-1.0-685.6.noarch.rpm failed.

Under the "Show Details" button a more verbose message is available, similar to the following:

Subprocess failed: Error: RPM failed: importing SuSE build key to rpm keyring...
gpg: key 307E3D54 was created 6831144 seconds in the future (time warp or clock problem)
gpg: key 307E3D54 was created 6831144 seconds in the future (time warp or clock
problem)
gpg: key 307E3D54: no valid user IDs
gpg: key A1912208 was created 11675492 seconds in the future (time warp or clock problem)
gpg: key A1912208 was created 11675492 seconds in the future (time warp or clock problem)
gpg: key A1912208: no valid user IDs
gpg: key 7E2E3B05 was created 12364165 seconds in the future (time warp or clock problem)
gpg: key 7E2E3B05 was created 12364165 seconds in the future (time warp or clock problem)
gpg: key 7E2E3B05: no valid user IDs
gpg: no ultimately trusted keys found
importing the key from the file usr/lib/rpm/gnupg/suse-build-key.gpg
returned an error. This should not happen. It may not be possible
to properly verify the authenticity of rpm packages from SuSE sources.
The keyring containing the SuSE rpm package signing key can be found
in the root directory of the first CD (DVD) of your SuSE product.
error: %post(suse-build-key-1.0-685.6.noarch) scriptlet failed, exit status 255


Root Cause

RPM packages in SUSE Linux products are digitally signed to ensure their integrity. The keys used in the digital signature scheme are time-limited and the system time needs to be configured properly for those keys to be added to the system's keyring.

Resolution

Restart the installation and configure the system's date and time during "Preparation"/"Time Zone".

Note that the date notation format used is DD/MM/YYYY, not MM/DD/YYYY as is common in the USA.

Additional Information

Related reading

The OpenSUSE SDB articles YOU Reports Problems Verifying Patch Signatures and YOU or RPM Report Problems Verifying Package Signatures discuss related issues (mostly in the context of older releases of SUSE Linux products) and provide additional background information.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:3257992
  • Creation Date:23-FEB-07
  • Modified Date:27-APR-12
    • SUSESUSE Linux Enterprise Desktop
      SUSE Linux Enterprise Server

Did this document solve your problem? Provide Feedback

< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center