Knowledge Partner
Knowledge Partner

Re: OES2018 yast2-oes-wagon

dchunt;2493127 wrote:
Thanks, Kevin. So the obvious place to change the font, the 'Font' option that is right above the composition window is useless, huh? Why is it there then?? Just sayin

Dan


Hi Dan,

You selected the Courier New font, a fixed font, and that is what you got. I also suspect that without the CODE tags that the alignment is not preserved even though you have used a fixed font due to the way HTML deals with blanks.

Another thing to consider is how text is aligned: if tab characters are used the alignment may not be preserved but that is just speculation.

When I view your post from my NNTP news reader, I see that the alignment is preserved but the lines do wrap as you can see here:

Name                                                   | Enabled | GPGCheck | Refresh
--------------------------------------------------------+---------+-----------+--------
OES2018-2018-0 | No | ----
| ----
OES2018-Pool | Yes | (r )
Yes | Yes
OES2018-SLE-Manager-Tools-12-SP2-Debuginfo-Pool | No | ----
| ----
OES2018-SLE-Manager-Tools-12-SP2-Debuginfo-Updates | No | ----
| ----
OES2018-SLE-Manager-Tools-12-SP2-Pool | No | ----
| ----
OES2018-SLE-Manager-Tools-12-SP2-Updates | No | ----
| ----
OES2018-SLE-Module-Containers-12-SP2-Debuginfo-Pool | No | ----
| ----
OES2018-SLE-Module-Containers-12-SP2-Debuginfo-Updates | No | ----
| ----


The best way to display text copied from a terminal window is with CODE tags: they will force a fixed font, preserve alignment, and prevent line wrapping.

Why don't you re-post the same list of repositories, using CODE tags, to make it more readable?
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
dchunt Absent Member.
Absent Member.

Re: OES2018 yast2-oes-wagon

OK, here it is with the code tags:

| Name | Enabled | GPG Check | Refresh
+--------------------------------------------------------+---------+-----------+--------
| OES2018-2018-0 | No | ---- | ----
| OES2018-Pool | Yes | (r ) Yes | Yes
| OES2018-SLE-Manager-Tools-12-SP2-Debuginfo-Pool | No | ---- | ----
| OES2018-SLE-Manager-Tools-12-SP2-Debuginfo-Updates | No | ---- | ----
| OES2018-SLE-Manager-Tools-12-SP2-Pool | No | ---- | ----
| OES2018-SLE-Manager-Tools-12-SP2-Updates | No | ---- | ----
| OES2018-SLE-Module-Containers-12-SP2-Debuginfo-Pool | No | ---- | ----
| OES2018-SLE-Module-Containers-12-SP2-Debuginfo-Updates | No | ---- | ----
| OES2018-SLE-Module-Containers-12-SP2-Pool | Yes | (r ) Yes | Yes
| OES2018-SLE-Module-Containers-12-SP2-Updates | Yes | (r ) Yes | Yes
| OES2018-SLE-Modules-Web-Scripting-12-SP2-Pool | No | ---- | ----
| OES2018-SLE-Modules-Web-Scripting-12-SP2-Updates | No | ---- | ----
| OES2018-SLE-SDK-12-SP2-Debuginfo-Pool | No | ---- | ----
| OES2018-SLE-SDK-12-SP2-Debuginfo-Updates | No | ---- | ----
| OES2018-SLE-SDK-12-SP2-Pool | No | ---- | ----
| OES2018-SLE-SDK-12-SP2-Updates | No | ---- | ----
| OES2018-SLES12-SP2-Debuginfo-Pool | No | ---- | ----
| OES2018-SLES12-SP2-Debuginfo-Updates | No | ---- | ----
| OES2018-SLES12-SP2-Pool | Yes | (r ) Yes | Yes
| OES2018-SLES12-SP2-Updates | Yes | (r ) Yes | Yes
| OES2018-Updates | Yes | (r ) Yes | Yes


Same questions - should all of the repositories be enabled?

Also, what does the 'GPG Check' column mean and the 'Refresh' column mean?

Thanks,

Dan
0 Likes
Knowledge Partner
Knowledge Partner

Re: OES2018 yast2-oes-wagon

dchunt;2493133 wrote:

Same questions - should all of the repositories be enabled?

Also, what does the 'GPG Check' column mean and the 'Refresh' column mean?

Thanks,

Dan


Wow, what a difference!

The repositories contain packages needed for your system.

  • The pool repositories contain the packages as provided with the product when it was released.
  • The updates repositories contain new packages that have been added since the initial release.

Add-on products and and some optional components have their own repositories. If you have any of these installed on your system, their repositories have to be installed and enabled. See the OPEN ENTERPRISE SERVER 2018 DOCUMENTATION Updating the Server for information about which repositories are needed.

GPG Check
From the SUSE documentation:
By default, digests and signatures of packages from repositories provided by SUSE are checked to ensure their integrity and origin. This GPG check is enabled in the repository configuration file on the server that provides the repository.


Refresh
A Yes in the Refresh column means that the repository can be refreshed. When you refresh a repository it is updated with packages having all the latest available changes.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
dchunt Absent Member.
Absent Member.

Re: OES2018 yast2-oes-wagon

Thanks for the info, Kevin. It looks like I have the correct repositories updated. So I have 3 OES 2018 servers. Two of them had the problem that I detailed in this thread. I just tried to do updates on the third and get a conflict between two kernel packages. All of these are pretty plain servers. I'll start another thread for that.

Dan
0 Likes
Knowledge Partner
Knowledge Partner

Re: OES2018 yast2-oes-wagon

KBOYLE Wrote in message:

> The repositories contain packages needed for your system.
>
> - The -pool -repositories contain the packages as provided with the
> product when it was released.
> - The -updates -repositories contain new packages that have been added
> since the initial release.


And the repos with debuginfo in their name contain debug packages
which shouldn't normally be in play so all those repos are
disabled by default and should be left that way.

HTH.
--
Simon Flood
Micro Focus Knowledge Partner


----Android NewsGroup Reader----
http://usenet.sinaapp.com/
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.