Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions cf-agent/verify_packages.c
Original file line number Diff line number Diff line change
Expand Up @@ -2204,9 +2204,9 @@ static bool WillSchedulePackageOperation(EvalContext *ctx, const Attributes *a,
break;

default:
if (!matches) // why do we schedule a 'not matched' operation?
if (!matches)
Copy link
Contributor Author

@craigcomstock craigcomstock Dec 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if the package is a meta package? "yum install snmpd" would install net-snmpd so in that case this change would block an "snmpd" package_method promiser and I think that is OK. If we really wanted to we could amend the package_list_command to include the meta package names?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem here might be that we only don't want to schedule the operation if it is an Add. If the operation is a Verify we want to let it through to SchedulePackageOp().

{
return true;
Log(LOG_LEVEL_INFO, "Package '%s' is not an available package.", pp->promiser);
}
else if (!installed) // matches and not installed
{
Expand Down
Loading