Hello there. So, we have been doing a lot with OpenPKG and almost our entire environment is now converted to using OpenPKG as our core software. While doing this we have come across several issues or bumps in the road as it were. One of these has to do with openpkg build functionality. I was curious why openpkg build seems to be doing an 'rpm -Uhv --force' on each individual rpm, instead of all of the rpm such as if you installed them doing 'openpkg rpm -Uhv *.rpm'?
The problem we are seeing is that when we are installing or updating openpkg rpms on our servers, which pulls from rebuild binary rpms that we have in a custom repository, they often have conflicts that prevent them from being installed at all. If instead the openpkg build were to do one openpkg rpm -Uhv on all of the rpms that it identifies it needs to update then these conflicts wouldn't happen. This is because rpm sees the dependencies exist on the same rpm -Uhv line and recognizes this, thus it doesn't error. Whereas when it does a --force for each individual rpm, it doesn't take note that the dependencies are actually satisfied and therefore it fails. This could be solved one of two ways as I can currently determine (I'm sure there are many other ways to solve it as well though). The openpkg build could have a --nodeps in addition to the --force for each individual rpm -Uhv command it executes. The other thing I was thinking is after the openpkg build does it's checking on build options and such to verify diffs between installed and newly indexed binaries, it could just do one openpkg rpm -Uhv --force *.rpm for all the rpms it sees that needs to be updated. Anyway, I hope this makes sense. If not let me know and I will try to show some more examples of scripts and work we have done to set everything up. Thanks. -- David M. Fetter - UNIX Systems Administrator Portland State University - www.oit.pdx.edu
signature.asc
Description: This is a digitally signed message part
