** Description changed:
tracking bug
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245
[ Impact ]
Even if the krb5 ticket is discoverable, the discovery fails (but
actually succeeded) So we cannot retrieve the policies or do any action
with the controller.
[ Test
** Description changed:
tracking bug
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245
[ Impact ]
Even if the krb5 ticket is discoverable, the discovery fails (but
actually succeeded) So we cannot retrieve the policies or do any action
with the controller.
[ Test
Public bug reported:
[placeholder for
https://github.com/ubuntu/adsys/pull/1065/commits/3d71626665b1560de9159b3b12c13bd5dc3d091a]
** Affects: adsys (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
This should fix the issues on Noble (24.04)
** Patch added: "Noble (24.04) diff"
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2079824/+attachment/5813940/+files/sru_2404.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch removed: "diff from 0.14.1 to 0.14.2 on 24.04"
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2079824/+attachment/5813928/+files/sru_2404.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
This should fix the issues on Jammy (22.04)
** Patch added: "Jammy 22.04 diff"
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2079824/+attachment/5813939/+files/sru_2204.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Patch added: "diff from 0.14.1 to 0.14.2"
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2079824/+attachment/5813928/+files/sru_2404.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2079
** Description changed:
+ [SRU]
+
+ [Impact]
+
Adsys has a fixed timeout for listing the GPOs. This can cause issues on
slower machines or in cases with many policies to be listed. Adding a
configurable timeout prevents the daemon from timing out the listing
- process with no necessity.
+
** Description changed:
+ [SRU]
+
+ [Impact]
+
+ adsys does not have support for some USB settings in DCONF
+
+ [Test Plan]
+
+ 1. Configure the administrative templates in the AD server:
+ - The templates can be generated through adsys with `adsysctl policy admx
all`
+
+ 2. Configure a GP
** Description changed:
+ [SRU]
+
+ [Impact]
+
+ adsys is only able to parse .pol files exactly named "Registry.pol".
+ With this, it is now able to ignore casing on the registry file and
+ behave more similarly to what Windows machines do (as they ignore
+ casing).
+
+ [Test Plan]
+
+ 1. Conf
** Also affects: adsys (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Summary changed:
- Add support for DCONF usb settings
+ [SRU] Add support for DCONF usb settings
** Description changed:
- [SRU]
-
[Impact]
adsys does not have support for some USB settings in DCONF
[Test Plan]
1. Configure the administrative templates in the AD server:
** Summary changed:
- Adsys can't properly resolve registry.pol vs Regristry.pol
+ [SRU] Adsys can't properly resolve registry.pol vs Regristry.pol
** Description changed:
- [SRU]
-
[Impact]
adsys is only able to parse .pol files exactly named "Registry.pol".
With this, it is now able
** Summary changed:
- Timeout for listing GPOs is not enough in some cases
+ [SRU] Timeout for listing GPOs is not enough in some cases
** Description changed:
- [SRU]
-
[Impact]
Adsys has a fixed timeout for listing the GPOs. This can cause issues on
slower machines or in cases with m
** Description changed:
[SRU]
[Impact]
adsys is only able to parse .pol files exactly named "Registry.pol".
With this, it is now able to ignore casing on the registry file and
behave more similarly to what Windows machines do (as they ignore
casing).
[Test Plan]
1. Conf
** Description changed:
[SRU]
[Impact]
adsys does not have support for some USB settings in DCONF
[Test Plan]
1. Configure the administrative templates in the AD server:
- - The templates can be generated through adsys with `adsysctl policy admx
all`
+ - The templates ca
** Description changed:
[SRU]
[Impact]
Adsys has a fixed timeout for listing the GPOs. This can cause issues on
slower machines or in cases with many policies to be listed. Adding a
configurable timeout prevents the daemon from timing out the listing
process during its execution.
The test plan was executed for Noble (24.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.2~24.04
Candidate: 0.14.2~24.04
Version table:
*** 0.14.2~24.04 500
500
I'm sorry for not commenting about the executed test plan. Let's fix
this!
The test plan was executed for Jammy (22.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.2~22.04
The test plan was executed for Noble (24.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.2~24.04
Candidate: 0.14.2~24.04
Version table:
*** 0.14.2~24.04 500
500
I'm sorry for not commenting about the executed test plan. Let's fix
this!
The test plan was executed and I confirm that it was successful. The package
version used for the tests is the one proposed, as can be seen by the output of
apt-cache policy:
adsys:
Installed: 0.14.2~22.04
Candidate:
The test plan was executed for Noble (24.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.2~24.04
Candidate: 0.14.2~24.04
Version table:
*** 0.14.2~24.04 500
500
I'm sorry for not commenting about the executed test plan. Let's fix
this!
The test plan was executed for Jammy (22.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.2~22.04
The test plan was executed for Noble (24.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.2~24.04
Candidate: 0.14.2~24.04
Version table:
*** 0.14.2~24.04 500
500
** Tags removed: verification-needed-jammy verification-needed-noble
** Tags added: verification-done-jammy verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078246
Title:
Ignor
I'm sorry for not commenting about the executed test plan. Let's fix
this!
The test plan was executed for Jammy (22.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.2~22.04
** Tags removed: verification-needed verification-needed-jammy
verification-needed-noble
** Tags added: verification-done verification-done-jammy verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Tags removed: verification-needed verification-needed-jammy
verification-needed-noble
** Tags added: verification-done verification-done-jammy verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Tags removed: verification-needed verification-needed-jammy
verification-needed-noble
** Tags added: verification-done verification-done-jammy verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Tags removed: verification-needed verification-needed-jammy
verification-needed-noble
** Tags added: verification-done verification-done-jammy verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Also affects: adsys (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Also affects: adsys (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Public bug reported:
SRU placeholder for fix: https://github.com/ubuntu/adsys/pull/1097
** Affects: adsys (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Public bug reported:
SRU placeholder for fix: https://github.com/ubuntu/adsys/pull/1096
** Affects: adsys (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Description changed:
+ Adsys has a fixed timeout for listing the GPOs. This can cause issues on
+ slower machines or in cases with many policies to be listed. Adding a
+ configurable timeout prevents the daemon from timing out the listing
+ process with no necessity.
+
SRU placeholder for fi
** Description changed:
+ Adds support for some DCONF usb related settings: Allows for usbguard
+ configuration and mounting removable media as read-only.
+
SRU placeholder for fix: https://github.com/ubuntu/adsys/pull/1096
--
You received this bug notification because you are a member of Ubu
The test plan was executed for Noble (24.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.3~24.04
Candidate: 0.14.3~24.04
Version table:
*** 0.14.3~24.04 100
100
The test plan was executed for Noble (24.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.3~24.04
Candidate: 0.14.3~24.04
Version table:
*** 0.14.3~24.04 100
100
The test plan was executed for Noble (24.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.3~24.04
Candidate: 0.14.3~24.04
Version table:
*** 0.14.3~24.04 100
100
** Tags removed: verification-needed verification-needed-jammy
verification-needed-noble
** Tags added: verification-done verification-done-jammy verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
The test plan was executed for Jammy (22.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.3~22.04
Candidate: 0.14.3~22.04
Version table:
*** 0.14.3~22.04 500
500
The test plan was executed for Jammy (22.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.3~22.04
Candidate: 0.14.3~22.04
Version table:
*** 0.14.3~22.04 500
500
The test plan was executed for Jammy (22.04) and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.14.3~22.04
Candidate: 0.14.3~22.04
Version table:
*** 0.14.3~22.04 500
500
** Tags removed: verification-needed verification-needed-jammy
verification-needed-noble
** Tags added: verification-done verification-done-jammy verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Tags removed: verification-needed verification-needed-jammy
verification-needed-noble
** Tags added: verification-done verification-done-jammy verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Hey, Andreas! Thanks for the quick follow-up!
Regarding the (a) question:
Since DCONF is (in a short way) a register of key:value pairs, what
matters is how other applications interact with it. If a key is added
there but not used by any process or aplication, it does not affect the
system at all
** Summary changed:
- [SRU] Release adsys 0.16.1 to Oracular
+ [SRU] Release adsys 0.16.2
** Also affects: adsys (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: adsys (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification be
** Changed in: adsys (Ubuntu)
Status: Fix Released => In Progress
** Description changed:
[Impact]
- Adsys 0.16.1 introduces dependency bumps, and updates to the privilege
+ Adsys 0.16.2 introduces dependency bumps, and updates to the privilege
policy manager to support the newer Po
** Description changed:
[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 Oracul
** Description changed:
[Impact]
- Adsys 0.16.1 introduces dependency bumps, and (this relates to 0.16.0)
- 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 w
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
** Description changed:
[Impact]
- Adsys 0.16.2 introduces dependency bumps, and updates to the privilege
+ Adsys 0.16.3 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.
** Summary changed:
- [SRU] Release adsys 0.16.2
+ [SRU] Release adsys 0.16.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2091940
Title:
[SRU] Release adsys 0.16.3
To manage notifications about
Public bug reported:
## FFE ##
Version 0.16.3 of adsys contains bug fixes that customers requested and
are already in use through PPAs. To avoid having users rely on PPAs as
their source (and also avoid having multiple versions throughout PPAs),
we'd like to request a FFE for this release.
One o
** Description changed:
## FFE ##
Version 0.16.3 of adsys contains bug fixes that customers requested and
are already in use through PPAs. To avoid having users rely on PPAs as
their source (and also avoid having multiple versions throughout PPAs),
we'd like to request a FFE for this
Hey, Andreas! Thanks for looking into this (and sorry for the delayed
answer)!
Answering your questions:
a) It does apply to the LTS releases. However, there are no changes to
DCONF at all so, even though we could also test it in the LTS releases,
it's not necessary. The reason I included the DCO
We had introduced the "purge" stenza for adsys in a previous update, but
it had some issues managing the DCONF databases, so we decided to
disable it entirely. AFAIK, it was only available on Noble and Mantic
(we removed it before the Oracular release), so it's not present on
Jammy and Oracular.
-
> Do you have a bug about this change?
No, we didn't open any bug regarding this change. The detailed
explanation for this change can be seen in this commit message:
https://github.com/ubuntu/adsys/commit/fb9ab42e6320e3904aa229ad859d67d7aa1b12ba
> Is this change in the policy purge upon package r
The test plan was executed for Noble (24.04), and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.16.3~24.04.1
Candidate: 0.16.3~24.04.1
Version table:
*** 0.16.3~24.04.1 100
The autopkgtests failures for Jammy and Noble were due to not properly
adjusting the Go binary that should be used to run the tests. They are
now fixed with the new uploads 0.16.3~22.04.1 and 0.16.3~24.04.1, for
Jammy and Noble respectively, which are now waiting in the ~unnaproved
queue.
--
You
The test plan was executed for Oracular (24.10), and I confirm it was
successful. The package version used for the tests is the one proposed, as can
be seen by the output of apt-cache policy:
adsys:
Installed: 0.16.3~24.10
Candidate: 0.16.3~24.10
Version table:
*** 0.16.3~24.10 100
The test plan was executed for Jammy (22.04), and I confirm it was successful.
The package version used for the tests is the one proposed, as can be seen by
the output of apt-cache policy:
adsys:
Installed: 0.16.3~22.04.1
Candidate: 0.16.3~22.04.1
Version table:
*** 0.16.3~22.04.1 500
62 matches
Mail list logo
