Public bug reported:
[Impact]
Adsys 0.16.0 introduces dependency bumps, and updates to the privilege
policy manager to support the newer Polkit versions (>= 124) and their
new syntax for defining system admins. We want to SRU this all the way
to Jammy, so we need to start at Oracular.
Since the updates mentioned only impact a policy manager which is locked
under a Pro subscription, this should have no impact on Oracular
whatsoever.
[Test Plan]
1) Configure DCONF policies in the AD controller;
2) Enroll the Ubuntu client VM on the domain;
3) Install adsys 0.16.0;
4) Ensure the client can authenticate and that the policies were applied
correctly;
[Where problems could occur]
As said before, the behavior changes were added to Pro subscription
manager, so they have no impact on an interim release and, therefore, we
don't expect a problem here.
Since the dependencies are vendored, there is no risk of incompatibility
with local packages in the Ubuntu release. Unless an internal bug within
one of them affects adsys (this would likely been spotted in CI), no
issues should occur when bumping their version also.
** Affects: adsys (Ubuntu)
Importance: Undecided
Status: New
** Affects: adsys (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2091940
Title:
[SRU] Release adsys 0.16.0 to Oracular
Status in adsys package in Ubuntu:
New
Status in adsys source package in Oracular:
New
Bug description:
[Impact]
Adsys 0.16.0 introduces dependency bumps, and updates to the privilege
policy manager to support the newer Polkit versions (>= 124) and their
new syntax for defining system admins. We want to SRU this all the way
to Jammy, so we need to start at Oracular.
Since the updates mentioned only impact a policy manager which is
locked under a Pro subscription, this should have no impact on
Oracular whatsoever.
[Test Plan]
1) Configure DCONF policies in the AD controller;
2) Enroll the Ubuntu client VM on the domain;
3) Install adsys 0.16.0;
4) Ensure the client can authenticate and that the policies were applied
correctly;
[Where problems could occur]
As said before, the behavior changes were added to Pro subscription
manager, so they have no impact on an interim release and, therefore,
we don't expect a problem here.
Since the dependencies are vendored, there is no risk of
incompatibility with local packages in the Ubuntu release. Unless an
internal bug within one of them affects adsys (this would likely been
spotted in CI), no issues should occur when bumping their version
also.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2091940/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
