Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1959022 - libdnf advisory APIs for context do not expose update suggestion (reboot, relogin)
Summary: libdnf advisory APIs for context do not expose update suggestion (reboot, rel...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: libdnf
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: dnf-community
TreeView+ depends on / blocked
 
Reported: 2021-05-10 15:12 UTC by Neal Gompa
Modified: 2021-05-17 12:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 435574 0 NOR UNCONFIRMED Unattended updates should only be used for packages that actually require a reboot 2021-05-10 15:12:56 UTC

Description Neal Gompa 2021-05-10 15:12:56 UTC
Description of problem:
libdnf's advisory API for the context API lacks a method that returns the suggestion for whether an update advisory suggests a reboot or relogin. This makes it impossible for PackageKit to give software centers the option to be smarter about triggering offline updates.

Version-Release number of selected component (if applicable):
0.62.0-1.fc34

Additional info:
See the linked KDE bug for details.

Comment 1 Neal Gompa 2021-05-10 16:21:03 UTC
It seems that reboot_suggested and relogin_suggested flags are per-package. Does that mean we need to extend the DnfAdvisoryPkg object to contain that data?


Note You need to log in before you can comment on or make changes to this bug.