Bug 1313931 - Package rubygem-newt is missing
Summary: Package rubygem-newt is missing
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high vote
Target Milestone: Unspecified
Assignee: Mike McCune
QA Contact: Sachin Ghai
Depends On:
Blocks: 1313857
TreeView+ depends on / blocked
Reported: 2016-03-02 16:03 UTC by Lukas Zapletal
Modified: 2019-09-26 17:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-07-27 09:04:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1500 normal SHIPPED_LIVE Red Hat Satellite 6.2 Base Libraries 2016-07-27 12:24:38 UTC

Description Lukas Zapletal 2016-03-02 16:03:48 UTC
This package disappeared from Satellite 6.2 SNAP1&2, it must be present in the Capsule repository (not Server). It is used in fdi.

Comment 3 Roman Plevka 2016-04-05 11:11:38 UTC

the package is not present in Capsule repo.
It is only present in Server repo for Snap6.1

Comment 4 Roman Plevka 2016-04-05 11:12:19 UTC
mistakenly put this bug to VERIFIED, moving to ASSIGNED

Comment 5 Roman Plevka 2016-04-11 13:15:13 UTC

the package is now available in Capsule repo:

rubygem-newt-0.9.6-2.el7sat.x86_64.rpm	2016-04-07 12:08 	19K

Comment 6 Lukas Zapletal 2016-04-13 10:32:12 UTC
For the record, we moved the package in brew from Capsule to Server repository. It was supposed to be in Server repo, my apologizes. So in the next compose the package should move there.

Comment 7 Sachin Ghai 2016-04-18 11:37:29 UTC
Yes, verified with sat6.2 beta snap8.2

Package is moved back to server repo and I can see latest version:


Comment 10 errata-xmlrpc 2016-07-27 09:04:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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