Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Confirm RPM scripts work
See original GitHub issueThe following need to work before we close the door on 2.4.0.
CentOS 6
- - Fresh Install Hazmat edit:
- - ~Update from 2.3.X~
- - ~Update from 2.1.X~
- - ~Erase RPM~
- - ~Verify
/var/run/beer-garden/bug~ - - ~Install, erase, Install~
- - ~Labeling Configuration files correctly~
CentOS 7
- - Fresh Install
- - Update from 2.3.X
- - Update from 2.1.X
- - Erase RPM
- - Verify
/var/run/beer-garden/bug - - Install, erase, Install
- - Labeling Configuration files correctly
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Selecting What to Verify, and How - Ftp
The Package Label — Verify an Installed Package Against the RPM Database ... If the package was built with a verification script, that...
Read more >Linux RPM: View Script That Run When You Install RPM Files
All rpm packages can run scripts after a package is added or removed. How do I view pre/post install and uninstall rpm file...
Read more >RPM and GPG: How to verify Linux packages before installing ...
The rpm utility uses GPG keys to sign packages and its own collection of imported public keys to verify the packages.
Read more >10.3. Writing Verification Scripts - Jeff's Home Page
Writing Verification Scripts. RPM automatically handles package verification, checking to see that the proper files are installed, and testing the files ...
Read more >Check if rpm exists in bash script silently - Stack Overflow
This way should be faster because it doesn't have to wait a -qa (query all) rpm packages installed but just queries the target...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For the labeling, I’m pretty sure this works? We’ll generate yaml files by default for the clean install case. For the upgrade case if either json or yaml files exist we’ll upgrade them in-place and they’ll remain whatever they were.
If you manually use the
generage_bartender_configentry point you can specify--configuration-fileand--configuration-type.typedefaults to yaml, but if you specify a file and the file ends in “.json” we’ll assume you want json and do that for you. If you specify a file and and type but the file doesn’t have an extension we will not append the extension.Closing this out