-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
whois package on FCOS #432
Comments
@bgilbert it looks like you added |
Clarification: All that I wanted was |
In CoreOS (original), we had nss-lookup.target loaded active active Host and Network Name Lookups In FCOS, we have: nss-user-lookup.target loaded active active User and Group Name Lookups |
right, you were just choosing the wrong package. |
$ sudo rpm-ostree install whois --allow-inactive
Checking out tree 3477082... done
Enabled rpm-md repositories: updates fedora
rpm-md repo 'updates' (cached); generated: 2020-03-22T02:55:39Z
rpm-md repo 'fedora' (cached); generated: 2019-10-23T22:52:47Z
Importing rpm-md... done
⠁
Forbidden base package replacements:
whois-nls 5.5.5-1.fc31 -> 5.5.6-1.fc31 (updates)
This likely means that some of your layered packages have requirements on newer or older versions of some base packages. Doing `rpm-ostree cleanup -m` andResolving dependencies... done
error: Some base packages would be replaced BTW, |
More issues: $ sudo rpm-ostree upgrade whois-nls
⠙ Receiving metadata objects: 0/(estimating) -/s 0 bytes...
Receiving metadata objects: 0/(estimating) -/s 0 bytes... done
Checking out tree 3477082... done
Enabled rpm-md repositories: updates fedora
Updating metadata for 'updates'... done
rpm-md repo 'updates'; generated: 2020-03-22T02:55:39Z
Updating metadata for 'fedora'... done
rpm-md repo 'fedora'; generated: 2019-10-23T22:52:47Z
⠒ Importing rpm-md 52% [██████████░░░░░░░░░░] (6s) |
It is excruciating to upgrade a package and still does not seem to work :-( Without upgrading this package, I cannot install package # rpm-ostree upgrade --install=whois-nls-5.5.6-1.fc31
1 metadata, 0 content objects fetched; 569 B transferred in 1 seconds
Checking out tree 3477082... done
Enabled rpm-md repositories: updates fedora
Updating metadata for 'updates'... done
rpm-md repo 'updates'; generated: 2020-03-22T02:55:39Z
Updating metadata for 'fedora'... done
rpm-md repo 'fedora'; generated: 2019-10-23T22:52:47Z
⠒ Importing rpm-md 52% [██████████░░░░░░░░░░] (7s) This is a blocker for me and I am stuck. I have been blowing AWS instances as |
Right. You are hitting #400. The latest |
I don't know why rpm-ostree operations are getting stuck. Is this on the |
It is worth pointing out that the way rpm-ostree works you don't have to worry about a corrupted |
I am actually using t3.micro instances with EBS storage.
If 'rpm-ostree' takes so much time, a notification of some kind is required to communicate to the user if it is doing something or struck.
Any idea when #400 will be fixed and released?
Thanks
/Shivaram
… On Mar 23, 2020, at 6:15 AM, Dusty Mabe ***@***.***> wrote:
This is a blocker for me and I am stuck. I have been blowing AWS instances as rpm-ostree does not not even time out and I don't want to screw around trying to debug corrupted rpm database.
It is worth pointing out that the way rpm-ostree works you don't have to worry about a corrupted rpm database. You can cancel an rpm-ostree transaction at any point (even losing power) and the machine should be fine.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@dustymabe As a workaround, is it possible to provide a This way we can make some progress |
Ok. Here is a workaround: Download Go binary for As |
@dustymabe It's possible that F30 was pulling in whois and F31 doesn't. I only readded whois-nls because I didn't want to drop NLS support as a side-effect of disabling Recommends. |
We discussed this in the community meeting today. Chatting with @shivarammysore in the meeting it seems his use case is to do "schema verification of JSON/YAML" using
That being said.. I did just add a PR (coreos/fedora-coreos-config#320) to drop the subpackage |
coreos/fedora-coreos-config#320 merged. I'll go ahead and close. |
The fix for this landed upstream. It is now pending a testing stream release. |
The fix for this went into testing stream release |
The fix for this went into stable stream release |
I have some schema loaders in my code which needs
whois
. I can't load that package asWhat is the impact of installing this package with
--allow-inactive
option? Will I still be able to usewhois
The text was updated successfully, but these errors were encountered: