Skip to content
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

chore(rocky): set Rocky Linux 9 EOL #1495

Merged
merged 1 commit into from
Jul 26, 2022
Merged

Conversation

MaineK00n
Copy link
Collaborator

@MaineK00n MaineK00n commented Jul 19, 2022

What did you implement:

Rocky Linux 9.0 is now GA and EOL is set.
https://rockylinux.org/news/rocky-linux-9-0-ga-release/

Type of change

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update

How Has This Been Tested?

before

$ vuls scan
[Jul 19 10:00:41]  INFO [localhost] vuls-v0.19.8-build-20220719_095936_d1a617c
[Jul 19 10:00:41]  INFO [localhost] Start scanning
[Jul 19 10:00:41]  INFO [localhost] config: /home/mainek00n/github/github.com/MaineK00n/vuls/config.toml
[Jul 19 10:00:41]  INFO [localhost] Validating config...
[Jul 19 10:00:41]  INFO [localhost] Detecting Server/Container OS... 
[Jul 19 10:00:41]  INFO [localhost] Detecting OS of servers... 
[Jul 19 10:00:42]  INFO [localhost] (1/1) Detected: vuls-target: rocky 9.0
[Jul 19 10:00:42]  INFO [localhost] Detecting OS of containers... 
[Jul 19 10:00:42]  INFO [localhost] Checking Scan Modes... 
[Jul 19 10:00:42]  INFO [localhost] Detecting Platforms... 
[Jul 19 10:00:43]  INFO [localhost] (1/1) vuls-target is running on other
[Jul 19 10:00:43]  INFO [vuls-target] Scanning OS pkg in fast mode
[Jul 19 10:00:47]  WARN [localhost] Some warnings occurred during scanning on vuls-target. Please fix the warnings to get a useful information. Execute configtest subcommand before scanning to know the cause of the warnings. warnings: [Failed to check EOL. Register the issue to https://github.com/future-architect/vuls/issues with the information in `Family: rocky Release: 9.0`]


Scan Summary
================
vuls-target	rocky9.0	175 installed, 0 updatable

Warning: [Failed to check EOL. Register the issue to https://github.com/future-architect/vuls/issues with the information in `Family: rocky Release: 9.0`]



To view the detail, vuls tui is useful.
To send a report, run vuls report -h.

after

$ vuls scan
[Jul 19 10:08:19]  INFO [localhost] vuls-v0.19.8-build-20220719_100638_a7879f33
[Jul 19 10:08:19]  INFO [localhost] Start scanning
[Jul 19 10:08:19]  INFO [localhost] config: /home/mainek00n/github/github.com/MaineK00n/vuls/config.toml
[Jul 19 10:08:19]  INFO [localhost] Validating config...
[Jul 19 10:08:19]  INFO [localhost] Detecting Server/Container OS... 
[Jul 19 10:08:19]  INFO [localhost] Detecting OS of servers... 
[Jul 19 10:08:20]  INFO [localhost] (1/1) Detected: vuls-target: rocky 9.0
[Jul 19 10:08:20]  INFO [localhost] Detecting OS of containers... 
[Jul 19 10:08:20]  INFO [localhost] Checking Scan Modes... 
[Jul 19 10:08:20]  INFO [localhost] Detecting Platforms... 
[Jul 19 10:08:21]  INFO [localhost] (1/1) vuls-target is running on other
[Jul 19 10:08:21]  INFO [vuls-target] Scanning OS pkg in fast mode


Scan Summary
================
vuls-target	rocky9.0	175 installed, 0 updatable





To view the detail, vuls tui is useful.
To send a report, run vuls report -h.

Checklist:

You don't have to satisfy all of the following.

  • Write tests
  • Write documentation
  • Check that there aren't other open pull requests for the same issue/feature
  • Format your source code by make fmt
  • Pass the test by make test
  • Provide verification config / commands
  • Enable "Allow edits from maintainers" for this PR
  • Update the messages below

Is this ready for review?: YES

Reference

@MaineK00n MaineK00n self-assigned this Jul 19, 2022
@MaineK00n MaineK00n marked this pull request as ready for review July 19, 2022 01:22
@MaineK00n MaineK00n merged commit 2f3b8bf into master Jul 26, 2022
@MaineK00n MaineK00n deleted the MaineK00n/set-rocky9-eol branch July 26, 2022 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant