Attachment 601742 Details for Bug 842827 – Screen capture showing custom repo creation

Screen capture showing custom repo creation

custom_repo_creation.txt (text/plain), 2.63 KB, created by James Slagle on 2012-08-01 12:57:55 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: James Slagle

Created: 2012-08-01 12:57:55 UTC

Size: 2.63 KB

patch

obsolete

>------------------------------------------------------------------------------
>             -= Red Hat Update Infrastructure Management Tool =-
>
>
>-= Repository Management =-
>
>   l   list repositories currently managed by the RHUI
>   i   display detailed information on a repository
>   a   add a new Red Hat content repository
>   c   create a new custom repository
>   d   delete a repository from the RHUI
>   u   upload content to a custom repository
>   p   list packages in a repository
>
>                                                         Connected: teletran-1
>------------------------------------------------------------------------------
>rhui (repo) => c
>
>Unique ID for the custom repository (alphanumerics, _, and - only):
>custom_repo_1
>
>Display name for the custom repository [custom_repo_1]:
>Custom Repository 1
>
>Path at which the repository will be served [custom_repo_1]:
>/custom/i386
>
>Algorithm to use when calculating the checksum values for repository metadata:
>* Select "sha256" for RHEL6:
>* Select "sha1" for either RHEL5 or RHEL6:
>
>  1  - sha256
>  2  - sha1
>Enter value (1-2) or 'b' to abort: 1
>
>Should the repository require an entitlement certificate to access? (y/n)
>y
>
>Based on the repository's relative path, the suggested entitlement path is:
>  /custom/$basearch
>
>The following repositories have the same entitlement path as suggested:
>  Custom Repository 2
>
>Path that should be used when granting an entitlement for this repository. This
>may use yum variable substitutions (e.g. $basearch) to group this together with
>other repositories that share the entitlement [/custom/$basearch]:
>
>
>Should the repository require clients to perform a GPG check and
>verify packages are signed by a GPG key? (y/n)
>y
>
>Will the repository be used to host any Red Hat GPG signed content? (y/n)
>y
>
>Will the repository be used to host any custom GPG signed content? (y/n)
>y
>
>Enter the absolute path to the public key of the GPG keypair:
>/tmp/rhuitest1.gpg
>
>Would you like to enter another public key? (y/n)
>y
>
>Enter the absolute path to the public key of the GPG keypair:
>/tmp/rhuitest2.gpg
>
>Would you like to enter another public key? (y/n)
>n
>
>The following repository will be created:
>  ID:              custom_repo_1
>  Name:            Custom Repository 1
>  Path:            /custom/i386
>  Entitlement:     /custom/$basearch
>  GPG Check        Yes
>  Custom GPG Keys: '/tmp/rhuitest1.gpg', '/tmp/rhuitest2.gpg'
>  Red Hat GPG Key: Yes
>Proceed? (y/n) y
>
>Successfully created repository Custom Repository 1
>
>------------------------------------------------------------------------------
>rhui (repo) =>

Actions: View

Attachments on bug 842827: 600071 | 601741 | 601742 | 602745