Skip to content

PMM-15015 Remove conflicting package declaration in pmm-client#5296

Open
ademidoff wants to merge 1 commit intov3from
PMM-15015-fix-the-client-package-conflict-section
Open

PMM-15015 Remove conflicting package declaration in pmm-client#5296
ademidoff wants to merge 1 commit intov3from
PMM-15015-fix-the-client-package-conflict-section

Conversation

@ademidoff
Copy link
Copy Markdown
Member

@ademidoff ademidoff commented Apr 27, 2026

PMM-15015

Ref: reported on the forum - https://forums.percona.com/t/pmm-client-v3-7-0-conflicting-with-itself/40715.

Link to the Feature Build: SUBMODULES-4326

This pull request makes a small change to the pmm-client.spec file, removing the Conflicts: pmm-client line. This simplifies the package specification and may help avoid unnecessary package conflict errors during installation.

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 27, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 42.13%. Comparing base (e21a678) to head (0849efc).
⚠️ Report is 1 commits behind head on v3.

Additional details and impacted files
@@            Coverage Diff             @@
##               v3    #5296      +/-   ##
==========================================
+ Coverage   42.10%   42.13%   +0.02%     
==========================================
  Files         410      410              
  Lines       41992    41992              
==========================================
+ Hits        17682    17694      +12     
+ Misses      22525    22515      -10     
+ Partials     1785     1783       -2     
Flag Coverage Δ
admin 34.89% <ø> (ø)
agent 49.24% <ø> (+0.11%) ⬆️
managed 40.62% <ø> (ø)
vmproxy 72.09% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ademidoff ademidoff marked this pull request as ready for review April 27, 2026 10:54
@ademidoff ademidoff requested a review from a team as a code owner April 27, 2026 10:54
@ademidoff ademidoff requested review from JiriCtvrtka and maxkondr and removed request for a team April 27, 2026 10:54
Requires(postun): systemd

AutoReq: no
Conflicts: pmm-client
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

It should contain version match <3.0.0

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This line was removed. What are you referring to?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I suggest not removing it but just add Conflicts: pmm-client < 3.0.0

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

That's exactly what we want to avoid. We actually want any newer version of the package called pmm-client, which is being installed, to replace any previous version, and not to conflict with it.

Unless I'm unaware of other benefits this may bring.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is exactly RPM pattern that is used for the behavior you want. Yes it will work with the only Obsoletes but it will fail in case enduser will execute rpm -i pmm-client.... So that is why Obsoletes and Conflicts are used together.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Hm, I don't really understand why the user can't install PMM Client by running rpm -i pmm-client.

OK, thank you, we will QA this solution anyway.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

user can download package from repo or can copy it to a server from let's say USB drive as there are a lot of users that doesn't use repo to install packages.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the RPM packaging for PMM Client by removing a self-referential Conflicts: pmm-client declaration from the spec file, addressing reported installation/upgrade conflicts (PMM-15015).

Changes:

  • Removed Conflicts: pmm-client from the pmm-client RPM spec to prevent erroneous package conflict behavior during install/upgrade.

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.

3 participants