[Group.of.nepali.translators] [Bug 2058133] Re: [SRU] update-manager crashes when ua security-status response is an error
This bug was fixed in the package update-manager - 1:18.04.12
---
update-manager (1:18.04.12) bionic; urgency=medium
* Replace Popen to 'ua security-status --format=json' by the Ubuntu Pro API.
The former is not stable enough and would break the program once in a
while when something unrelated to Update Manager (Livepatch, for instance)
went awry. The updates() end point from the API, on the other hand,
does not raise exceptions. LP: #2058133.
-- Nathan Pratta Teodosio Fri, 22 Mar
2024 08:42:47 +0100
** Changed in: update-manager (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: update-manager (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2058133
Title:
[SRU] update-manager crashes when ua security-status response is an
error
Status in Canonical Livepatch Client:
New
Status in ubuntu-advantage-tools package in Ubuntu:
Invalid
Status in update-manager package in Ubuntu:
Fix Released
Status in update-manager source package in Xenial:
Fix Committed
Status in update-manager source package in Bionic:
Fix Released
Status in update-manager source package in Focal:
Fix Released
Status in update-manager source package in Jammy:
Fix Released
Status in update-manager source package in Noble:
Fix Released
Bug description:
Impact
--
Update Manager fails to launch in the LTS releases if the 'ua
security-status' command fails. It tries to parse its output to
generate the list of ESM-Apps and ESM-Infra updates that would be
available if the system were attached to Ubuntu Pro.
However, if ua finds some problem with unrelated stuff, such as
Livepatch (as evidenced by the attached ubuntu-advantage.log), the
command just raises an error, crashing Update Manager.
Although Update Manager could catch the error, it would result in not
showing Ubuntu Pro updates, simply because the information is not
there.
Better would be to ditch 'ua security-status' in favor of the Ubuntu
Pro API. The updates() end point[1] will provide the information
Update Manager wants even if the Ubuntu Advantage daemon has issues
with other services such as Livepatch (as evidenced by #10), and it
does not raise exceptions.
[1] https://canonical-ubuntu-pro-client.readthedocs-
hosted.com/en/latest/references/api/#u-pro-packages-updates-v1
Test Plan
-
Attach your machine to Ubuntu Pro and make sure Livepatch is enabled
in the output of 'ua status'. Then, simulate a failing Livepatch with
--->
mv /snap/bin/canonical-livepatch /snap/bin/canonical-livepatch.bak
>/snap/bin/canonical-livepatch printf '%s\n' '#!/bin/sh' 'exit 1'
chmod +x /snap/bin/canonical-livepatch
<
Launch update-manager, it should open and not crash.
Where problems could occur
--
In the Ubuntu Pro section of the updates, in form of wrong package
data (e.g. package name, version number etc.) in the description pane
when selecting a package. The section could not show at all, or the
program could crash right away.
Original bug report
---
Below is a run in my computer. Please send a mail on what to do
fuga2:~> update-manager -c -d
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py",
line 448, in _on_finished
self._action_done(action,
File "/usr/lib/python3/dist-packages/UpdateManager/backend/__init__.py",
line 365, in _action_done
self.window_main.start_available()
File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line
241, in start_available
self.refresh_cache()
File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line
459, in refresh_cache
self._get_ua_security_status()
File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line
285, in _get_ua_security_status
s = json.load(p.stdout)
File "/usr/lib/python3.10/json/__init__.py", line 293, in load
return loads(fp.read(),
File "/usr/lib/python3.10/json/__init__.py", line 346, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.10/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.10/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
^CTraceback (most recent call last):
File "/usr/bin/update-manager", line 125, in
Gtk.main()
[Group.of.nepali.translators] [Bug 2052438] Re: Update d/control file with a dependency on google-guest-agent
This bug was fixed in the package google-compute-engine-oslogin - 20231004.00-0ubuntu1~20.04.3 --- google-compute-engine-oslogin (20231004.00-0ubuntu1~20.04.3) focal; urgency=medium * d/control: There must be a dependency on `google-guest-agent` to match the (upstream) Google managed d/control file (LP: #2052438) -- Chloé 'kajiya' Smith Tue, 06 Feb 2024 16:16:42 + ** Changed in: google-compute-engine-oslogin (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2052438 Title: Update d/control file with a dependency on google-guest-agent Status in google-compute-engine-oslogin package in Ubuntu: Fix Released Status in google-compute-engine-oslogin source package in Xenial: New Status in google-compute-engine-oslogin source package in Bionic: New Status in google-compute-engine-oslogin source package in Focal: Fix Released Status in google-compute-engine-oslogin source package in Jammy: Fix Released Status in google-compute-engine-oslogin source package in Mantic: Fix Released Bug description: [SRU] === [Impact] `google-compute-engine-oslogin` is a package provided by Google for installation within guests that run on Google Compute Engine (GCE). It is part of a collection of tools and daemons that ensure that Ubuntu images published to GCE run properly on the platform. In Google's packed upstream debian distro `d/control` files for both `google-compute-engine-oslogin` and `google-guest-agent` there is a dependency on the other. This was not reflected in the ubuntu archive. LP: #2050956 fixed `google-guest-agent`'s dependency on `google- compute-engine-oslogin`, so now it's time to do the reverse. The regression caused in `google-guest-agent` was critical enough to warrant this stand-alone update into `google-compute-engine-oslogin`, and not just wait for it to be packaged into a normal update. [Test Case] When the new version of this package is uploaded to -proposed, the following will happen: * an image based on -proposed will be built for GCE and published * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. * Each test image will be launched, and we will validate: ** the package version(s) ** that the correct ssh keys have been imported ** that the google specific services are running successfully If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [ Regression potential / Where problems could occur ] As this is just a dependency change and not a functionality change, the risk is somewhat lower. That being said: * In the edge case that a user has uninstalled/removed `google-guest-agent`, any update to install new versions of `google-compute-engine-oslogin` will force an installation of the guest-agent. But the guest-agent package is pretty fundamental to getting images working on the platform, so I don't think this is a viable set up anyways to be honest. * There is also risk we might break users who have pinned a much older version of `google-guest-agent`. However, there has been a *significant* shift in functionality between these two packages (see LP: #2050956 for details) so we might actually be saving these pinned users from a bigger issue later... [Additional Information] This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [0]. [0]: https://wiki.ubuntu.com/google-compute-engine-oslogin-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2052438/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2052438] Re: Update d/control file with a dependency on google-guest-agent
This bug was fixed in the package google-compute-engine-oslogin - 20231004.00-0ubuntu1~22.04.3 --- google-compute-engine-oslogin (20231004.00-0ubuntu1~22.04.3) jammy; urgency=medium * d/control: There must be a dependency on `google-guest-agent` to match the (upstream) Google managed d/control file (LP: #2052438) -- Chloé 'kajiya' Smith Tue, 06 Feb 2024 14:06:11 + ** Changed in: google-compute-engine-oslogin (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2052438 Title: Update d/control file with a dependency on google-guest-agent Status in google-compute-engine-oslogin package in Ubuntu: Fix Released Status in google-compute-engine-oslogin source package in Xenial: New Status in google-compute-engine-oslogin source package in Bionic: New Status in google-compute-engine-oslogin source package in Focal: Fix Committed Status in google-compute-engine-oslogin source package in Jammy: Fix Released Status in google-compute-engine-oslogin source package in Mantic: Fix Released Bug description: [SRU] === [Impact] `google-compute-engine-oslogin` is a package provided by Google for installation within guests that run on Google Compute Engine (GCE). It is part of a collection of tools and daemons that ensure that Ubuntu images published to GCE run properly on the platform. In Google's packed upstream debian distro `d/control` files for both `google-compute-engine-oslogin` and `google-guest-agent` there is a dependency on the other. This was not reflected in the ubuntu archive. LP: #2050956 fixed `google-guest-agent`'s dependency on `google- compute-engine-oslogin`, so now it's time to do the reverse. The regression caused in `google-guest-agent` was critical enough to warrant this stand-alone update into `google-compute-engine-oslogin`, and not just wait for it to be packaged into a normal update. [Test Case] When the new version of this package is uploaded to -proposed, the following will happen: * an image based on -proposed will be built for GCE and published * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. * Each test image will be launched, and we will validate: ** the package version(s) ** that the correct ssh keys have been imported ** that the google specific services are running successfully If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [ Regression potential / Where problems could occur ] As this is just a dependency change and not a functionality change, the risk is somewhat lower. That being said: * In the edge case that a user has uninstalled/removed `google-guest-agent`, any update to install new versions of `google-compute-engine-oslogin` will force an installation of the guest-agent. But the guest-agent package is pretty fundamental to getting images working on the platform, so I don't think this is a viable set up anyways to be honest. * There is also risk we might break users who have pinned a much older version of `google-guest-agent`. However, there has been a *significant* shift in functionality between these two packages (see LP: #2050956 for details) so we might actually be saving these pinned users from a bigger issue later... [Additional Information] This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [0]. [0]: https://wiki.ubuntu.com/google-compute-engine-oslogin-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2052438/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2052438] Re: Update d/control file with a dependency on google-guest-agent
This bug was fixed in the package google-compute-engine-oslogin - 20231004.00-0ubuntu1~23.10.3 --- google-compute-engine-oslogin (20231004.00-0ubuntu1~23.10.3) mantic; urgency=medium * d/control: There must be a dependency on `google-guest-agent` to match the (upstream) Google managed d/control file (LP: #2052438) -- Chloé 'kajiya' Smith Tue, 06 Feb 2024 13:18:51 + ** Changed in: google-compute-engine-oslogin (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2052438 Title: Update d/control file with a dependency on google-guest-agent Status in google-compute-engine-oslogin package in Ubuntu: Fix Released Status in google-compute-engine-oslogin source package in Xenial: New Status in google-compute-engine-oslogin source package in Bionic: New Status in google-compute-engine-oslogin source package in Focal: Fix Committed Status in google-compute-engine-oslogin source package in Jammy: Fix Released Status in google-compute-engine-oslogin source package in Mantic: Fix Released Bug description: [SRU] === [Impact] `google-compute-engine-oslogin` is a package provided by Google for installation within guests that run on Google Compute Engine (GCE). It is part of a collection of tools and daemons that ensure that Ubuntu images published to GCE run properly on the platform. In Google's packed upstream debian distro `d/control` files for both `google-compute-engine-oslogin` and `google-guest-agent` there is a dependency on the other. This was not reflected in the ubuntu archive. LP: #2050956 fixed `google-guest-agent`'s dependency on `google- compute-engine-oslogin`, so now it's time to do the reverse. The regression caused in `google-guest-agent` was critical enough to warrant this stand-alone update into `google-compute-engine-oslogin`, and not just wait for it to be packaged into a normal update. [Test Case] When the new version of this package is uploaded to -proposed, the following will happen: * an image based on -proposed will be built for GCE and published * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. * Each test image will be launched, and we will validate: ** the package version(s) ** that the correct ssh keys have been imported ** that the google specific services are running successfully If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [ Regression potential / Where problems could occur ] As this is just a dependency change and not a functionality change, the risk is somewhat lower. That being said: * In the edge case that a user has uninstalled/removed `google-guest-agent`, any update to install new versions of `google-compute-engine-oslogin` will force an installation of the guest-agent. But the guest-agent package is pretty fundamental to getting images working on the platform, so I don't think this is a viable set up anyways to be honest. * There is also risk we might break users who have pinned a much older version of `google-guest-agent`. However, there has been a *significant* shift in functionality between these two packages (see LP: #2050956 for details) so we might actually be saving these pinned users from a bigger issue later... [Additional Information] This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [0]. [0]: https://wiki.ubuntu.com/google-compute-engine-oslogin-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2052438/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2059143] Re: Remove getabis scripts
This bug was fixed in the package linux - 5.15.0-105.115 --- linux (5.15.0-105.115) jammy; urgency=medium * jammy/linux: 5.15.0-105.115 -proposed tracker (LP: #2061372) * Jammy update: v5.15.149 upstream stable release (LP: #2059014) // CIFS stopped working/is unstable with kernel update to 5.15.0-102.112 (LP: #2060780) - smb3: Replace smb2pdu 1-element arrays with flex-arrays linux (5.15.0-103.113) jammy; urgency=medium * jammy/linux: 5.15.0-103.113 -proposed tracker (LP: #2059683) * Packaging resync (LP: #1786013) - [Packaging] drop getabis data * Remove getabis scripts (LP: #2059143) - [Packaging] Remove getabis * CVE-2023-24023 - Bluetooth: Add more enc key size check * CVE-2023-52600 - jfs: fix uaf in jfs_evict_inode * Jammy update: v5.15.149 upstream stable release (LP: #2059014) // CVE-2023-52603 - UBSAN: array-index-out-of-bounds in dtSplitRoot * CVE-2024-26581 - netfilter: nft_set_rbtree: skip end interval element from gc -- Roxana Nicolescu Mon, 15 Apr 2024 10:38:15 +0200 ** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Mantic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26591 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2059143] Re: Remove getabis scripts
This bug was fixed in the package linux - 5.4.0-177.197 --- linux (5.4.0-177.197) focal; urgency=medium * focal/linux: 5.4.0-177.197 -proposed tracker (LP: #2059633) * Packaging resync (LP: #1786013) - [Packaging] drop getabis data * Remove getabis scripts (LP: #2059143) - [Packaging] Remove getabis * CVE-2023-24023 - Bluetooth: Add more enc key size check * CVE-2023-52600 - jfs: fix uaf in jfs_evict_inode * Focal update: v5.4.269 upstream stable release (LP: #2058948) // CVE-2023-52603 - UBSAN: array-index-out-of-bounds in dtSplitRoot * CVE-2024-26581 - netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure - netfilter: nft_set_rbtree: skip end interval element from gc * CVE-2024-26589 - bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS -- Manuel Diewald Thu, 28 Mar 2024 19:08:48 +0100 ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-24023 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-52600 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-52603 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26581 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-26589 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2057937] Re: apt-news.service reporting errors after ubuntu-pro-client install
This bug was fixed in the package ubuntu-advantage-tools - 31.2.2~20.04 --- ubuntu-advantage-tools (31.2.2~20.04) focal; urgency=medium * version.py: match version from d/changelog (LP: #2058934) ubuntu-advantage-tools (31.2.1~20.04) focal; urgency=medium * apt-news.service: ignore apparmor errors when starting (LP: #2057937) -- Andreas Hasenack Mon, 25 Mar 2024 11:49:51 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2057937 Title: apt-news.service reporting errors after ubuntu-pro-client install Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [ Impact ] src:ubuntu-advantage-tools version 31 introduced[1] an apparmor profile to the apt-news service. It's known that some ubuntu systems do not have apparmor enabled, and this was considered. The systemd.exec(5) manpage states that the AppArmorProfile setting has no effect if apparmor is disabled[2]. This was tested and verified. Turns out, however, that apparmor can be enabled on a system, but without the apparmor package installed. When this package is not installed, no profiles are loaded. Crucially, the ubuntu_pro_apt_news profile, used by apt-news.service, is not loaded. This situation is different than "apparmor is disabled", and systemd will try to launch apt-news confined by ubuntu_pro_apt_news. But since that profile is not loaded into the kernel, the service will fail. apt-news.service is called as an apt update hook, but its failure does not fail apt, since it's guarded[3] by "|| true", i.e., failures in the hook are ignored. The only impact is that apt news won't be fetched. [ Test Plan ] The test plan will be in two parts. One to confirm the apt-news service won't fail to start if the apparmor profile is not available (it's what triggered this bug). The second part is to confirm that in the "good case", with apparmor available on the system, the confinement is still applied. a) To reproduce the problem, launch an ubuntu lxd container, or a VM, and: # install ubuntu-advantage-tools 31 or later. It's in updates right now, so just make sure the system is updated: sudo apt update && sudo apt install ubuntu-advantage-tools -y # verify it's version 31 or higher: $ dpkg -l ubuntu-advantage-tools | grep ubuntu-advantage-tools ii ubuntu-advantage-tools 31.2~22.04 all transitional dummy package for ubuntu-pro-client # remove (not purge) apparmor: sudo apt remove apparmor -y # reboot sudo reboot # start apt-news.service, and verify it fails: $ sudo systemctl start apt-news.service Job for apt-news.service failed because the control process exited with error code. See "systemctl status apt-news.service" and "journalctl -xeu apt-news.service" for details. # The log will show it's because it couldn't confine the service with the ubuntu_pro_apt_news profile: $ systemctl status apt-news.service × apt-news.service - Update APT News Loaded: loaded (/lib/systemd/system/apt-news.service; static) Active: failed (Result: exit-code) since Mon 2024-03-18 20:35:41 UTC; 35s ago Process: 263 ExecStart=/usr/bin/python3 /usr/lib/ubuntu-advantage/apt_news.py (code=exited, status=231/APPARMOR) Main PID: 263 (code=exited, status=231/APPARMOR) CPU: 7ms Mar 18 20:35:41 j systemd[1]: Starting Update APT News... Mar 18 20:35:41 j systemd[263]: apt-news.service: Failed to prepare AppArmor profile change to ubuntu_pro_apt_news: No such file or directory Mar 18 20:35:41 j systemd[263]: apt-news.service: Failed at step APPARMOR spawning /usr/bin/python3: No such file or directory Mar 18 20:35:41 j systemd[1]: apt-news.service: Main process exited, code=exited, status=231/APPARMOR Mar 18 20:35:41 j systemd[1]: apt-news.service: Failed with result 'exit-code'. Mar 18 20:35:41 j systemd[1]: Failed to start Update APT News. With the fixed package, the service will not fail to start. b) Continuing from the test plan above, now we will confirm that if apparmor is installed, that the apt-news service is run confined. * Install apparmor back again and reboot: $ sudo apt install apparmor -y $ sudo reboot * Confirm the apt-news profile is loaded and in
[Group.of.nepali.translators] [Bug 2057937] Re: apt-news.service reporting errors after ubuntu-pro-client install
This bug was fixed in the package ubuntu-advantage-tools - 31.2.2~16.04 --- ubuntu-advantage-tools (31.2.2~16.04) xenial; urgency=medium * version.py: match version from d/changelog (LP: #2058934) ubuntu-advantage-tools (31.2.1~16.04) xenial; urgency=medium * apt-news.service: ignore apparmor errors when starting (LP: #2057937) -- Andreas Hasenack Mon, 25 Mar 2024 11:29:56 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2057937 Title: apt-news.service reporting errors after ubuntu-pro-client install Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [ Impact ] src:ubuntu-advantage-tools version 31 introduced[1] an apparmor profile to the apt-news service. It's known that some ubuntu systems do not have apparmor enabled, and this was considered. The systemd.exec(5) manpage states that the AppArmorProfile setting has no effect if apparmor is disabled[2]. This was tested and verified. Turns out, however, that apparmor can be enabled on a system, but without the apparmor package installed. When this package is not installed, no profiles are loaded. Crucially, the ubuntu_pro_apt_news profile, used by apt-news.service, is not loaded. This situation is different than "apparmor is disabled", and systemd will try to launch apt-news confined by ubuntu_pro_apt_news. But since that profile is not loaded into the kernel, the service will fail. apt-news.service is called as an apt update hook, but its failure does not fail apt, since it's guarded[3] by "|| true", i.e., failures in the hook are ignored. The only impact is that apt news won't be fetched. [ Test Plan ] The test plan will be in two parts. One to confirm the apt-news service won't fail to start if the apparmor profile is not available (it's what triggered this bug). The second part is to confirm that in the "good case", with apparmor available on the system, the confinement is still applied. a) To reproduce the problem, launch an ubuntu lxd container, or a VM, and: # install ubuntu-advantage-tools 31 or later. It's in updates right now, so just make sure the system is updated: sudo apt update && sudo apt install ubuntu-advantage-tools -y # verify it's version 31 or higher: $ dpkg -l ubuntu-advantage-tools | grep ubuntu-advantage-tools ii ubuntu-advantage-tools 31.2~22.04 all transitional dummy package for ubuntu-pro-client # remove (not purge) apparmor: sudo apt remove apparmor -y # reboot sudo reboot # start apt-news.service, and verify it fails: $ sudo systemctl start apt-news.service Job for apt-news.service failed because the control process exited with error code. See "systemctl status apt-news.service" and "journalctl -xeu apt-news.service" for details. # The log will show it's because it couldn't confine the service with the ubuntu_pro_apt_news profile: $ systemctl status apt-news.service × apt-news.service - Update APT News Loaded: loaded (/lib/systemd/system/apt-news.service; static) Active: failed (Result: exit-code) since Mon 2024-03-18 20:35:41 UTC; 35s ago Process: 263 ExecStart=/usr/bin/python3 /usr/lib/ubuntu-advantage/apt_news.py (code=exited, status=231/APPARMOR) Main PID: 263 (code=exited, status=231/APPARMOR) CPU: 7ms Mar 18 20:35:41 j systemd[1]: Starting Update APT News... Mar 18 20:35:41 j systemd[263]: apt-news.service: Failed to prepare AppArmor profile change to ubuntu_pro_apt_news: No such file or directory Mar 18 20:35:41 j systemd[263]: apt-news.service: Failed at step APPARMOR spawning /usr/bin/python3: No such file or directory Mar 18 20:35:41 j systemd[1]: apt-news.service: Main process exited, code=exited, status=231/APPARMOR Mar 18 20:35:41 j systemd[1]: apt-news.service: Failed with result 'exit-code'. Mar 18 20:35:41 j systemd[1]: Failed to start Update APT News. With the fixed package, the service will not fail to start. b) Continuing from the test plan above, now we will confirm that if apparmor is installed, that the apt-news service is run confined. * Install apparmor back again and reboot: $ sudo apt install apparmor -y $ sudo reboot * Confirm the apt-news profile is loaded and
[Group.of.nepali.translators] [Bug 2057937] Re: apt-news.service reporting errors after ubuntu-pro-client install
This bug was fixed in the package ubuntu-advantage-tools - 31.2.2~22.04 --- ubuntu-advantage-tools (31.2.2~22.04) jammy; urgency=medium * version.py: match version from d/changelog (LP: #2058934) ubuntu-advantage-tools (31.2.1~22.04) jammy; urgency=medium * apt-news.service: ignore apparmor errors when starting (LP: #2057937) -- Andreas Hasenack Mon, 25 Mar 2024 11:52:09 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: ubuntu-advantage-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2057937 Title: apt-news.service reporting errors after ubuntu-pro-client install Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [ Impact ] src:ubuntu-advantage-tools version 31 introduced[1] an apparmor profile to the apt-news service. It's known that some ubuntu systems do not have apparmor enabled, and this was considered. The systemd.exec(5) manpage states that the AppArmorProfile setting has no effect if apparmor is disabled[2]. This was tested and verified. Turns out, however, that apparmor can be enabled on a system, but without the apparmor package installed. When this package is not installed, no profiles are loaded. Crucially, the ubuntu_pro_apt_news profile, used by apt-news.service, is not loaded. This situation is different than "apparmor is disabled", and systemd will try to launch apt-news confined by ubuntu_pro_apt_news. But since that profile is not loaded into the kernel, the service will fail. apt-news.service is called as an apt update hook, but its failure does not fail apt, since it's guarded[3] by "|| true", i.e., failures in the hook are ignored. The only impact is that apt news won't be fetched. [ Test Plan ] The test plan will be in two parts. One to confirm the apt-news service won't fail to start if the apparmor profile is not available (it's what triggered this bug). The second part is to confirm that in the "good case", with apparmor available on the system, the confinement is still applied. a) To reproduce the problem, launch an ubuntu lxd container, or a VM, and: # install ubuntu-advantage-tools 31 or later. It's in updates right now, so just make sure the system is updated: sudo apt update && sudo apt install ubuntu-advantage-tools -y # verify it's version 31 or higher: $ dpkg -l ubuntu-advantage-tools | grep ubuntu-advantage-tools ii ubuntu-advantage-tools 31.2~22.04 all transitional dummy package for ubuntu-pro-client # remove (not purge) apparmor: sudo apt remove apparmor -y # reboot sudo reboot # start apt-news.service, and verify it fails: $ sudo systemctl start apt-news.service Job for apt-news.service failed because the control process exited with error code. See "systemctl status apt-news.service" and "journalctl -xeu apt-news.service" for details. # The log will show it's because it couldn't confine the service with the ubuntu_pro_apt_news profile: $ systemctl status apt-news.service × apt-news.service - Update APT News Loaded: loaded (/lib/systemd/system/apt-news.service; static) Active: failed (Result: exit-code) since Mon 2024-03-18 20:35:41 UTC; 35s ago Process: 263 ExecStart=/usr/bin/python3 /usr/lib/ubuntu-advantage/apt_news.py (code=exited, status=231/APPARMOR) Main PID: 263 (code=exited, status=231/APPARMOR) CPU: 7ms Mar 18 20:35:41 j systemd[1]: Starting Update APT News... Mar 18 20:35:41 j systemd[263]: apt-news.service: Failed to prepare AppArmor profile change to ubuntu_pro_apt_news: No such file or directory Mar 18 20:35:41 j systemd[263]: apt-news.service: Failed at step APPARMOR spawning /usr/bin/python3: No such file or directory Mar 18 20:35:41 j systemd[1]: apt-news.service: Main process exited, code=exited, status=231/APPARMOR Mar 18 20:35:41 j systemd[1]: apt-news.service: Failed with result 'exit-code'. Mar 18 20:35:41 j systemd[1]: Failed to start Update APT News. With the fixed package, the service will not fail to start. b) Continuing from the test plan above, now we will confirm that if apparmor is installed, that the apt-news service is run confined. * Install apparmor back again and reboot:
[Group.of.nepali.translators] [Bug 2057937] Re: apt-news.service reporting errors after ubuntu-pro-client install
This bug was fixed in the package ubuntu-advantage-tools - 31.2.2~23.10 --- ubuntu-advantage-tools (31.2.2~23.10) mantic; urgency=medium * version.py: match version from d/changelog (LP: #2058934) ubuntu-advantage-tools (31.2.1~23.10) mantic; urgency=medium * apt-news.service: ignore apparmor errors when starting (LP: #2057937) -- Andreas Hasenack Mon, 25 Mar 2024 11:56:18 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2057937 Title: apt-news.service reporting errors after ubuntu-pro-client install Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [ Impact ] src:ubuntu-advantage-tools version 31 introduced[1] an apparmor profile to the apt-news service. It's known that some ubuntu systems do not have apparmor enabled, and this was considered. The systemd.exec(5) manpage states that the AppArmorProfile setting has no effect if apparmor is disabled[2]. This was tested and verified. Turns out, however, that apparmor can be enabled on a system, but without the apparmor package installed. When this package is not installed, no profiles are loaded. Crucially, the ubuntu_pro_apt_news profile, used by apt-news.service, is not loaded. This situation is different than "apparmor is disabled", and systemd will try to launch apt-news confined by ubuntu_pro_apt_news. But since that profile is not loaded into the kernel, the service will fail. apt-news.service is called as an apt update hook, but its failure does not fail apt, since it's guarded[3] by "|| true", i.e., failures in the hook are ignored. The only impact is that apt news won't be fetched. [ Test Plan ] The test plan will be in two parts. One to confirm the apt-news service won't fail to start if the apparmor profile is not available (it's what triggered this bug). The second part is to confirm that in the "good case", with apparmor available on the system, the confinement is still applied. a) To reproduce the problem, launch an ubuntu lxd container, or a VM, and: # install ubuntu-advantage-tools 31 or later. It's in updates right now, so just make sure the system is updated: sudo apt update && sudo apt install ubuntu-advantage-tools -y # verify it's version 31 or higher: $ dpkg -l ubuntu-advantage-tools | grep ubuntu-advantage-tools ii ubuntu-advantage-tools 31.2~22.04 all transitional dummy package for ubuntu-pro-client # remove (not purge) apparmor: sudo apt remove apparmor -y # reboot sudo reboot # start apt-news.service, and verify it fails: $ sudo systemctl start apt-news.service Job for apt-news.service failed because the control process exited with error code. See "systemctl status apt-news.service" and "journalctl -xeu apt-news.service" for details. # The log will show it's because it couldn't confine the service with the ubuntu_pro_apt_news profile: $ systemctl status apt-news.service × apt-news.service - Update APT News Loaded: loaded (/lib/systemd/system/apt-news.service; static) Active: failed (Result: exit-code) since Mon 2024-03-18 20:35:41 UTC; 35s ago Process: 263 ExecStart=/usr/bin/python3 /usr/lib/ubuntu-advantage/apt_news.py (code=exited, status=231/APPARMOR) Main PID: 263 (code=exited, status=231/APPARMOR) CPU: 7ms Mar 18 20:35:41 j systemd[1]: Starting Update APT News... Mar 18 20:35:41 j systemd[263]: apt-news.service: Failed to prepare AppArmor profile change to ubuntu_pro_apt_news: No such file or directory Mar 18 20:35:41 j systemd[263]: apt-news.service: Failed at step APPARMOR spawning /usr/bin/python3: No such file or directory Mar 18 20:35:41 j systemd[1]: apt-news.service: Main process exited, code=exited, status=231/APPARMOR Mar 18 20:35:41 j systemd[1]: apt-news.service: Failed with result 'exit-code'. Mar 18 20:35:41 j systemd[1]: Failed to start Update APT News. With the fixed package, the service will not fail to start. b) Continuing from the test plan above, now we will confirm that if apparmor is installed, that the apt-news service is run confined. * Install apparmor back again and reboot: $ sudo apt install apparmor -y $ sudo reboot * Confirm the apt-news profile is loaded and
[Group.of.nepali.translators] [Bug 2058934] Re: Missing version.py update
This bug was fixed in the package ubuntu-advantage-tools - 31.2.2~16.04 --- ubuntu-advantage-tools (31.2.2~16.04) xenial; urgency=medium * version.py: match version from d/changelog (LP: #2058934) ubuntu-advantage-tools (31.2.1~16.04) xenial; urgency=medium * apt-news.service: ignore apparmor errors when starting (LP: #2057937) -- Andreas Hasenack Mon, 25 Mar 2024 11:29:56 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2058934 Title: Missing version.py update Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [ Impact ] The "pro" command-line tool has a "version" parameter that needs to be kept in sync with the package version from d/changelog. This has been forgotten in 31.2.1, and we decided to release 31.2.2 with that fix. [ Test Plan ] Install ubuntu-advantage-tools and run the command: pro version Its output must match the package version from: dpkg -l ubuntu-advantage-tools [ Where problems could occur ] The most common problem here is to rebuild the package with a new version, or new suffix, and forgetting to update version.py again. Another problem is that the version.py update could be the wrong version, but the test plan is looking for that exactly. [ Other Info ] Not at this time. [ Original Description ] https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2.1 missed a corresponding uaclient/version.py version update to match d/changelog. It was fixed in https://launchpad.net/ubuntu/+source/ubuntu-advantage- tools/31.2.2 without a changelog reference, and we should use this bug for the same change for the upcoming SRU in https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+bug/2057937 Version 31.2.1 was not technically released as an SRU yet, it briefly existed in the unapproved queues without the uaclient/version.py fix, but was rejected in time. Technically we could add the corresponding version.py fix and use 31.2.1 in the SRUs, but we prefer to keep the stable releases using the same version everywhere, including devel. So let's make a 31.2.2 for the SRU, matching noble, and use this bug to track that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2058934] Re: Missing version.py update
This bug was fixed in the package ubuntu-advantage-tools - 31.2.2~20.04 --- ubuntu-advantage-tools (31.2.2~20.04) focal; urgency=medium * version.py: match version from d/changelog (LP: #2058934) ubuntu-advantage-tools (31.2.1~20.04) focal; urgency=medium * apt-news.service: ignore apparmor errors when starting (LP: #2057937) -- Andreas Hasenack Mon, 25 Mar 2024 11:49:51 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2058934 Title: Missing version.py update Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [ Impact ] The "pro" command-line tool has a "version" parameter that needs to be kept in sync with the package version from d/changelog. This has been forgotten in 31.2.1, and we decided to release 31.2.2 with that fix. [ Test Plan ] Install ubuntu-advantage-tools and run the command: pro version Its output must match the package version from: dpkg -l ubuntu-advantage-tools [ Where problems could occur ] The most common problem here is to rebuild the package with a new version, or new suffix, and forgetting to update version.py again. Another problem is that the version.py update could be the wrong version, but the test plan is looking for that exactly. [ Other Info ] Not at this time. [ Original Description ] https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2.1 missed a corresponding uaclient/version.py version update to match d/changelog. It was fixed in https://launchpad.net/ubuntu/+source/ubuntu-advantage- tools/31.2.2 without a changelog reference, and we should use this bug for the same change for the upcoming SRU in https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+bug/2057937 Version 31.2.1 was not technically released as an SRU yet, it briefly existed in the unapproved queues without the uaclient/version.py fix, but was rejected in time. Technically we could add the corresponding version.py fix and use 31.2.1 in the SRUs, but we prefer to keep the stable releases using the same version everywhere, including devel. So let's make a 31.2.2 for the SRU, matching noble, and use this bug to track that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2058934] Re: Missing version.py update
This bug was fixed in the package ubuntu-advantage-tools - 31.2.2~22.04 --- ubuntu-advantage-tools (31.2.2~22.04) jammy; urgency=medium * version.py: match version from d/changelog (LP: #2058934) ubuntu-advantage-tools (31.2.1~22.04) jammy; urgency=medium * apt-news.service: ignore apparmor errors when starting (LP: #2057937) -- Andreas Hasenack Mon, 25 Mar 2024 11:52:09 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: ubuntu-advantage-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2058934 Title: Missing version.py update Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [ Impact ] The "pro" command-line tool has a "version" parameter that needs to be kept in sync with the package version from d/changelog. This has been forgotten in 31.2.1, and we decided to release 31.2.2 with that fix. [ Test Plan ] Install ubuntu-advantage-tools and run the command: pro version Its output must match the package version from: dpkg -l ubuntu-advantage-tools [ Where problems could occur ] The most common problem here is to rebuild the package with a new version, or new suffix, and forgetting to update version.py again. Another problem is that the version.py update could be the wrong version, but the test plan is looking for that exactly. [ Other Info ] Not at this time. [ Original Description ] https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2.1 missed a corresponding uaclient/version.py version update to match d/changelog. It was fixed in https://launchpad.net/ubuntu/+source/ubuntu-advantage- tools/31.2.2 without a changelog reference, and we should use this bug for the same change for the upcoming SRU in https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+bug/2057937 Version 31.2.1 was not technically released as an SRU yet, it briefly existed in the unapproved queues without the uaclient/version.py fix, but was rejected in time. Technically we could add the corresponding version.py fix and use 31.2.1 in the SRUs, but we prefer to keep the stable releases using the same version everywhere, including devel. So let's make a 31.2.2 for the SRU, matching noble, and use this bug to track that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2058934] Re: Missing version.py update
This bug was fixed in the package ubuntu-advantage-tools - 31.2.2~23.10 --- ubuntu-advantage-tools (31.2.2~23.10) mantic; urgency=medium * version.py: match version from d/changelog (LP: #2058934) ubuntu-advantage-tools (31.2.1~23.10) mantic; urgency=medium * apt-news.service: ignore apparmor errors when starting (LP: #2057937) -- Andreas Hasenack Mon, 25 Mar 2024 11:56:18 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2058934 Title: Missing version.py update Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [ Impact ] The "pro" command-line tool has a "version" parameter that needs to be kept in sync with the package version from d/changelog. This has been forgotten in 31.2.1, and we decided to release 31.2.2 with that fix. [ Test Plan ] Install ubuntu-advantage-tools and run the command: pro version Its output must match the package version from: dpkg -l ubuntu-advantage-tools [ Where problems could occur ] The most common problem here is to rebuild the package with a new version, or new suffix, and forgetting to update version.py again. Another problem is that the version.py update could be the wrong version, but the test plan is looking for that exactly. [ Other Info ] Not at this time. [ Original Description ] https://launchpad.net/ubuntu/+source/ubuntu-advantage-tools/31.2.1 missed a corresponding uaclient/version.py version update to match d/changelog. It was fixed in https://launchpad.net/ubuntu/+source/ubuntu-advantage- tools/31.2.2 without a changelog reference, and we should use this bug for the same change for the upcoming SRU in https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+bug/2057937 Version 31.2.1 was not technically released as an SRU yet, it briefly existed in the unapproved queues without the uaclient/version.py fix, but was rejected in time. Technically we could add the corresponding version.py fix and use 31.2.1 in the SRUs, but we prefer to keep the stable releases using the same version everywhere, including devel. So let's make a 31.2.2 for the SRU, matching noble, and use this bug to track that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2058934/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1825755] Re: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files
This bug was fixed in the package apt-mirror - 0.5.4-1ubuntu1.20.04.1 --- apt-mirror (0.5.4-1ubuntu1.20.04.1) focal; urgency=medium * Download cnf files (LP: #1825755) - Adds support for xz files - d/p/Support-for-xz-translations.patch - d/p/Download-cnf-Files.patch -- Heather Lemon Wed, 31 Jan 2024 14:16:34 + ** Changed in: apt-mirror (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825755 Title: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files Status in apt-mirror package in Ubuntu: Fix Released Status in apt-mirror source package in Xenial: Won't Fix Status in apt-mirror source package in Bionic: Won't Fix Status in apt-mirror source package in Eoan: Won't Fix Status in apt-mirror source package in Focal: Fix Released Status in apt-mirror source package in Groovy: Won't Fix Status in apt-mirror source package in Jammy: Fix Released Bug description: [Impact] * since ubuntu disco, main repositories contains 'cnf' directory with 'Commands*' files. those files are compressed with xy, whereas apt- mirror 0.5.1 doesn't contain the patch which enable download of .xz compressed files * Without this update, users are not able to mirror newer releases of Ubuntu. [Test Case] * On any release of Ubuntu install apt-mirror and add this line to /etc/apt/mirror.list: deb http://archive.ubuntu.com/ubuntu eoan-updates main restricted universe multiverse * sync the mirror using `apt-mirror` * Attempt to run `apt update` against the mirror. The result will be similar to: ... Err:7 http://10.3.0.41/ubuntu eoan-updates/main amd64 c-n-f Metadata 404 Not Found [IP: 10.3.0.41 80] Ign:14 http://10.3.0.41/ubuntu eoan-updates/multiverse amd64 c-n-f Metadata Ign:15 http://10.3.0.41/ubuntu eoan-updates/universe amd64 c-n-f Metadata Ign:16 http://10.3.0.41/ubuntu eoan-updates/restricted amd64 c-n-f Metadata Reading package lists... Done E: Failed to fetch http://10.3.0.41/ubuntu/dists/eoan-updates/main/cnf/Commands-amd64 404 Not Found [IP: 10.3.0.41 80] E: Some index files failed to download. They have been ignored, or old ones used instead. ... * Updating the apt-mirror package from ppa:slashd/test and then re- running the `apt-mirror` command will then allow a successful `apt update`. [Regression Potential] * The regression potential is low since the package doesn't currently work properly anyway. * It's a patchset from a fork repo, if apt-mirror upstream becomes alive again in the future, it won't necessary mean that the fork will be commited/merged upstream, and Ubuntu package might differ from original upstream until next version bump. [Other informations] Upstream bug: https://github.com/apt-mirror/apt-mirror/issues/118 Not much update has been made since Upstream become inactive as noted from the output of rmadison: Since Bionic, it is a simple copy from release to active devel release and so on directly from debian, no patching whatsoever and nothing new to pull from Debian as well. Ubuntu apt-mirror | 0.5.1-1ubuntu1 | xenial/universe | source, all apt-mirror | 0.5.4-1 | bionic/universe | source, all apt-mirror | 0.5.4-1 | disco/universe | source, all apt-mirror | 0.5.4-1 | eoan/universe| source, all apt-mirror | 0.5.4-1 | focal/universe | source, all apt-mirror | 0.5.4-1 | groovy/universe | source, all Debian apt-mirror 0.5.4-1 is found in sid/unstable --- The required patchset is from a fork of upstream apt-mirror josbraden/apt-mirror (https://github.com/josbraden/apt-mirror) Note that upstream apt-mirror is not active anymore, and is looking for a new maintainer as published in their github page: https://github.com/apt-mirror/apt-mirror That's why we have to rely on the fork atm. The required patchset are (tested by Chris in the form of a test pkg: 0001-Copy-DEP-11-functions-for-editing.patch 0001-Replace-DEP-11-with-cnf-in-DEP-11-code-copy.patch 0001-Fix-Regex.patch 0001-Improve-regex-for-cnf-file-matching.patch 0001-Remove-dev-note.patch 0001-Fix-missing-parenthesis.patch I also talked with sil2100 (SRU verification team member) about the feasibilty of this SRU (from a fork repo): " Yeah, I'd say fixes from forked repositories in this case make sense Since there's no longer any 'one authority' for it. " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1825755/+subscriptions ___ Mailing list:
[Group.of.nepali.translators] [Bug 2058133] Re: [SRU] update-manager crashes when ua security-status response is an error
This bug was fixed in the package update-manager - 1:22.04.20
---
update-manager (1:22.04.20) jammy; urgency=medium
* Replace Popen to 'ua security-status --format=json' by the Ubuntu Pro API.
The former is not stable enough and would break the program once in a
while when something unrelated to Update Manager (Livepatch, for instance)
went awry. The updates() end point from the API, on the other hand,
does not raise exceptions. LP: #2058133.
-- Nathan Pratta Teodosio Fri, 22 Mar
2024 08:24:04 +0100
** Changed in: update-manager (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2058133
Title:
[SRU] update-manager crashes when ua security-status response is an
error
Status in Canonical Livepatch Client:
New
Status in ubuntu-advantage-tools package in Ubuntu:
Invalid
Status in update-manager package in Ubuntu:
Fix Released
Status in update-manager source package in Xenial:
Fix Committed
Status in update-manager source package in Bionic:
Fix Committed
Status in update-manager source package in Focal:
Fix Committed
Status in update-manager source package in Jammy:
Fix Released
Status in update-manager source package in Noble:
Fix Released
Bug description:
Impact
--
Update Manager fails to launch in the LTS releases if the 'ua
security-status' command fails. It tries to parse its output to
generate the list of ESM-Apps and ESM-Infra updates that would be
available if the system were attached to Ubuntu Pro.
However, if ua finds some problem with unrelated stuff, such as
Livepatch (as evidenced by the attached ubuntu-advantage.log), the
command just raises an error, crashing Update Manager.
Although Update Manager could catch the error, it would result in not
showing Ubuntu Pro updates, simply because the information is not
there.
Better would be to ditch 'ua security-status' in favor of the Ubuntu
Pro API. The updates() end point[1] will provide the information
Update Manager wants even if the Ubuntu Advantage daemon has issues
with other services such as Livepatch (as evidenced by #10), and it
does not raise exceptions.
[1] https://canonical-ubuntu-pro-client.readthedocs-
hosted.com/en/latest/references/api/#u-pro-packages-updates-v1
Test Plan
-
Attach your machine to Ubuntu Pro and make sure Livepatch is enabled
in the output of 'ua status'. Then, simulate a failing Livepatch with
--->
mv /snap/bin/canonical-livepatch /snap/bin/canonical-livepatch.bak
>/snap/bin/canonical-livepatch printf '%s\n' '#!/bin/sh' 'exit 1'
chmod +x /snap/bin/canonical-livepatch
<
Launch update-manager, it should open and not crash.
Where problems could occur
--
In the Ubuntu Pro section of the updates, in form of wrong package
data (e.g. package name, version number etc.) in the description pane
when selecting a package. The section could not show at all, or the
program could crash right away.
Original bug report
---
Below is a run in my computer. Please send a mail on what to do
fuga2:~> update-manager -c -d
Unexpected error(s) occurred.
For more details, see the log: /var/log/ubuntu-advantage.log
To file a bug run: ubuntu-bug ubuntu-advantage-tools
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py",
line 448, in _on_finished
self._action_done(action,
File "/usr/lib/python3/dist-packages/UpdateManager/backend/__init__.py",
line 365, in _action_done
self.window_main.start_available()
File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line
241, in start_available
self.refresh_cache()
File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line
459, in refresh_cache
self._get_ua_security_status()
File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line
285, in _get_ua_security_status
s = json.load(p.stdout)
File "/usr/lib/python3.10/json/__init__.py", line 293, in load
return loads(fp.read(),
File "/usr/lib/python3.10/json/__init__.py", line 346, in loads
return _default_decoder.decode(s)
File "/usr/lib/python3.10/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.10/json/decoder.py", line 355, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
^CTraceback (most recent call last):
File "/usr/bin/update-manager", line 125, in
Gtk.main()
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 1687, in
main
with
[Group.of.nepali.translators] [Bug 2055686] Re: Drop ABI checks from kernel build
This bug was fixed in the package linux - 5.15.0-102.112 --- linux (5.15.0-102.112) jammy; urgency=medium * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632) * Drop ABI checks from kernel build (LP: #2055686) - [Packaging] Remove in-tree abi checks - [Packaging] Drop abi checks from final-checks * Packaging resync (LP: #1786013) - [Packaging] drop ABI data - [Packaging] update annotations scripts - debian.master/dkms-versions -- update from kernel-versions (main/2024.03.04) * block/loop: No longer allows to create partitions (LP: #2056143) - block, loop: support partitions without scanning * Cranky update-dkms-versions rollout (LP: #2055685) - [Packaging] remove update-dkms-versions - Move debian/dkms-versions to debian.master/dkms-versions - [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions - [Packaging] remove update-version-dkms * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux- modules-extra to linux-modules (LP: #2054809) - UBUNTU [Packaging]: Include erofs in linux-modules instead of linux-modules- extra * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094) - [Packaging] rules: Put usbip manpages in the correct directory * CVE-2024-23851 - dm ioctl: log an error if the ioctl structure is corrupted - dm: limit the number of targets and parameter size area * CVE-2024-23850 - btrfs: do not ASSERT() if the newly created subvolume already got read * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform (LP: #2054699) - x86/tsc: Extend watchdog check exemption to 4-Sockets platform * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules (LP: #2045561) - [Packaging] Move dmi-sysfs.ko into linux-modules * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567) - Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on stack" * Jammy update: v5.15.148 upstream stable release (LP: #2055145) - f2fs: explicitly null-terminate the xattr list - pinctrl: lochnagar: Don't build on MIPS - ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro - mptcp: fix uninit-value in mptcp_incoming_options - wifi: cfg80211: lock wiphy mutex for rfkill poll - debugfs: fix automount d_fsdata usage - drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer - nvme-core: check for too small lba shift - ASoC: wm8974: Correct boost mixer inputs - ASoC: Intel: Skylake: Fix mem leak in few functions - ASoC: nau8822: Fix incorrect type in assignment and cast to restricted __be16 - ASoC: Intel: Skylake: mem leak in skl register function - ASoC: cs43130: Fix the position of const qualifier - ASoC: cs43130: Fix incorrect frame delay configuration - ASoC: rt5650: add mutex to avoid the jack detection failure - nouveau/tu102: flush all pdbs on vmm flush - net/tg3: fix race condition in tg3_reset_task() - ASoC: da7219: Support low DC impedance headset - ASoC: ops: add correct range check for limiting volume - nvme: introduce helper function to get ctrl state - drm/amdgpu: Add NULL checks for function pointers - drm/exynos: fix a potential error pointer dereference - drm/exynos: fix a wrong error checking - hwmon: (corsair-psu) Fix probe when built-in - clk: rockchip: rk3128: Fix HCLK_OTG gate register - jbd2: correct the printing of write_flags in jbd2_write_superblock() - drm/crtc: Fix uninit-value bug in drm_mode_setcrtc - neighbour: Don't let neigh_forced_gc() disable preemption for long - platform/x86: intel-vbtn: Fix missing tablet-mode-switch events - jbd2: fix soft lockup in journal_finish_inode_data_buffers() - tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing - tracing: Add size check when printing trace_marker output - stmmac: dwmac-loongson: drop useless check for compatible fallback - MIPS: dts: loongson: drop incorrect dwmac fallback compatible - tracing: Fix uaf issue when open the hist or hist_debug file - ring-buffer: Do not record in NMI if the arch does not support cmpxchg in NMI - reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning - Input: atkbd - skip ATKBD_CMD_GETID in translated mode - Input: i8042 - add nomux quirk for Acer P459-G2-M - s390/scm: fix virtual vs physical address confusion - ARC: fix spare error - wifi: iwlwifi: pcie: avoid a NULL pointer dereference - Input: xpad - add Razer Wolverine V2 support - ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346 - i2c: rk3x: fix potential spinlock recursion on poll - net: qrtr: ns: Return 0 if server port is not present - ARM: sun9i: smp: fix return code check of
[Group.of.nepali.translators] [Bug 2055685] Re: Cranky update-dkms-versions rollout
This bug was fixed in the package linux - 5.15.0-102.112 --- linux (5.15.0-102.112) jammy; urgency=medium * jammy/linux: 5.15.0-102.112 -proposed tracker (LP: #2055632) * Drop ABI checks from kernel build (LP: #2055686) - [Packaging] Remove in-tree abi checks - [Packaging] Drop abi checks from final-checks * Packaging resync (LP: #1786013) - [Packaging] drop ABI data - [Packaging] update annotations scripts - debian.master/dkms-versions -- update from kernel-versions (main/2024.03.04) * block/loop: No longer allows to create partitions (LP: #2056143) - block, loop: support partitions without scanning * Cranky update-dkms-versions rollout (LP: #2055685) - [Packaging] remove update-dkms-versions - Move debian/dkms-versions to debian.master/dkms-versions - [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions - [Packaging] remove update-version-dkms * linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux- modules-extra to linux-modules (LP: #2054809) - UBUNTU [Packaging]: Include erofs in linux-modules instead of linux-modules- extra * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094) - [Packaging] rules: Put usbip manpages in the correct directory * CVE-2024-23851 - dm ioctl: log an error if the ioctl structure is corrupted - dm: limit the number of targets and parameter size area * CVE-2024-23850 - btrfs: do not ASSERT() if the newly created subvolume already got read * x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform (LP: #2054699) - x86/tsc: Extend watchdog check exemption to 4-Sockets platform * linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules (LP: #2045561) - [Packaging] Move dmi-sysfs.ko into linux-modules * Fix bpf selftests build failure after v5.15.139 update (LP: #2054567) - Revert "selftests/bpf: Test tail call counting with bpf2bpf and data on stack" * Jammy update: v5.15.148 upstream stable release (LP: #2055145) - f2fs: explicitly null-terminate the xattr list - pinctrl: lochnagar: Don't build on MIPS - ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro - mptcp: fix uninit-value in mptcp_incoming_options - wifi: cfg80211: lock wiphy mutex for rfkill poll - debugfs: fix automount d_fsdata usage - drm/amdgpu: Fix cat debugfs amdgpu_regs_didt causes kernel null pointer - nvme-core: check for too small lba shift - ASoC: wm8974: Correct boost mixer inputs - ASoC: Intel: Skylake: Fix mem leak in few functions - ASoC: nau8822: Fix incorrect type in assignment and cast to restricted __be16 - ASoC: Intel: Skylake: mem leak in skl register function - ASoC: cs43130: Fix the position of const qualifier - ASoC: cs43130: Fix incorrect frame delay configuration - ASoC: rt5650: add mutex to avoid the jack detection failure - nouveau/tu102: flush all pdbs on vmm flush - net/tg3: fix race condition in tg3_reset_task() - ASoC: da7219: Support low DC impedance headset - ASoC: ops: add correct range check for limiting volume - nvme: introduce helper function to get ctrl state - drm/amdgpu: Add NULL checks for function pointers - drm/exynos: fix a potential error pointer dereference - drm/exynos: fix a wrong error checking - hwmon: (corsair-psu) Fix probe when built-in - clk: rockchip: rk3128: Fix HCLK_OTG gate register - jbd2: correct the printing of write_flags in jbd2_write_superblock() - drm/crtc: Fix uninit-value bug in drm_mode_setcrtc - neighbour: Don't let neigh_forced_gc() disable preemption for long - platform/x86: intel-vbtn: Fix missing tablet-mode-switch events - jbd2: fix soft lockup in journal_finish_inode_data_buffers() - tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing - tracing: Add size check when printing trace_marker output - stmmac: dwmac-loongson: drop useless check for compatible fallback - MIPS: dts: loongson: drop incorrect dwmac fallback compatible - tracing: Fix uaf issue when open the hist or hist_debug file - ring-buffer: Do not record in NMI if the arch does not support cmpxchg in NMI - reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning - Input: atkbd - skip ATKBD_CMD_GETID in translated mode - Input: i8042 - add nomux quirk for Acer P459-G2-M - s390/scm: fix virtual vs physical address confusion - ARC: fix spare error - wifi: iwlwifi: pcie: avoid a NULL pointer dereference - Input: xpad - add Razer Wolverine V2 support - ASoC: Intel: bytcr_rt5640: Add quirk for the Medion Lifetab S10346 - i2c: rk3x: fix potential spinlock recursion on poll - net: qrtr: ns: Return 0 if server port is not present - ARM: sun9i: smp: fix return code check of
[Group.of.nepali.translators] [Bug 2055685] Re: Cranky update-dkms-versions rollout
This bug was fixed in the package linux - 5.4.0-176.196 --- linux (5.4.0-176.196) focal; urgency=medium * focal/linux: 5.4.0-176.196 -proposed tracker (LP: #2058756) * Problems with HVCS and hotplugging (LP: #2056373) - powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry - powerpc/pseries: Fix of_read_drc_info_cell() to point at next record - hvcs: Fix hvcs port reference counting - hvcs: Use dev_groups to manage hvcs device attributes - hvcs: Use driver groups to manage driver attributes - hvcs: Get reference to tty in remove - hvcs: Use vhangup in hotplug remove - hvcs: Synchronize hotplug remove with port free linux (5.4.0-175.195) focal; urgency=medium * focal/linux: 5.4.0-175.195 -proposed tracker (LP: #2055684) * Packaging resync (LP: #1786013) - [Packaging] drop ABI data - [Packaging] update annotations scripts - debian.master/dkms-versions -- update from kernel-versions (main/2024.03.04) * Drop ABI checks from kernel build (LP: #2055686) - [Packaging] Remove in-tree abi checks - [Packaging] Bring back install- prerequisite for checks- - [Packaging] Remove abi-check from final-checks * Cranky update-dkms-versions rollout (LP: #2055685) - [Packaging] remove update-dkms-versions - Move debian/dkms-versions to debian.master/dkms-versions - [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions - [Packaging] remove update-version-dkms * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094) - [Packaging] rules: Put usbip manpages in the correct directory * CVE-2024-23851 - dm ioctl: log an error if the ioctl structure is corrupted - dm: limit the number of targets and parameter size area * Focal update: v5.4.268 upstream stable release (LP: #2055075) - f2fs: explicitly null-terminate the xattr list - pinctrl: lochnagar: Don't build on MIPS - ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro - ASoC: Intel: Skylake: Fix mem leak in few functions - ASoC: nau8822: Fix incorrect type in assignment and cast to restricted __be16 - ASoC: Intel: Skylake: mem leak in skl register function - ASoC: cs43130: Fix the position of const qualifier - ASoC: cs43130: Fix incorrect frame delay configuration - ASoC: rt5650: add mutex to avoid the jack detection failure - nouveau/tu102: flush all pdbs on vmm flush - net/tg3: fix race condition in tg3_reset_task() - ASoC: da7219: Support low DC impedance headset - nvme: introduce helper function to get ctrl state - drm/exynos: fix a potential error pointer dereference - drm/exynos: fix a wrong error checking - clk: rockchip: rk3128: Fix HCLK_OTG gate register - jbd2: correct the printing of write_flags in jbd2_write_superblock() - drm/crtc: Fix uninit-value bug in drm_mode_setcrtc - neighbour: Don't let neigh_forced_gc() disable preemption for long - tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing - tracing: Add size check when printing trace_marker output - ring-buffer: Do not record in NMI if the arch does not support cmpxchg in NMI - reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning - Input: atkbd - skip ATKBD_CMD_GETID in translated mode - Input: i8042 - add nomux quirk for Acer P459-G2-M - s390/scm: fix virtual vs physical address confusion - ARC: fix spare error - Input: xpad - add Razer Wolverine V2 support - ARM: sun9i: smp: fix return code check of of_property_match_string - drm/crtc: fix uninitialized variable use - ACPI: resource: Add another DMI match for the TongFang GMxXGxx - binder: use EPOLLERR from eventpoll.h - binder: fix trivial typo of binder_free_buf_locked() - binder: fix comment on binder_alloc_new_buf() return value - uio: Fix use-after-free in uio_open - parport: parport_serial: Add Brainboxes BAR details - parport: parport_serial: Add Brainboxes device IDs and geometry - coresight: etm4x: Fix width of CCITMIN field - x86/lib: Fix overflow when counting digits - EDAC/thunderx: Fix possible out-of-bounds string access - powerpc: add crtsavres.o to always-y instead of extra-y - powerpc/44x: select I2C for CURRITUCK - powerpc/pseries/memhotplug: Quieten some DLPAR operations - powerpc/pseries/memhp: Fix access beyond end of drmem array - selftests/powerpc: Fix error handling in FPU/VMX preemption tests - powerpc/powernv: Add a null pointer check to scom_debug_init_one() - powerpc/powernv: Add a null pointer check in opal_event_init() - powerpc/powernv: Add a null pointer check in opal_powercap_init() - powerpc/imc-pmu: Add a null pointer check in update_events_in_group() - mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response - ACPI: video: check for error while searching for backlight
[Group.of.nepali.translators] [Bug 2055686] Re: Drop ABI checks from kernel build
This bug was fixed in the package linux - 5.4.0-176.196 --- linux (5.4.0-176.196) focal; urgency=medium * focal/linux: 5.4.0-176.196 -proposed tracker (LP: #2058756) * Problems with HVCS and hotplugging (LP: #2056373) - powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry - powerpc/pseries: Fix of_read_drc_info_cell() to point at next record - hvcs: Fix hvcs port reference counting - hvcs: Use dev_groups to manage hvcs device attributes - hvcs: Use driver groups to manage driver attributes - hvcs: Get reference to tty in remove - hvcs: Use vhangup in hotplug remove - hvcs: Synchronize hotplug remove with port free linux (5.4.0-175.195) focal; urgency=medium * focal/linux: 5.4.0-175.195 -proposed tracker (LP: #2055684) * Packaging resync (LP: #1786013) - [Packaging] drop ABI data - [Packaging] update annotations scripts - debian.master/dkms-versions -- update from kernel-versions (main/2024.03.04) * Drop ABI checks from kernel build (LP: #2055686) - [Packaging] Remove in-tree abi checks - [Packaging] Bring back install- prerequisite for checks- - [Packaging] Remove abi-check from final-checks * Cranky update-dkms-versions rollout (LP: #2055685) - [Packaging] remove update-dkms-versions - Move debian/dkms-versions to debian.master/dkms-versions - [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions - [Packaging] remove update-version-dkms * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094) - [Packaging] rules: Put usbip manpages in the correct directory * CVE-2024-23851 - dm ioctl: log an error if the ioctl structure is corrupted - dm: limit the number of targets and parameter size area * Focal update: v5.4.268 upstream stable release (LP: #2055075) - f2fs: explicitly null-terminate the xattr list - pinctrl: lochnagar: Don't build on MIPS - ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro - ASoC: Intel: Skylake: Fix mem leak in few functions - ASoC: nau8822: Fix incorrect type in assignment and cast to restricted __be16 - ASoC: Intel: Skylake: mem leak in skl register function - ASoC: cs43130: Fix the position of const qualifier - ASoC: cs43130: Fix incorrect frame delay configuration - ASoC: rt5650: add mutex to avoid the jack detection failure - nouveau/tu102: flush all pdbs on vmm flush - net/tg3: fix race condition in tg3_reset_task() - ASoC: da7219: Support low DC impedance headset - nvme: introduce helper function to get ctrl state - drm/exynos: fix a potential error pointer dereference - drm/exynos: fix a wrong error checking - clk: rockchip: rk3128: Fix HCLK_OTG gate register - jbd2: correct the printing of write_flags in jbd2_write_superblock() - drm/crtc: Fix uninit-value bug in drm_mode_setcrtc - neighbour: Don't let neigh_forced_gc() disable preemption for long - tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing - tracing: Add size check when printing trace_marker output - ring-buffer: Do not record in NMI if the arch does not support cmpxchg in NMI - reset: hisilicon: hi6220: fix Wvoid-pointer-to-enum-cast warning - Input: atkbd - skip ATKBD_CMD_GETID in translated mode - Input: i8042 - add nomux quirk for Acer P459-G2-M - s390/scm: fix virtual vs physical address confusion - ARC: fix spare error - Input: xpad - add Razer Wolverine V2 support - ARM: sun9i: smp: fix return code check of of_property_match_string - drm/crtc: fix uninitialized variable use - ACPI: resource: Add another DMI match for the TongFang GMxXGxx - binder: use EPOLLERR from eventpoll.h - binder: fix trivial typo of binder_free_buf_locked() - binder: fix comment on binder_alloc_new_buf() return value - uio: Fix use-after-free in uio_open - parport: parport_serial: Add Brainboxes BAR details - parport: parport_serial: Add Brainboxes device IDs and geometry - coresight: etm4x: Fix width of CCITMIN field - x86/lib: Fix overflow when counting digits - EDAC/thunderx: Fix possible out-of-bounds string access - powerpc: add crtsavres.o to always-y instead of extra-y - powerpc/44x: select I2C for CURRITUCK - powerpc/pseries/memhotplug: Quieten some DLPAR operations - powerpc/pseries/memhp: Fix access beyond end of drmem array - selftests/powerpc: Fix error handling in FPU/VMX preemption tests - powerpc/powernv: Add a null pointer check to scom_debug_init_one() - powerpc/powernv: Add a null pointer check in opal_event_init() - powerpc/powernv: Add a null pointer check in opal_powercap_init() - powerpc/imc-pmu: Add a null pointer check in update_events_in_group() - mtd: rawnand: Increment IFC_TIMEOUT_MSECS for nand controller response - ACPI: video: check for error while searching for backlight
[Group.of.nepali.translators] [Bug 1825755] Re: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files
This bug was fixed in the package apt-mirror - 0.5.4-1ubuntu0.22.04.1 --- apt-mirror (0.5.4-1ubuntu0.22.04.1) jammy; urgency=medium * Download cnf files (LP: #1825755) - Adds support for xz files - d/p/Support-for-xz-translations.patch - d/p/Download-cnf-Files.patch -- Heather Lemon Tue, 30 Jan 2024 22:50:26 + ** Changed in: apt-mirror (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825755 Title: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files Status in apt-mirror package in Ubuntu: Fix Released Status in apt-mirror source package in Xenial: Won't Fix Status in apt-mirror source package in Bionic: Won't Fix Status in apt-mirror source package in Eoan: Won't Fix Status in apt-mirror source package in Focal: Fix Committed Status in apt-mirror source package in Groovy: Won't Fix Status in apt-mirror source package in Jammy: Fix Released Bug description: [Impact] * since ubuntu disco, main repositories contains 'cnf' directory with 'Commands*' files. those files are compressed with xy, whereas apt- mirror 0.5.1 doesn't contain the patch which enable download of .xz compressed files * Without this update, users are not able to mirror newer releases of Ubuntu. [Test Case] * On any release of Ubuntu install apt-mirror and add this line to /etc/apt/mirror.list: deb http://archive.ubuntu.com/ubuntu eoan-updates main restricted universe multiverse * sync the mirror using `apt-mirror` * Attempt to run `apt update` against the mirror. The result will be similar to: ... Err:7 http://10.3.0.41/ubuntu eoan-updates/main amd64 c-n-f Metadata 404 Not Found [IP: 10.3.0.41 80] Ign:14 http://10.3.0.41/ubuntu eoan-updates/multiverse amd64 c-n-f Metadata Ign:15 http://10.3.0.41/ubuntu eoan-updates/universe amd64 c-n-f Metadata Ign:16 http://10.3.0.41/ubuntu eoan-updates/restricted amd64 c-n-f Metadata Reading package lists... Done E: Failed to fetch http://10.3.0.41/ubuntu/dists/eoan-updates/main/cnf/Commands-amd64 404 Not Found [IP: 10.3.0.41 80] E: Some index files failed to download. They have been ignored, or old ones used instead. ... * Updating the apt-mirror package from ppa:slashd/test and then re- running the `apt-mirror` command will then allow a successful `apt update`. [Regression Potential] * The regression potential is low since the package doesn't currently work properly anyway. * It's a patchset from a fork repo, if apt-mirror upstream becomes alive again in the future, it won't necessary mean that the fork will be commited/merged upstream, and Ubuntu package might differ from original upstream until next version bump. [Other informations] Upstream bug: https://github.com/apt-mirror/apt-mirror/issues/118 Not much update has been made since Upstream become inactive as noted from the output of rmadison: Since Bionic, it is a simple copy from release to active devel release and so on directly from debian, no patching whatsoever and nothing new to pull from Debian as well. Ubuntu apt-mirror | 0.5.1-1ubuntu1 | xenial/universe | source, all apt-mirror | 0.5.4-1 | bionic/universe | source, all apt-mirror | 0.5.4-1 | disco/universe | source, all apt-mirror | 0.5.4-1 | eoan/universe| source, all apt-mirror | 0.5.4-1 | focal/universe | source, all apt-mirror | 0.5.4-1 | groovy/universe | source, all Debian apt-mirror 0.5.4-1 is found in sid/unstable --- The required patchset is from a fork of upstream apt-mirror josbraden/apt-mirror (https://github.com/josbraden/apt-mirror) Note that upstream apt-mirror is not active anymore, and is looking for a new maintainer as published in their github page: https://github.com/apt-mirror/apt-mirror That's why we have to rely on the fork atm. The required patchset are (tested by Chris in the form of a test pkg: 0001-Copy-DEP-11-functions-for-editing.patch 0001-Replace-DEP-11-with-cnf-in-DEP-11-code-copy.patch 0001-Fix-Regex.patch 0001-Improve-regex-for-cnf-file-matching.patch 0001-Remove-dev-note.patch 0001-Fix-missing-parenthesis.patch I also talked with sil2100 (SRU verification team member) about the feasibilty of this SRU (from a fork repo): " Yeah, I'd say fixes from forked repositories in this case make sense Since there's no longer any 'one authority' for it. " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1825755/+subscriptions ___ Mailing list:
[Group.of.nepali.translators] [Bug 2015420] Re: motd: can't disable esm-related messages
This bug was fixed in the package update-notifier - 3.192.68build1 --- update-notifier (3.192.68build1) noble; urgency=medium * No-change rebuild against libglib2.0-0t64 -- Steve Langasek Mon, 11 Mar 2024 23:47:11 + ** Changed in: update-notifier (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2015420 Title: motd: can't disable esm-related messages Status in update-notifier package in Ubuntu: Fix Released Status in update-notifier source package in Xenial: Fix Released Status in update-notifier source package in Bionic: Fix Released Status in update-notifier source package in Focal: Fix Released Status in update-notifier source package in Jammy: Fix Released Bug description: [ Impact ] If ESM Infra/Apps is available for a system, users will always see messages related to those Ubuntu Pro services in their MOTDs. As stated in the original description, there have been complaints on how hard it is to disable those messages - we have users who don't want Pro and don't want to be reminded of Pro all the time. The fix here is making it easier for people to disable the ESM related messages in the update-related MOTD, by giving them a way to opt-out. Users will have the option to create the /var/lib/ubuntu- advantage/hide-esm-in-motd marker file, causing the /usr/lib/update- notifier/update-motd-updates-available script to include a --no-esm- messages flag when generating the outputs. This file is the same file used in the Pro Client to suppress those messages. [ Test Plan ] Compare the messages before and after installing the new version of the package, and make sure they are exactly the same in different scenarios: - ESM status: unavailable, disabled, enabled - LTS system: yes or no - updates available: yes or no Thankfully, the unit test suite in tests/test_motd.py covers all of those scenarios functionality-wise. Manual checks on real systems may endorse the functionality. New tests were added to the suite making sure the flag hides the ESM related messages when it is present. On real systems, creating the /var/lib/ubuntu-advantage/hide-esm-in- motd marker file and making sure to update the MOTDs should remove ESM related messages for the same scenarios above. The execution of the script relies on running one of a couple trigger hooks set in the apt configuration. Running `apt update` will trigger one of them. To make sure messages will be updated, the /var/lib/update-notifier/updates-available stamp file can be removed before the update. (The alternative would be running manually with --force, but that is slightly worse for acceptance testing) [ Where problems could occur ] - Other software may be relying on the apt-check script to generate human-readable messages. A mistake here could intefere with the message generated, changing expectation on stable releases, or causing errors. To mitigate that, the standard behavior is exactly the same if the marker file is absent, and all existing functionality is preserved. - Users may make mistakes when creating the marker file. We will mitigate that by having comprehensible documentation with a clear explanation of what the flag does and where to put it. The worst that can happen is that users create a useless file, and no change happens. [ Other Info ] As opposed to what was in the original description, the proposed changeset does not separate esm messages from the regular updates messages - this ensures current users and potential callers get exactly the same result when checking their outputs after the change lands. As suggested in the original description, we understand that it is not the easiest and straightforward approach create a specific file when compared to running a command or clicking a button. However, the messages are there for a product decision, and it is a product decision not to have a "too easy opt-out". On the other hand, users who want to disable this are capable of creating the file, and it will be way easier for them than making the changes in the python script itself - plus the configuration is kept between upgrades. As noted in a subsequent comment, the patch fixing this bug introduces a new help message. The translations of update-notifier are shipped together with the package. Consulting with @enr0n, the decision about this new entry is: - For the Noble version, @enr0n will add this new line to the pot file, so it can be translated for the future releases. - For the SRUs, we will let it be as is. The main two reasons are: 1. there is low value in translating this string to the couple languages we know, and new translations would require a new
[Group.of.nepali.translators] [Bug 2055046] Re: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log
This bug was fixed in the package ubuntu-advantage-tools - 31.2.2 --- ubuntu-advantage-tools (31.2.2) noble; urgency=medium * version.py: fix internal version to match ubuntu package version (it was missed in the previous upload, so 31.2.1 is "burned" now) -- Andreas Hasenack Sun, 24 Mar 2024 10:52:02 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2055046 Title: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage- license-check.log Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1, an old logrotate conffile named ubuntu-advantage-tools is left behind. The old file configures the same files as the new conffile: ubuntu-pro-client. The result is that when logrotate runs (on a daily timer) it has an error because two configurations for the same log files exist. This results in a "degraded" system status. The fix is to use the `mv_conffile` maintscript to remove the old ubuntu-advantage-tools logrotate conffile on upgrade. [ Test Plan ] We added a test to the ubuntu-pro-client integration test suite that covers this scenario. It upgrades to the new ubuntu-pro-client and then runs logrotate and checks that there are no errors. Because this is covered by the integration test suite, this bug will be verified as part of the verification process for LP: #2048921. [ Where problems could occur ] Touching conffiles is always risky. It could result in the removal of a needed config option or in an unnecessary debconf prompt on upgrade. I tested that user modifications were preserved on upgrade, but there is always the possibility that something could go wrong. [ Original Description ] Logrotate does not start due to misconfigured Ubuntu Pro: $ sudo systemctl status logrotate | cat × logrotate.service - Rotate log files Loaded: loaded (/usr/lib/systemd/system/logrotate.service; static) Active: failed (Result: exit-code) since Mon 2024-02-26 15:10:44 CET; 9s ago TriggeredBy: ● logrotate.timer Docs: man:logrotate(8) man:logrotate.conf(5) Process: 85798 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=1/FAILURE) Main PID: 85798 (code=exited, status=1/FAILURE) CPU: 69ms Feb 26 15:10:44 workstation5 systemd[1]: Starting logrotate.service - Rotate log files... Feb 26 15:10:44 workstation5 logrotate[85798]: error: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log Feb 26 15:10:44 workstation5 logrotate[85798]: error: found error in file ubuntu-pro-client, skipping Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Feb 26 15:10:44 workstation5 systemd[1]: logrotate.service: Failed with result 'exit-code'. Feb 26 15:10:44 workstation5 systemd[1]: Failed to start logrotate.service - Rotate log files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2055046/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2057937] Re: apt-news.service reporting errors after ubuntu-pro-client install
This bug was fixed in the package ubuntu-advantage-tools - 31.2.2 --- ubuntu-advantage-tools (31.2.2) noble; urgency=medium * version.py: fix internal version to match ubuntu package version (it was missed in the previous upload, so 31.2.1 is "burned" now) -- Andreas Hasenack Sun, 24 Mar 2024 10:52:02 -0300 ** Changed in: ubuntu-advantage-tools (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2057937 Title: apt-news.service reporting errors after ubuntu-pro-client install Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Triaged Status in ubuntu-advantage-tools source package in Bionic: Triaged Status in ubuntu-advantage-tools source package in Focal: Triaged Status in ubuntu-advantage-tools source package in Jammy: Triaged Status in ubuntu-advantage-tools source package in Mantic: Triaged Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [ Impact ] src:ubuntu-advantage-tools version 31 introduced[1] an apparmor profile to the apt-news service. It's known that some ubuntu systems do not have apparmor enabled, and this was considered. The systemd.exec(5) manpage states that the AppArmorProfile setting has no effect if apparmor is disabled[2]. This was tested and verified. Turns out, however, that apparmor can be enabled on a system, but without the apparmor package installed. When this package is not installed, no profiles are loaded. Crucially, the ubuntu_pro_apt_news profile, used by apt-news.service, is not loaded. This situation is different than "apparmor is disabled", and systemd will try to launch apt-news confined by ubuntu_pro_apt_news. But since that profile is not loaded into the kernel, the service will fail. apt-news.service is called as an apt update hook, but its failure does not fail apt, since it's guarded[3] by "|| true", i.e., failures in the hook are ignored. The only impact is that apt news won't be fetched. [ Test Plan ] The test plan will be in two parts. One to confirm the apt-news service won't fail to start if the apparmor profile is not available (it's what triggered this bug). The second part is to confirm that in the "good case", with apparmor available on the system, the confinement is still applied. a) To reproduce the problem, launch an ubuntu lxd container, or a VM, and: # install ubuntu-advantage-tools 31 or later. It's in updates right now, so just make sure the system is updated: sudo apt update && sudo apt install ubuntu-advantage-tools -y # verify it's version 31 or higher: $ dpkg -l ubuntu-advantage-tools | grep ubuntu-advantage-tools ii ubuntu-advantage-tools 31.2~22.04 all transitional dummy package for ubuntu-pro-client # remove (not purge) apparmor: sudo apt remove apparmor -y # reboot sudo reboot # start apt-news.service, and verify it fails: $ sudo systemctl start apt-news.service Job for apt-news.service failed because the control process exited with error code. See "systemctl status apt-news.service" and "journalctl -xeu apt-news.service" for details. # The log will show it's because it couldn't confine the service with the ubuntu_pro_apt_news profile: $ systemctl status apt-news.service × apt-news.service - Update APT News Loaded: loaded (/lib/systemd/system/apt-news.service; static) Active: failed (Result: exit-code) since Mon 2024-03-18 20:35:41 UTC; 35s ago Process: 263 ExecStart=/usr/bin/python3 /usr/lib/ubuntu-advantage/apt_news.py (code=exited, status=231/APPARMOR) Main PID: 263 (code=exited, status=231/APPARMOR) CPU: 7ms Mar 18 20:35:41 j systemd[1]: Starting Update APT News... Mar 18 20:35:41 j systemd[263]: apt-news.service: Failed to prepare AppArmor profile change to ubuntu_pro_apt_news: No such file or directory Mar 18 20:35:41 j systemd[263]: apt-news.service: Failed at step APPARMOR spawning /usr/bin/python3: No such file or directory Mar 18 20:35:41 j systemd[1]: apt-news.service: Main process exited, code=exited, status=231/APPARMOR Mar 18 20:35:41 j systemd[1]: apt-news.service: Failed with result 'exit-code'. Mar 18 20:35:41 j systemd[1]: Failed to start Update APT News. With the fixed package, the service will not fail to start. b) Continuing from the test plan above, now we will confirm that if apparmor is installed, that the apt-news service is run confined. * Install apparmor back again and reboot: $ sudo apt install apparmor -y $ sudo reboot * Confirm the apt-news profile is loaded and in enforce mode: $ sudo grep ubuntu_pro_apt_news /sys/kernel/security/apparmor/profiles
[Group.of.nepali.translators] [Bug 2058035] Re: [SRU] Create directories for apt configuration files if they are absent
This bug was fixed in the package software-properties - 0.99.44 --- software-properties (0.99.44) noble; urgency=medium * Handle backup and restore of deb822 sources (LP: #2053228) software-properties (0.99.43) noble; urgency=medium * Fix autopkgtest: Make sure directory exists before trying to create file in it (LP: #2058035). -- Julian Andres Klode Wed, 20 Mar 2024 13:18:16 +0100 ** Changed in: software-properties (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2058035 Title: [SRU] Create directories for apt configuration files if they are absent Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: Fix Committed Bug description: Impact -- The autopkgtest for 0.96.20.12, which introduces Ubuntu Pro in Xenial's software-properties, failed on Dbus tests[1]. The failure is because, at some point in time, the .keep file were removed from the otherwise empty tests/aptroot/etc/apt/apt.conf.d/. This caused the Git repository to drop tests/aptroot/etc/apt/apt.conf.d/ and also its parent, which also became empty, and the tests try to directly create files in those directories, raising the error. It seems that previous uploaders did not use the Git checkout, as the offending commit was introduced in Jun 2019 and there were subsequent uploads that did contain those empty directories. Test case - Trigger an autopkgtest against the proposed package version. It must succeed. Regression Potential Although the introduced change is idempotent, there could be other part of the code assuming the directories didn't exist and trying to create them with a "fail if already exists" approach, causing a runtime regression. [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- xenial/xenial/amd64/s/software- properties/20240301_100314_9e242@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2058035/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2015420] Re: motd: can't disable esm-related messages
This bug was fixed in the package update-notifier - 3.192.1.21 --- update-notifier (3.192.1.21) bionic; urgency=medium * update-motd: use a marker file to hide ESM messages (LP: #2015420) -- Renan Rodrigo Barbosa Mon, 04 Mar 2024 08:04:19 -0300 ** Changed in: update-notifier (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2015420 Title: motd: can't disable esm-related messages Status in update-notifier package in Ubuntu: In Progress Status in update-notifier source package in Xenial: Fix Released Status in update-notifier source package in Bionic: Fix Released Status in update-notifier source package in Focal: Fix Released Status in update-notifier source package in Jammy: Fix Released Bug description: [ Impact ] If ESM Infra/Apps is available for a system, users will always see messages related to those Ubuntu Pro services in their MOTDs. As stated in the original description, there have been complaints on how hard it is to disable those messages - we have users who don't want Pro and don't want to be reminded of Pro all the time. The fix here is making it easier for people to disable the ESM related messages in the update-related MOTD, by giving them a way to opt-out. Users will have the option to create the /var/lib/ubuntu- advantage/hide-esm-in-motd marker file, causing the /usr/lib/update- notifier/update-motd-updates-available script to include a --no-esm- messages flag when generating the outputs. This file is the same file used in the Pro Client to suppress those messages. [ Test Plan ] Compare the messages before and after installing the new version of the package, and make sure they are exactly the same in different scenarios: - ESM status: unavailable, disabled, enabled - LTS system: yes or no - updates available: yes or no Thankfully, the unit test suite in tests/test_motd.py covers all of those scenarios functionality-wise. Manual checks on real systems may endorse the functionality. New tests were added to the suite making sure the flag hides the ESM related messages when it is present. On real systems, creating the /var/lib/ubuntu-advantage/hide-esm-in- motd marker file and making sure to update the MOTDs should remove ESM related messages for the same scenarios above. The execution of the script relies on running one of a couple trigger hooks set in the apt configuration. Running `apt update` will trigger one of them. To make sure messages will be updated, the /var/lib/update-notifier/updates-available stamp file can be removed before the update. (The alternative would be running manually with --force, but that is slightly worse for acceptance testing) [ Where problems could occur ] - Other software may be relying on the apt-check script to generate human-readable messages. A mistake here could intefere with the message generated, changing expectation on stable releases, or causing errors. To mitigate that, the standard behavior is exactly the same if the marker file is absent, and all existing functionality is preserved. - Users may make mistakes when creating the marker file. We will mitigate that by having comprehensible documentation with a clear explanation of what the flag does and where to put it. The worst that can happen is that users create a useless file, and no change happens. [ Other Info ] As opposed to what was in the original description, the proposed changeset does not separate esm messages from the regular updates messages - this ensures current users and potential callers get exactly the same result when checking their outputs after the change lands. As suggested in the original description, we understand that it is not the easiest and straightforward approach create a specific file when compared to running a command or clicking a button. However, the messages are there for a product decision, and it is a product decision not to have a "too easy opt-out". On the other hand, users who want to disable this are capable of creating the file, and it will be way easier for them than making the changes in the python script itself - plus the configuration is kept between upgrades. As noted in a subsequent comment, the patch fixing this bug introduces a new help message. The translations of update-notifier are shipped together with the package. Consulting with @enr0n, the decision about this new entry is: - For the Noble version, @enr0n will add this new line to the pot file, so it can be translated for the future releases. - For the SRUs, we will let it be as is. The main two reasons are: 1. there is low value in translating this string to the couple languages we know, and new
[Group.of.nepali.translators] [Bug 2015420] Re: motd: can't disable esm-related messages
This bug was fixed in the package update-notifier - 3.192.30.19 --- update-notifier (3.192.30.19) focal; urgency=medium * update-motd: use a marker file to hide ESM messages (LP: #2015420) -- Renan Rodrigo Barbosa Mon, 04 Mar 2024 07:57:08 -0300 ** Changed in: update-notifier (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: update-notifier (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2015420 Title: motd: can't disable esm-related messages Status in update-notifier package in Ubuntu: In Progress Status in update-notifier source package in Xenial: Fix Released Status in update-notifier source package in Bionic: Fix Released Status in update-notifier source package in Focal: Fix Released Status in update-notifier source package in Jammy: Fix Released Bug description: [ Impact ] If ESM Infra/Apps is available for a system, users will always see messages related to those Ubuntu Pro services in their MOTDs. As stated in the original description, there have been complaints on how hard it is to disable those messages - we have users who don't want Pro and don't want to be reminded of Pro all the time. The fix here is making it easier for people to disable the ESM related messages in the update-related MOTD, by giving them a way to opt-out. Users will have the option to create the /var/lib/ubuntu- advantage/hide-esm-in-motd marker file, causing the /usr/lib/update- notifier/update-motd-updates-available script to include a --no-esm- messages flag when generating the outputs. This file is the same file used in the Pro Client to suppress those messages. [ Test Plan ] Compare the messages before and after installing the new version of the package, and make sure they are exactly the same in different scenarios: - ESM status: unavailable, disabled, enabled - LTS system: yes or no - updates available: yes or no Thankfully, the unit test suite in tests/test_motd.py covers all of those scenarios functionality-wise. Manual checks on real systems may endorse the functionality. New tests were added to the suite making sure the flag hides the ESM related messages when it is present. On real systems, creating the /var/lib/ubuntu-advantage/hide-esm-in- motd marker file and making sure to update the MOTDs should remove ESM related messages for the same scenarios above. The execution of the script relies on running one of a couple trigger hooks set in the apt configuration. Running `apt update` will trigger one of them. To make sure messages will be updated, the /var/lib/update-notifier/updates-available stamp file can be removed before the update. (The alternative would be running manually with --force, but that is slightly worse for acceptance testing) [ Where problems could occur ] - Other software may be relying on the apt-check script to generate human-readable messages. A mistake here could intefere with the message generated, changing expectation on stable releases, or causing errors. To mitigate that, the standard behavior is exactly the same if the marker file is absent, and all existing functionality is preserved. - Users may make mistakes when creating the marker file. We will mitigate that by having comprehensible documentation with a clear explanation of what the flag does and where to put it. The worst that can happen is that users create a useless file, and no change happens. [ Other Info ] As opposed to what was in the original description, the proposed changeset does not separate esm messages from the regular updates messages - this ensures current users and potential callers get exactly the same result when checking their outputs after the change lands. As suggested in the original description, we understand that it is not the easiest and straightforward approach create a specific file when compared to running a command or clicking a button. However, the messages are there for a product decision, and it is a product decision not to have a "too easy opt-out". On the other hand, users who want to disable this are capable of creating the file, and it will be way easier for them than making the changes in the python script itself - plus the configuration is kept between upgrades. As noted in a subsequent comment, the patch fixing this bug introduces a new help message. The translations of update-notifier are shipped together with the package. Consulting with @enr0n, the decision about this new entry is: - For the Noble version, @enr0n will add this new line to the pot file, so it can be translated for the future releases. - For the SRUs, we will let it be as is. The main two reasons are:
[Group.of.nepali.translators] [Bug 2015420] Re: motd: can't disable esm-related messages
This bug was fixed in the package update-notifier - 3.192.54.8 --- update-notifier (3.192.54.8) jammy; urgency=medium * update-motd: use a marker file to hide ESM messages (LP: #2015420) -- Renan Rodrigo Barbosa Mon, 04 Mar 2024 07:49:00 -0300 ** Changed in: update-notifier (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2015420 Title: motd: can't disable esm-related messages Status in update-notifier package in Ubuntu: In Progress Status in update-notifier source package in Xenial: Fix Released Status in update-notifier source package in Bionic: Fix Released Status in update-notifier source package in Focal: Fix Released Status in update-notifier source package in Jammy: Fix Released Bug description: [ Impact ] If ESM Infra/Apps is available for a system, users will always see messages related to those Ubuntu Pro services in their MOTDs. As stated in the original description, there have been complaints on how hard it is to disable those messages - we have users who don't want Pro and don't want to be reminded of Pro all the time. The fix here is making it easier for people to disable the ESM related messages in the update-related MOTD, by giving them a way to opt-out. Users will have the option to create the /var/lib/ubuntu- advantage/hide-esm-in-motd marker file, causing the /usr/lib/update- notifier/update-motd-updates-available script to include a --no-esm- messages flag when generating the outputs. This file is the same file used in the Pro Client to suppress those messages. [ Test Plan ] Compare the messages before and after installing the new version of the package, and make sure they are exactly the same in different scenarios: - ESM status: unavailable, disabled, enabled - LTS system: yes or no - updates available: yes or no Thankfully, the unit test suite in tests/test_motd.py covers all of those scenarios functionality-wise. Manual checks on real systems may endorse the functionality. New tests were added to the suite making sure the flag hides the ESM related messages when it is present. On real systems, creating the /var/lib/ubuntu-advantage/hide-esm-in- motd marker file and making sure to update the MOTDs should remove ESM related messages for the same scenarios above. The execution of the script relies on running one of a couple trigger hooks set in the apt configuration. Running `apt update` will trigger one of them. To make sure messages will be updated, the /var/lib/update-notifier/updates-available stamp file can be removed before the update. (The alternative would be running manually with --force, but that is slightly worse for acceptance testing) [ Where problems could occur ] - Other software may be relying on the apt-check script to generate human-readable messages. A mistake here could intefere with the message generated, changing expectation on stable releases, or causing errors. To mitigate that, the standard behavior is exactly the same if the marker file is absent, and all existing functionality is preserved. - Users may make mistakes when creating the marker file. We will mitigate that by having comprehensible documentation with a clear explanation of what the flag does and where to put it. The worst that can happen is that users create a useless file, and no change happens. [ Other Info ] As opposed to what was in the original description, the proposed changeset does not separate esm messages from the regular updates messages - this ensures current users and potential callers get exactly the same result when checking their outputs after the change lands. As suggested in the original description, we understand that it is not the easiest and straightforward approach create a specific file when compared to running a command or clicking a button. However, the messages are there for a product decision, and it is a product decision not to have a "too easy opt-out". On the other hand, users who want to disable this are capable of creating the file, and it will be way easier for them than making the changes in the python script itself - plus the configuration is kept between upgrades. As noted in a subsequent comment, the patch fixing this bug introduces a new help message. The translations of update-notifier are shipped together with the package. Consulting with @enr0n, the decision about this new entry is: - For the Noble version, @enr0n will add this new line to the pot file, so it can be translated for the future releases. - For the SRUs, we will let it be as is. The main two reasons are: 1. there is low value in translating this string to the couple languages we know, and new
[Group.of.nepali.translators] [Bug 1990450] Re: Show potential Ubuntu Pro updates and apt news messages
This bug was fixed in the package update-manager - 1:18.04.11.23 --- update-manager (1:18.04.11.23) bionic; urgency=medium * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). update-manager (1:18.04.11.22) bionic; urgency=medium * Add back removed widgets to UI file to fix crash when updating Upgrade Manager from inside itself (LP: #2045918). update-manager (1:18.04.11.21) bionic; urgency=medium * Fix incorrect available version for Ubuntu Pro updates in unattached case (LP: #2043425). update-manager (1:18.04.11.20) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - fix another linter error which was created while fixing a missing space in the previous upload... update-manager (1:18.04.11.19) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - Address linter errors that cause autopkgtest to fail. update-manager (1:18.04.11.18) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - Show Ubuntu Pro packages, whether the system is attached to Ubuntu Pro or not. - Replace Install now button by Enable Ubuntu Pro button when only Ubuntu Pro packages are available and the machine is not attached. - Fix checkbox and expander widget from overlapping. - Add News pane in a expander. - Replace notebook with Description and Changes tabs by a pane. update-manager (1:18.04.11.17) bionic; urgency=medium * Fix Ubuntu Pro updates checkbox and expander widget from overlapping (LP: #1990450) update-manager (1:18.04.11.16) bionic; urgency=medium * Update of the parsing for pro client changes (lp: #1990450) update-manager (1:18.04.11.15) bionic; urgency=medium * Show pending Ubuntu pro packages (LP: #1990450) update-manager (1:18.04.11.14) bionic; urgency=medium * tests/test_meta_release_core.py: switch a test from using lucid to bionic as precise was removed from the archive. (LP: #1929865) -- Nathan Pratta Teodosio Mon, 22 Jan 2024 21:36:03 +0100 ** Changed in: update-manager (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: update-manager (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1990450 Title: Show potential Ubuntu Pro updates and apt news messages Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Released Status in update-manager source package in Bionic: Fix Released Status in update-manager source package in Focal: Fix Released Status in update-manager source package in Jammy: Fix Released Status in update-manager source package in Kinetic: Fix Released Status in update-manager source package in Lunar: Won't Fix Status in update-manager source package in Mantic: Won't Fix Status in update-manager source package in Noble: Fix Released Bug description: [Impact] Show the Ubuntu Pro (aka Ubuntu Advantage) updates that would be enabled if you attached this machine. This information is not currently shown. The new revision also update the reference to the Software Properties' Livepatch tab which doesn't exist anymore since bug #2003527 and was replaced by Ubuntu Pro. There is also a new section 'News' showing the apt-news messages if there are any available and some layout changes to accommodate for the new section [Test Case] 1. Do fresh install of Ubuntu with available updates 2. Check there are updates available by running: $ pro security-status Note that updates are only available for older LTS releases. If there are no Pro specific updates available, install any package listed in https://esm.ubuntu.com/apps/ubuntu/dists/jammy-apps-security/main/binary-amd64/Packages (without attaching your machine!) 3. Open update-manager -> There should be a 'Ubuntu Pro security updates (Enable in Settings...)' section at the bottom of the updates list showing disabled and including under it the name of the packages that would be available if pro was enabled 4. start software-properties, go to the ubuntu pro tab and attach to a pro account 5. close software-properties and restart update-manager -> There should be a 'Ubuntu Pro security updates' section at the bottom of the updates list showing enabled and including under it packages updated provided by pro that can be installed 6. Check the top of the update-manager dialog If there is a message available on the server $ curl https://motd.ubuntu.com/aptnews.json with a
[Group.of.nepali.translators] [Bug 2043425] Re: Details pane against unavailable Pro updates is misleading
This bug was fixed in the package update-manager - 1:18.04.11.23 --- update-manager (1:18.04.11.23) bionic; urgency=medium * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). update-manager (1:18.04.11.22) bionic; urgency=medium * Add back removed widgets to UI file to fix crash when updating Upgrade Manager from inside itself (LP: #2045918). update-manager (1:18.04.11.21) bionic; urgency=medium * Fix incorrect available version for Ubuntu Pro updates in unattached case (LP: #2043425). update-manager (1:18.04.11.20) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - fix another linter error which was created while fixing a missing space in the previous upload... update-manager (1:18.04.11.19) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - Address linter errors that cause autopkgtest to fail. update-manager (1:18.04.11.18) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - Show Ubuntu Pro packages, whether the system is attached to Ubuntu Pro or not. - Replace Install now button by Enable Ubuntu Pro button when only Ubuntu Pro packages are available and the machine is not attached. - Fix checkbox and expander widget from overlapping. - Add News pane in a expander. - Replace notebook with Description and Changes tabs by a pane. update-manager (1:18.04.11.17) bionic; urgency=medium * Fix Ubuntu Pro updates checkbox and expander widget from overlapping (LP: #1990450) update-manager (1:18.04.11.16) bionic; urgency=medium * Update of the parsing for pro client changes (lp: #1990450) update-manager (1:18.04.11.15) bionic; urgency=medium * Show pending Ubuntu pro packages (LP: #1990450) update-manager (1:18.04.11.14) bionic; urgency=medium * tests/test_meta_release_core.py: switch a test from using lucid to bionic as precise was removed from the archive. (LP: #1929865) -- Nathan Pratta Teodosio Mon, 22 Jan 2024 21:36:03 +0100 ** Changed in: update-manager (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: update-manager (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2043425 Title: Details pane against unavailable Pro updates is misleading Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Released Status in update-manager source package in Bionic: Fix Released Status in update-manager source package in Focal: Fix Committed Status in update-manager source package in Jammy: Fix Released Status in update-manager source package in Noble: Fix Released Bug description: * Impact If Pro is not enabled, then the details pane against a Pro update misleads the user into believing that there is no update available. Example of someone being misled: https://inteltechniques.com/blog/2023/11/12/ubuntu-pro-shenanigans/ Expected results: either no details presented, or the actual details of the potential Pro update presented Actual results: a message that implies that there is no update available for this package, Pro or not. * Test Case Install the update on a system not attached to Pro, select an update in the Pro section, check the 'Version available' string, it should reflect the version that would be installed if pro was enabled * Regression potential The change is in the code getting the available version to display, if the logic was wrong it could lead to have the 'available version' label being missing or incorrect. The code could hit an exception if there was not non expected value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2043425/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2045918] Re: [SRU] Fix crash caused by updating update-manager from inside itself
This bug was fixed in the package update-manager - 1:18.04.11.23 --- update-manager (1:18.04.11.23) bionic; urgency=medium * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). update-manager (1:18.04.11.22) bionic; urgency=medium * Add back removed widgets to UI file to fix crash when updating Upgrade Manager from inside itself (LP: #2045918). update-manager (1:18.04.11.21) bionic; urgency=medium * Fix incorrect available version for Ubuntu Pro updates in unattached case (LP: #2043425). update-manager (1:18.04.11.20) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - fix another linter error which was created while fixing a missing space in the previous upload... update-manager (1:18.04.11.19) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - Address linter errors that cause autopkgtest to fail. update-manager (1:18.04.11.18) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - Show Ubuntu Pro packages, whether the system is attached to Ubuntu Pro or not. - Replace Install now button by Enable Ubuntu Pro button when only Ubuntu Pro packages are available and the machine is not attached. - Fix checkbox and expander widget from overlapping. - Add News pane in a expander. - Replace notebook with Description and Changes tabs by a pane. update-manager (1:18.04.11.17) bionic; urgency=medium * Fix Ubuntu Pro updates checkbox and expander widget from overlapping (LP: #1990450) update-manager (1:18.04.11.16) bionic; urgency=medium * Update of the parsing for pro client changes (lp: #1990450) update-manager (1:18.04.11.15) bionic; urgency=medium * Show pending Ubuntu pro packages (LP: #1990450) update-manager (1:18.04.11.14) bionic; urgency=medium * tests/test_meta_release_core.py: switch a test from using lucid to bionic as precise was removed from the archive. (LP: #1929865) -- Nathan Pratta Teodosio Mon, 22 Jan 2024 21:36:03 +0100 ** Changed in: update-manager (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2045918 Title: [SRU] Fix crash caused by updating update-manager from inside itself Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Released Status in update-manager source package in Bionic: Fix Released Status in update-manager source package in Focal: Fix Released Status in update-manager source package in Jammy: Fix Released Status in update-manager source package in Mantic: Won't Fix Bug description: Impact -- LP:1990450 introduced Ubuntu Pro updates and news to update-manager, but also a bug whereby updating update-manager itself while update- manager is running replaces its UI files with a version incompatible with the already running handle of update-manager, subsequently causing a crash when the latter references an widget existing only in the old UI file. In other words, update-manager crashes if the user tries installing the new update-manager release from inside itself. Even though updates would have been installed successfully at that point and subsequent runs of update-manager would not crash, the user is none the wiser and is most likely left worried about his resulting system state. Test case - 1. Have the old version of Update Manager installed and the proposed version available in the Apt database, such that, in Jammy for example, 'apt install --dry-run --verbose-versions' would report update-manager (1:22.04.9 => 1:22.04.19) 2. Start update-manager from a terminal. 3. Make sure 'Software Updater' is selected in the list. We don't care about any other package for this test. 4. Click 'Install now'. The installation must complete successfully and the view must be automatically recalculated. Verify that the application didn't crash (no tracebacks in the terminal window) and confirm with 'apt policy update-manager' that the new version was indeed installed. To note --- The recalculated view will not include references to Ubuntu Pro (neither news pane nor Ubuntu Pro updates section), as it is still the old version of the program that is running. Regression potential GTK is very finicky about its *.ui files; We must look out for other widgets failing to map or being relocated. Original report --- The Ubuntu Error Tracker has been receiving
[Group.of.nepali.translators] [Bug 2049785] Re: /usr/bin/update-manager:json.decoder.JSONDecodeError:/bin/update-manager@118:start_update:start_available:refresh_cache:_get_ua_security_status:load:loa
This bug was fixed in the package update-manager - 1:20.04.10.20 --- update-manager (1:20.04.10.20) focal; urgency=medium * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). update-manager (1:20.04.10.19) focal; urgency=medium * Add back removed widgets to UI file to fix crash when updating Upgrade Manager from inside itself (LP: #2045918). -- Nathan Pratta Teodosio Mon, 22 Jan 2024 21:32:17 +0100 ** Changed in: update-manager (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: update-manager (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2049785 Title: /usr/bin/update-manager:json.decoder.JSONDecodeError:/bin/update- manager@118:start_update:start_available:refresh_cache:_get_ua_security_status:load:loads:decode:raw_decode Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Released Status in update-manager source package in Bionic: Fix Released Status in update-manager source package in Focal: Fix Released Status in update-manager source package in Jammy: Fix Released Bug description: * Impact The new Ubuntu Pro integration hits an exception when the pro client call isn't returning a value json output * Test case Check that reports on https://errors.ubuntu.com/problem/741dff427bf59c3208da3b509caf1e8d2385fdea stop Also on a system not connected to pro, install an old ubuntu- advantage-tools 27 (outdated version), disconnect from internet and start update-manager, it should list the updates and not error out * Regression potential The code is changing the callback to get the list of pro updates to use the ubuntu-advantage-tools python API instead of calling the cmdline client. If there is an issue with the new API the pro updates listing on non pro-attached system could be incorrect or the client could hit a new exception -- In JournalErrors: ---> Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-91-generic=focal Cannot verify certificate of server Please check your openssl configuration. [info] A new version is available: 30~20.04 Please run: sudo apt-get install ubuntu-advantage-tools <--- Is it the ubuntu-advantage-tools version problem, is it the failure to access contracts.canonical.com? Should we switch to calling the API directly as in 24.04[1] or handle the exception? [1] https://code.launchpad.net/~nteodosio/update-manager/+git/update- manager/+merge/456088 -- The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:20.04.10.18, the problem page at https://errors.ubuntu.com/problem/741dff427bf59c3208da3b509caf1e8d2385fdea contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2049785/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2045918] Re: [SRU] Fix crash caused by updating update-manager from inside itself
This bug was fixed in the package update-manager - 1:20.04.10.20 --- update-manager (1:20.04.10.20) focal; urgency=medium * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). update-manager (1:20.04.10.19) focal; urgency=medium * Add back removed widgets to UI file to fix crash when updating Upgrade Manager from inside itself (LP: #2045918). -- Nathan Pratta Teodosio Mon, 22 Jan 2024 21:32:17 +0100 ** Changed in: update-manager (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: update-manager (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2045918 Title: [SRU] Fix crash caused by updating update-manager from inside itself Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Released Status in update-manager source package in Bionic: Fix Released Status in update-manager source package in Focal: Fix Released Status in update-manager source package in Jammy: Fix Released Status in update-manager source package in Mantic: Won't Fix Bug description: Impact -- LP:1990450 introduced Ubuntu Pro updates and news to update-manager, but also a bug whereby updating update-manager itself while update- manager is running replaces its UI files with a version incompatible with the already running handle of update-manager, subsequently causing a crash when the latter references an widget existing only in the old UI file. In other words, update-manager crashes if the user tries installing the new update-manager release from inside itself. Even though updates would have been installed successfully at that point and subsequent runs of update-manager would not crash, the user is none the wiser and is most likely left worried about his resulting system state. Test case - 1. Have the old version of Update Manager installed and the proposed version available in the Apt database, such that, in Jammy for example, 'apt install --dry-run --verbose-versions' would report update-manager (1:22.04.9 => 1:22.04.19) 2. Start update-manager from a terminal. 3. Make sure 'Software Updater' is selected in the list. We don't care about any other package for this test. 4. Click 'Install now'. The installation must complete successfully and the view must be automatically recalculated. Verify that the application didn't crash (no tracebacks in the terminal window) and confirm with 'apt policy update-manager' that the new version was indeed installed. To note --- The recalculated view will not include references to Ubuntu Pro (neither news pane nor Ubuntu Pro updates section), as it is still the old version of the program that is running. Regression potential GTK is very finicky about its *.ui files; We must look out for other widgets failing to map or being relocated. Original report --- The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:22.04.17, the problem page at https://errors.ubuntu.com/problem/7b4facc926a743e632733dcc290e7cd5623b6eb0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2045918/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2049785] Re: /usr/bin/update-manager:json.decoder.JSONDecodeError:/bin/update-manager@118:start_update:start_available:refresh_cache:_get_ua_security_status:load:loa
This bug was fixed in the package update-manager - 1:18.04.11.23 --- update-manager (1:18.04.11.23) bionic; urgency=medium * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). update-manager (1:18.04.11.22) bionic; urgency=medium * Add back removed widgets to UI file to fix crash when updating Upgrade Manager from inside itself (LP: #2045918). update-manager (1:18.04.11.21) bionic; urgency=medium * Fix incorrect available version for Ubuntu Pro updates in unattached case (LP: #2043425). update-manager (1:18.04.11.20) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - fix another linter error which was created while fixing a missing space in the previous upload... update-manager (1:18.04.11.19) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - Address linter errors that cause autopkgtest to fail. update-manager (1:18.04.11.18) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - Show Ubuntu Pro packages, whether the system is attached to Ubuntu Pro or not. - Replace Install now button by Enable Ubuntu Pro button when only Ubuntu Pro packages are available and the machine is not attached. - Fix checkbox and expander widget from overlapping. - Add News pane in a expander. - Replace notebook with Description and Changes tabs by a pane. update-manager (1:18.04.11.17) bionic; urgency=medium * Fix Ubuntu Pro updates checkbox and expander widget from overlapping (LP: #1990450) update-manager (1:18.04.11.16) bionic; urgency=medium * Update of the parsing for pro client changes (lp: #1990450) update-manager (1:18.04.11.15) bionic; urgency=medium * Show pending Ubuntu pro packages (LP: #1990450) update-manager (1:18.04.11.14) bionic; urgency=medium * tests/test_meta_release_core.py: switch a test from using lucid to bionic as precise was removed from the archive. (LP: #1929865) -- Nathan Pratta Teodosio Mon, 22 Jan 2024 21:36:03 +0100 ** Changed in: update-manager (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2049785 Title: /usr/bin/update-manager:json.decoder.JSONDecodeError:/bin/update- manager@118:start_update:start_available:refresh_cache:_get_ua_security_status:load:loads:decode:raw_decode Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Released Status in update-manager source package in Bionic: Fix Released Status in update-manager source package in Focal: Fix Released Status in update-manager source package in Jammy: Fix Released Bug description: * Impact The new Ubuntu Pro integration hits an exception when the pro client call isn't returning a value json output * Test case Check that reports on https://errors.ubuntu.com/problem/741dff427bf59c3208da3b509caf1e8d2385fdea stop Also on a system not connected to pro, install an old ubuntu- advantage-tools 27 (outdated version), disconnect from internet and start update-manager, it should list the updates and not error out * Regression potential The code is changing the callback to get the list of pro updates to use the ubuntu-advantage-tools python API instead of calling the cmdline client. If there is an issue with the new API the pro updates listing on non pro-attached system could be incorrect or the client could hit a new exception -- In JournalErrors: ---> Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-91-generic=focal Cannot verify certificate of server Please check your openssl configuration. [info] A new version is available: 30~20.04 Please run: sudo apt-get install ubuntu-advantage-tools <--- Is it the ubuntu-advantage-tools version problem, is it the failure to access contracts.canonical.com? Should we switch to calling the API directly as in 24.04[1] or handle the exception? [1] https://code.launchpad.net/~nteodosio/update-manager/+git/update- manager/+merge/456088 -- The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:20.04.10.18, the problem page at https://errors.ubuntu.com/problem/741dff427bf59c3208da3b509caf1e8d2385fdea contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access
[Group.of.nepali.translators] [Bug 2051115] Re: ubuntu pro integration interferes with dist-upgrade prompting
This bug was fixed in the package update-manager - 1:20.04.10.20 --- update-manager (1:20.04.10.20) focal; urgency=medium * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). update-manager (1:20.04.10.19) focal; urgency=medium * Add back removed widgets to UI file to fix crash when updating Upgrade Manager from inside itself (LP: #2045918). -- Nathan Pratta Teodosio Mon, 22 Jan 2024 21:32:17 +0100 ** Changed in: update-manager (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: update-manager (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2051115 Title: ubuntu pro integration interferes with dist-upgrade prompting Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Released Status in update-manager source package in Bionic: Fix Released Status in update-manager source package in Focal: Fix Released Status in update-manager source package in Jammy: Fix Released Status in update-manager source package in Noble: Fix Released Bug description: The listing of Ubuntu Pro packages has been introduced in recent versions of update-manager, but as an undesired consequence, in up to date machines unattached to Ubuntu Pro, update-manager stopped prompting to upgrade to a next supported release. Ubuntu Pro packages should be merely an addition to this program and not alter its main behavior. [Test plan] ---> ua detach --assume-yes apt update apt upgrade apt install hello update-manager <--- Instead of listing Ubuntu Pro packages (the hello one, for example, always has a ESM update) that would be installable if the user attached to Ubuntu Pro, the update-manager window should simply do as it did in older versions, namely, state that software is up to date, and, if a newer LTS is available, suggest to the user to update to it. [Where problems could occur] The Pro packages should still be listed as such (i.e. under their own section, "Ubuntu Pro security updates", in the package listing) in case there is at least one upgradable package (as of 'apt list --upgradable'), whether the machine is attached, in which case the Ubuntu Pro section is sensitive, or unattached to Ubuntu Pro, in which case it is insensitive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2051115/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2051115] Re: ubuntu pro integration interferes with dist-upgrade prompting
This bug was fixed in the package update-manager - 1:18.04.11.23 --- update-manager (1:18.04.11.23) bionic; urgency=medium * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). update-manager (1:18.04.11.22) bionic; urgency=medium * Add back removed widgets to UI file to fix crash when updating Upgrade Manager from inside itself (LP: #2045918). update-manager (1:18.04.11.21) bionic; urgency=medium * Fix incorrect available version for Ubuntu Pro updates in unattached case (LP: #2043425). update-manager (1:18.04.11.20) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - fix another linter error which was created while fixing a missing space in the previous upload... update-manager (1:18.04.11.19) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - Address linter errors that cause autopkgtest to fail. update-manager (1:18.04.11.18) bionic; urgency=medium * Ubuntu Pro (LP: #1990450): - Show Ubuntu Pro packages, whether the system is attached to Ubuntu Pro or not. - Replace Install now button by Enable Ubuntu Pro button when only Ubuntu Pro packages are available and the machine is not attached. - Fix checkbox and expander widget from overlapping. - Add News pane in a expander. - Replace notebook with Description and Changes tabs by a pane. update-manager (1:18.04.11.17) bionic; urgency=medium * Fix Ubuntu Pro updates checkbox and expander widget from overlapping (LP: #1990450) update-manager (1:18.04.11.16) bionic; urgency=medium * Update of the parsing for pro client changes (lp: #1990450) update-manager (1:18.04.11.15) bionic; urgency=medium * Show pending Ubuntu pro packages (LP: #1990450) update-manager (1:18.04.11.14) bionic; urgency=medium * tests/test_meta_release_core.py: switch a test from using lucid to bionic as precise was removed from the archive. (LP: #1929865) -- Nathan Pratta Teodosio Mon, 22 Jan 2024 21:36:03 +0100 ** Changed in: update-manager (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2051115 Title: ubuntu pro integration interferes with dist-upgrade prompting Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Released Status in update-manager source package in Bionic: Fix Released Status in update-manager source package in Focal: Fix Released Status in update-manager source package in Jammy: Fix Released Status in update-manager source package in Noble: Fix Released Bug description: The listing of Ubuntu Pro packages has been introduced in recent versions of update-manager, but as an undesired consequence, in up to date machines unattached to Ubuntu Pro, update-manager stopped prompting to upgrade to a next supported release. Ubuntu Pro packages should be merely an addition to this program and not alter its main behavior. [Test plan] ---> ua detach --assume-yes apt update apt upgrade apt install hello update-manager <--- Instead of listing Ubuntu Pro packages (the hello one, for example, always has a ESM update) that would be installable if the user attached to Ubuntu Pro, the update-manager window should simply do as it did in older versions, namely, state that software is up to date, and, if a newer LTS is available, suggest to the user to update to it. [Where problems could occur] The Pro packages should still be listed as such (i.e. under their own section, "Ubuntu Pro security updates", in the package listing) in case there is at least one upgradable package (as of 'apt list --upgradable'), whether the machine is attached, in which case the Ubuntu Pro section is sensitive, or unattached to Ubuntu Pro, in which case it is insensitive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2051115/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2049785] Re: /usr/bin/update-manager:json.decoder.JSONDecodeError:/bin/update-manager@118:start_update:start_available:refresh_cache:_get_ua_security_status:load:loa
This bug was fixed in the package update-manager - 1:22.04.19 --- update-manager (1:22.04.19) jammy; urgency=medium * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). -- Nathan Pratta Teodosio Fri, 26 Jan 2024 15:10:31 +0100 ** Changed in: update-manager (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2049785 Title: /usr/bin/update-manager:json.decoder.JSONDecodeError:/bin/update- manager@118:start_update:start_available:refresh_cache:_get_ua_security_status:load:loads:decode:raw_decode Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Committed Status in update-manager source package in Bionic: Fix Committed Status in update-manager source package in Focal: Fix Committed Status in update-manager source package in Jammy: Fix Released Bug description: * Impact The new Ubuntu Pro integration hits an exception when the pro client call isn't returning a value json output * Test case Check that reports on https://errors.ubuntu.com/problem/741dff427bf59c3208da3b509caf1e8d2385fdea stop Also on a system not connected to pro, install an old ubuntu- advantage-tools 27 (outdated version), disconnect from internet and start update-manager, it should list the updates and not error out * Regression potential The code is changing the callback to get the list of pro updates to use the ubuntu-advantage-tools python API instead of calling the cmdline client. If there is an issue with the new API the pro updates listing on non pro-attached system could be incorrect or the client could hit a new exception -- In JournalErrors: ---> Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-91-generic=focal Cannot verify certificate of server Please check your openssl configuration. [info] A new version is available: 30~20.04 Please run: sudo apt-get install ubuntu-advantage-tools <--- Is it the ubuntu-advantage-tools version problem, is it the failure to access contracts.canonical.com? Should we switch to calling the API directly as in 24.04[1] or handle the exception? [1] https://code.launchpad.net/~nteodosio/update-manager/+git/update- manager/+merge/456088 -- The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:20.04.10.18, the problem page at https://errors.ubuntu.com/problem/741dff427bf59c3208da3b509caf1e8d2385fdea contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2049785/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2051115] Re: ubuntu pro integration interferes with dist-upgrade prompting
This bug was fixed in the package update-manager - 1:22.04.19 --- update-manager (1:22.04.19) jammy; urgency=medium * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). -- Nathan Pratta Teodosio Fri, 26 Jan 2024 15:10:31 +0100 ** Changed in: update-manager (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2051115 Title: ubuntu pro integration interferes with dist-upgrade prompting Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Committed Status in update-manager source package in Bionic: Fix Committed Status in update-manager source package in Focal: Fix Committed Status in update-manager source package in Jammy: Fix Released Status in update-manager source package in Noble: Fix Released Bug description: The listing of Ubuntu Pro packages has been introduced in recent versions of update-manager, but as an undesired consequence, in up to date machines unattached to Ubuntu Pro, update-manager stopped prompting to upgrade to a next supported release. Ubuntu Pro packages should be merely an addition to this program and not alter its main behavior. [Test plan] ---> ua detach --assume-yes apt update apt upgrade apt install hello update-manager <--- Instead of listing Ubuntu Pro packages (the hello one, for example, always has a ESM update) that would be installable if the user attached to Ubuntu Pro, the update-manager window should simply do as it did in older versions, namely, state that software is up to date, and, if a newer LTS is available, suggest to the user to update to it. [Where problems could occur] The Pro packages should still be listed as such (i.e. under their own section, "Ubuntu Pro security updates", in the package listing) in case there is at least one upgradable package (as of 'apt list --upgradable'), whether the machine is attached, in which case the Ubuntu Pro section is sensitive, or unattached to Ubuntu Pro, in which case it is insensitive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2051115/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2044657] Re: Multiple data corruption issues in zfs
This bug was fixed in the package zfs-linux - 2.1.5-1ubuntu6~22.04.3
---
zfs-linux (2.1.5-1ubuntu6~22.04.3) jammy; urgency=medium
* d/p/77b0c6f0403b2b7d145bf6c244b6acbc757ccdc9.patch Cherry-pick
"dnode_is_dirty: check dnode and its data for dirtiness" fix from
zfs-2.1.14. LP: #2044657
-- Dimitri John Ledkov Wed, 31 Jan 2024
14:32:34 +
** Changed in: zfs-linux (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: zfs-linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Jammy:
Fix Released
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2019997] Re: pro livepatch status incorrect when run as normal user
This bug was fixed in the package ubuntu-advantage-tools - 31.2~18.04 --- ubuntu-advantage-tools (31.2~18.04) bionic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2019997 Title: pro livepatch status incorrect when run as normal user Status in Canonical Livepatch Client: New Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] pro status shows livepatch as "disabled" when "canonical-livepatch" returns an error. This can be misleading. It would be more helpful to propagate the error message up to the user through pro status; that is what the fix does. [ Test Plan ] In a multipass VM: ``` # attach to pro sudo pro attach # hack canonical-livepatch to return an error cat > error.sh <&2 false EOF chmod +x error.sh sudo rm /snap/bin/canonical-livepatch sudo ln -s /home/ubuntu/error.sh /snap/bin/canonical-livepatch # check livepatch's status according to pro pro status ``` Without the fix, livepatch will show as "disabled". With the fix,
[Group.of.nepali.translators] [Bug 2043836] Re: /usr/bin/ubuntu-advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_
This bug was fixed in the package ubuntu-advantage-tools - 31.2~18.04 --- ubuntu-advantage-tools (31.2~18.04) bionic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2043836 Title: /usr/bin/ubuntu- advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_pkg_cache:get_last_known_candidate:get_pkg_candidate_version:__enter__:get_apt_pkg_cache:/usr/bin/ubuntu- advantage@33:wrapper:_warn_about_new_version:check_for_new_version:get_last_known_candidate Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Lunar: Won't Fix Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] When apt cannot be run as a normal user, and a pro command is run as a normal user, a bug occurs in the error handling. An UnboundLocalError occurs. The fix is to give that variable an initial value so that it is not unbound during the error handling. [ Test Plan ] lxc launch ubuntu-daily:jammy test lxc shell test #
[Group.of.nepali.translators] [Bug 2019997] Re: pro livepatch status incorrect when run as normal user
This bug was fixed in the package ubuntu-advantage-tools - 31.2~22.04 --- ubuntu-advantage-tools (31.2~22.04) jammy; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: ubuntu-advantage-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2019997 Title: pro livepatch status incorrect when run as normal user Status in Canonical Livepatch Client: New Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] pro status shows livepatch as "disabled" when "canonical-livepatch" returns an error. This can be misleading. It would be more helpful to propagate the error message up to the user through pro status; that is what the fix does. [ Test Plan ] In a multipass VM: ``` # attach to pro sudo pro attach # hack canonical-livepatch to return an error cat > error.sh <&2 false EOF chmod +x error.sh sudo rm /snap/bin/canonical-livepatch sudo ln -s /home/ubuntu/error.sh /snap/bin/canonical-livepatch # check livepatch's status according to
[Group.of.nepali.translators] [Bug 2019997] Re: pro livepatch status incorrect when run as normal user
This bug was fixed in the package ubuntu-advantage-tools - 31.2~20.04 --- ubuntu-advantage-tools (31.2~20.04) focal; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2019997 Title: pro livepatch status incorrect when run as normal user Status in Canonical Livepatch Client: New Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] pro status shows livepatch as "disabled" when "canonical-livepatch" returns an error. This can be misleading. It would be more helpful to propagate the error message up to the user through pro status; that is what the fix does. [ Test Plan ] In a multipass VM: ``` # attach to pro sudo pro attach # hack canonical-livepatch to return an error cat > error.sh <&2 false EOF chmod +x error.sh sudo rm /snap/bin/canonical-livepatch sudo ln -s /home/ubuntu/error.sh /snap/bin/canonical-livepatch # check livepatch's status according to pro pro status ``` Without the fix, livepatch will show as "disabled". With the fix,
[Group.of.nepali.translators] [Bug 2021988] Re: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé
This bug was fixed in the package ubuntu-advantage-tools - 31.2~20.04 --- ubuntu-advantage-tools (31.2~20.04) focal; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2021988 Title: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé un état de sortie d'erreur 1 Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] If somehow the prerm script ran while the Depends of u-a-t weren't installed, then it would crash. More generally, the prerm script is unnecessarily bloated by using python and importing many modules it doesn't use. The fix reimplements the python function from the old prerm in shell. This avoids running python at all. [ Test Plan ] In a lxd container: 1. interfere with the python3-apt installation somehow (e.g. `rm -rf /usr/lib/python3/dist-packages/apt`) 2. execute the u-a-t.prerm script `apt remove ubuntu-advantage-tools` Without the fix, you'll
[Group.of.nepali.translators] [Bug 2021988] Re: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé
This bug was fixed in the package ubuntu-advantage-tools - 31.2~18.04 --- ubuntu-advantage-tools (31.2~18.04) bionic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2021988 Title: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé un état de sortie d'erreur 1 Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] If somehow the prerm script ran while the Depends of u-a-t weren't installed, then it would crash. More generally, the prerm script is unnecessarily bloated by using python and importing many modules it doesn't use. The fix reimplements the python function from the old prerm in shell. This avoids running python at all. [ Test Plan ] In a lxd container: 1. interfere with the python3-apt installation somehow (e.g. `rm -rf /usr/lib/python3/dist-packages/apt`) 2. execute the u-a-t.prerm script `apt remove ubuntu-advantage-tools` Without the fix,
[Group.of.nepali.translators] [Bug 2048921] Re: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic
This bug was fixed in the package ubuntu-advantage-tools - 31.2~18.04 --- ubuntu-advantage-tools (31.2~18.04) bionic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2048921 Title: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] This release brings both bug-fixes and new features for the Pro Client, and we would like to make sure all of our supported customers have access to these improvements on all releases. The most important changes are: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach - introduce new ubuntu_pro_apt_news apparmor policy - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" - enable: + use deb822 apt source file format when on noble or later - landscape:
[Group.of.nepali.translators] [Bug 2021988] Re: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé
This bug was fixed in the package ubuntu-advantage-tools - 31.2~22.04 --- ubuntu-advantage-tools (31.2~22.04) jammy; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: ubuntu-advantage-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2021988 Title: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé un état de sortie d'erreur 1 Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] If somehow the prerm script ran while the Depends of u-a-t weren't installed, then it would crash. More generally, the prerm script is unnecessarily bloated by using python and importing many modules it doesn't use. The fix reimplements the python function from the old prerm in shell. This avoids running python at all. [ Test Plan ] In a lxd container: 1. interfere with the python3-apt installation somehow (e.g. `rm -rf /usr/lib/python3/dist-packages/apt`)
[Group.of.nepali.translators] [Bug 2043836] Re: /usr/bin/ubuntu-advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_
This bug was fixed in the package ubuntu-advantage-tools - 31.2~20.04 --- ubuntu-advantage-tools (31.2~20.04) focal; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2043836 Title: /usr/bin/ubuntu- advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_pkg_cache:get_last_known_candidate:get_pkg_candidate_version:__enter__:get_apt_pkg_cache:/usr/bin/ubuntu- advantage@33:wrapper:_warn_about_new_version:check_for_new_version:get_last_known_candidate Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Lunar: Won't Fix Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] When apt cannot be run as a normal user, and a pro command is run as a normal user, a bug occurs in the error handling. An UnboundLocalError occurs. The fix is to give that variable an initial value so that it is not unbound during the error handling. [ Test Plan ] lxc launch ubuntu-daily:jammy test lxc shell test #
[Group.of.nepali.translators] [Bug 2043836] Re: /usr/bin/ubuntu-advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_
This bug was fixed in the package ubuntu-advantage-tools - 31.2~22.04 --- ubuntu-advantage-tools (31.2~22.04) jammy; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: ubuntu-advantage-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2043836 Title: /usr/bin/ubuntu- advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_pkg_cache:get_last_known_candidate:get_pkg_candidate_version:__enter__:get_apt_pkg_cache:/usr/bin/ubuntu- advantage@33:wrapper:_warn_about_new_version:check_for_new_version:get_last_known_candidate Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Lunar: Won't Fix Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] When apt cannot be run as a normal user, and a pro command is run as a normal user, a bug occurs in the error handling. An UnboundLocalError occurs. The fix is to give that variable an initial value so that it is not unbound
[Group.of.nepali.translators] [Bug 2048921] Re: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic
This bug was fixed in the package ubuntu-advantage-tools - 31.2~20.04 --- ubuntu-advantage-tools (31.2~20.04) focal; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2048921 Title: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] This release brings both bug-fixes and new features for the Pro Client, and we would like to make sure all of our supported customers have access to these improvements on all releases. The most important changes are: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach - introduce new ubuntu_pro_apt_news apparmor policy - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" - enable: + use deb822 apt source file format when on noble or later - landscape:
[Group.of.nepali.translators] [Bug 2050022] Re: Cannot run apt after installation if attached to Ubuntu Pro
This bug was fixed in the package ubuntu-advantage-tools - 31.2~18.04 --- ubuntu-advantage-tools (31.2~18.04) bionic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2050022 Title: Cannot run apt after installation if attached to Ubuntu Pro Status in subiquity: Invalid Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ ubuntu-advantage-tools SRU info ] [ Impact ] If ubuntu-advantage-tools (u-a-t) is not already installed, but cloud- init user-data includes "ubuntu_advantage" configuration data, then cloud-init will try to install u-a-t. On install, u-a-t needs to start ubuntu-advantage.service. ubuntu-advantage.service is ordered After=cloud-config.service. This results in deadlock, preventing apt from ever finishing. The apt lock is held forever and cloud-init never continues. The fix is to break the deadlock by removing the "After=cloud- config.service" ordering dependency from ubuntu-advantage.service. ubuntu-advantage.service should still wait until
[Group.of.nepali.translators] [Bug 2048921] Re: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic
This bug was fixed in the package ubuntu-advantage-tools - 31.2~22.04 --- ubuntu-advantage-tools (31.2~22.04) jammy; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: ubuntu-advantage-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2048921 Title: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] This release brings both bug-fixes and new features for the Pro Client, and we would like to make sure all of our supported customers have access to these improvements on all releases. The most important changes are: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach - introduce new ubuntu_pro_apt_news apparmor policy - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include
[Group.of.nepali.translators] [Bug 2050022] Re: Cannot run apt after installation if attached to Ubuntu Pro
This bug was fixed in the package ubuntu-advantage-tools - 31.2~20.04 --- ubuntu-advantage-tools (31.2~20.04) focal; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2050022 Title: Cannot run apt after installation if attached to Ubuntu Pro Status in subiquity: Invalid Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ ubuntu-advantage-tools SRU info ] [ Impact ] If ubuntu-advantage-tools (u-a-t) is not already installed, but cloud- init user-data includes "ubuntu_advantage" configuration data, then cloud-init will try to install u-a-t. On install, u-a-t needs to start ubuntu-advantage.service. ubuntu-advantage.service is ordered After=cloud-config.service. This results in deadlock, preventing apt from ever finishing. The apt lock is held forever and cloud-init never continues. The fix is to break the deadlock by removing the "After=cloud- config.service" ordering dependency from ubuntu-advantage.service. ubuntu-advantage.service should still wait until
[Group.of.nepali.translators] [Bug 2050022] Re: Cannot run apt after installation if attached to Ubuntu Pro
This bug was fixed in the package ubuntu-advantage-tools - 31.2~22.04 --- ubuntu-advantage-tools (31.2~22.04) jammy; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: ubuntu-advantage-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2050022 Title: Cannot run apt after installation if attached to Ubuntu Pro Status in subiquity: Invalid Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ ubuntu-advantage-tools SRU info ] [ Impact ] If ubuntu-advantage-tools (u-a-t) is not already installed, but cloud- init user-data includes "ubuntu_advantage" configuration data, then cloud-init will try to install u-a-t. On install, u-a-t needs to start ubuntu-advantage.service. ubuntu-advantage.service is ordered After=cloud-config.service. This results in deadlock, preventing apt from ever finishing. The apt lock is held forever and cloud-init never continues. The fix is to break the deadlock by removing the "After=cloud- config.service" ordering
[Group.of.nepali.translators] [Bug 2055046] Re: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log
This bug was fixed in the package ubuntu-advantage-tools - 31.2~18.04 --- ubuntu-advantage-tools (31.2~18.04) bionic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2055046 Title: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage- license-check.log Status in ubuntu-advantage-tools package in Ubuntu: Confirmed Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1, an old logrotate conffile named ubuntu-advantage-tools is left behind. The old file configures the same files as the new conffile: ubuntu-pro-client. The result is that when logrotate runs (on a daily timer) it has an error because two configurations for the same log files exist. This results in a "degraded" system status. The fix is to use the `mv_conffile` maintscript to remove the old ubuntu-advantage-tools logrotate conffile on upgrade. [ Test Plan ] We added a test to the ubuntu-pro-client integration test suite that covers this scenario. It upgrades to the new
[Group.of.nepali.translators] [Bug 2055046] Re: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log
This bug was fixed in the package ubuntu-advantage-tools - 31.2~20.04 --- ubuntu-advantage-tools (31.2~20.04) focal; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2055046 Title: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage- license-check.log Status in ubuntu-advantage-tools package in Ubuntu: Confirmed Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1, an old logrotate conffile named ubuntu-advantage-tools is left behind. The old file configures the same files as the new conffile: ubuntu-pro-client. The result is that when logrotate runs (on a daily timer) it has an error because two configurations for the same log files exist. This results in a "degraded" system status. The fix is to use the `mv_conffile` maintscript to remove the old ubuntu-advantage-tools logrotate conffile on upgrade. [ Test Plan ] We added a test to the ubuntu-pro-client integration test suite that covers this scenario. It upgrades to the new
[Group.of.nepali.translators] [Bug 2055046] Re: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log
This bug was fixed in the package ubuntu-advantage-tools - 31.2~22.04 --- ubuntu-advantage-tools (31.2~22.04) jammy; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: ubuntu-advantage-tools (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2055046 Title: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage- license-check.log Status in ubuntu-advantage-tools package in Ubuntu: Confirmed Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1, an old logrotate conffile named ubuntu-advantage-tools is left behind. The old file configures the same files as the new conffile: ubuntu-pro-client. The result is that when logrotate runs (on a daily timer) it has an error because two configurations for the same log files exist. This results in a "degraded" system status. The fix is to use the `mv_conffile` maintscript to remove the old ubuntu-advantage-tools logrotate conffile on upgrade. [ Test Plan ] We added a test to the
[Group.of.nepali.translators] [Bug 2019997] Re: pro livepatch status incorrect when run as normal user
This bug was fixed in the package ubuntu-advantage-tools - 31.2~23.10 --- ubuntu-advantage-tools (31.2~23.10) mantic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2019997 Title: pro livepatch status incorrect when run as normal user Status in Canonical Livepatch Client: New Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] pro status shows livepatch as "disabled" when "canonical-livepatch" returns an error. This can be misleading. It would be more helpful to propagate the error message up to the user through pro status; that is what the fix does. [ Test Plan ] In a multipass VM: ``` # attach to pro sudo pro attach # hack canonical-livepatch to return an error cat > error.sh <&2 false EOF chmod +x error.sh sudo rm /snap/bin/canonical-livepatch sudo ln -s /home/ubuntu/error.sh /snap/bin/canonical-livepatch # check livepatch's status according to pro pro status ``` Without the fix, livepatch will show as "disabled". With the fix,
[Group.of.nepali.translators] [Bug 2021988] Re: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé
This bug was fixed in the package ubuntu-advantage-tools - 31.2~23.10 --- ubuntu-advantage-tools (31.2~23.10) mantic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2021988 Title: package ubuntu-advantage-tools 27.14.4 failed to install/upgrade: le sous-processus paquet ubuntu-advantage-tools script pre-removal installé a renvoyé un état de sortie d'erreur 1 Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] If somehow the prerm script ran while the Depends of u-a-t weren't installed, then it would crash. More generally, the prerm script is unnecessarily bloated by using python and importing many modules it doesn't use. The fix reimplements the python function from the old prerm in shell. This avoids running python at all. [ Test Plan ] In a lxd container: 1. interfere with the python3-apt installation somehow (e.g. `rm -rf /usr/lib/python3/dist-packages/apt`) 2. execute the u-a-t.prerm script `apt remove ubuntu-advantage-tools` Without the fix,
[Group.of.nepali.translators] [Bug 2043836] Re: /usr/bin/ubuntu-advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_
This bug was fixed in the package ubuntu-advantage-tools - 31.2~23.10 --- ubuntu-advantage-tools (31.2~23.10) mantic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2043836 Title: /usr/bin/ubuntu- advantage:UnboundLocalError:wrapper:main:action_security_status:security_status_dict:get_installed_packages_by_origin:__enter__:get_apt_pkg_cache:get_last_known_candidate:get_pkg_candidate_version:__enter__:get_apt_pkg_cache:/usr/bin/ubuntu- advantage@33:wrapper:_warn_about_new_version:check_for_new_version:get_last_known_candidate Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Lunar: Won't Fix Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] When apt cannot be run as a normal user, and a pro command is run as a normal user, a bug occurs in the error handling. An UnboundLocalError occurs. The fix is to give that variable an initial value so that it is not unbound during the error handling. [ Test Plan ] lxc launch ubuntu-daily:jammy test lxc shell test #
[Group.of.nepali.translators] [Bug 2048921] Re: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic
This bug was fixed in the package ubuntu-advantage-tools - 31.2~23.10 --- ubuntu-advantage-tools (31.2~23.10) mantic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2048921 Title: [SRU] ubuntu-advantage-tools (30 -> 31) Xenial, Bionic, Focal, Jammy, Mantic Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] This release brings both bug-fixes and new features for the Pro Client, and we would like to make sure all of our supported customers have access to these improvements on all releases. The most important changes are: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach - introduce new ubuntu_pro_apt_news apparmor policy - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" - enable: + use deb822 apt source file format when on noble or later - landscape:
[Group.of.nepali.translators] [Bug 2050022] Re: Cannot run apt after installation if attached to Ubuntu Pro
This bug was fixed in the package ubuntu-advantage-tools - 31.2~23.10 --- ubuntu-advantage-tools (31.2~23.10) mantic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2050022 Title: Cannot run apt after installation if attached to Ubuntu Pro Status in subiquity: Invalid Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ ubuntu-advantage-tools SRU info ] [ Impact ] If ubuntu-advantage-tools (u-a-t) is not already installed, but cloud- init user-data includes "ubuntu_advantage" configuration data, then cloud-init will try to install u-a-t. On install, u-a-t needs to start ubuntu-advantage.service. ubuntu-advantage.service is ordered After=cloud-config.service. This results in deadlock, preventing apt from ever finishing. The apt lock is held forever and cloud-init never continues. The fix is to break the deadlock by removing the "After=cloud- config.service" ordering dependency from ubuntu-advantage.service. ubuntu-advantage.service should still wait until
[Group.of.nepali.translators] [Bug 2055046] Re: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage-license-check.log
This bug was fixed in the package ubuntu-advantage-tools - 31.2~23.10 --- ubuntu-advantage-tools (31.2~23.10) mantic; urgency=medium * Backport new upstream release (LP: #2048921) ubuntu-advantage-tools (31.2) noble; urgency=medium * properly rename logrotate conffile to avoid duplicate confiles, keep user changes and avoid unnecessary prompts (LP: #2055046) * use mv_conffile on all ubuntu-advantage-tools conffiles to avoid "obsolete" dpkg conffile statuses * fix regression in api u.pro.attach.auto.should_auto_attach.v1 so that it works with the new package names ubuntu-advantage-tools (31.1) noble; urgency=medium * fix unit test that failed on newer version of python ubuntu-advantage-tools (31) noble; urgency=medium * d/*: - rename ubuntu-advantage-tools to ubuntu-pro-client - rename ubuntu-advantage-pro to ubuntu-pro-image-auto-attach * d/apparmor: - introduce new ubuntu_pro_apt_news apparmor policy * d/control: - update descriptions and homepages - update ubuntu-pro-client-l10n to Depend on same binary version of ubuntu-pro-client * d/rules: - install ubuntu_pro_apt_news apparmor policy * d/ubuntu-pro-client.prerm: - removed dependency on python3 by reimplementing in sh (LP: #2021988) * apport: - collect logs related to ubuntu_pro_apt_news apparmor policy * release-upgrades.d/ubuntu-advantage-upgrades.cfg: - convert APT list files to deb822 files when upgrading to noble * systemd/apt-news.service: - add apparmor profile and capability restrictions * systemd/ubuntu-advantage.service: - avoid deadlock when started during cloud-config.service (LP: #2050022) * New upstream release 31 (LP: #2048921) - api: + u.pro.attach.auto.full_auto_attach.v1: new cloud_override param + u.pro.status.enabled_services.v1: * include services in "warning" state * include "usg" + u.pro.security.fix.*.plan.v1: export common objects from endpoint modules (GH: #2714) - cli: + add autocomplete for api subcommand + autocomplete multiple services for enable/disable subcommands + if lock is held, cli will retry over the course of a few seconds - collect-logs: + include logs related to ubuntu_pro_apt_news apparmor policy + include logs of apt-news.service + include logs of esm-cache.service - enable: + use deb822 apt source file format when on noble or later - fix: + avoid insinuating that CVEs were found on the machine (GH: #1522) + ignore LSNs when considering related USNs + pick CVE description based on what packages are installed - landscape: + don't disable landscape on ubuntu releases where it cannot be enabled (GH: #2743) + no longer assume landscape-client gets removed on disable (GH: #2840) + leave client.conf in place instead of renaming + require service to be running to consider "enabled" + new explanatory message when disabling - motd: properly pluralize messages about updates (GH: #1579) - status: show warning when canonical-livepatch command fails (LP: #2019997) - timer jobs: jobs-status.json is now world readable (GH: #2601) ubuntu-advantage-tools (30.1) noble; urgency=medium * fix UnboundLocalError in update-check error handling (LP: #2043836) -- Grant Orndorff Thu, 29 Feb 2024 09:03:11 -0500 ** Changed in: ubuntu-advantage-tools (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2055046 Title: ubuntu-pro-client:3 duplicate log entry for /var/log/ubuntu-advantage- license-check.log Status in ubuntu-advantage-tools package in Ubuntu: Confirmed Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] After an upgrade from ubuntu-advantage-tools 30.1 to ubuntu-pro-client 31.1, an old logrotate conffile named ubuntu-advantage-tools is left behind. The old file configures the same files as the new conffile: ubuntu-pro-client. The result is that when logrotate runs (on a daily timer) it has an error because two configurations for the same log files exist. This results in a "degraded" system status. The fix is to use the `mv_conffile` maintscript to remove the old ubuntu-advantage-tools logrotate conffile on upgrade. [ Test Plan ] We added a test to the ubuntu-pro-client integration test suite that covers this scenario. It upgrades to the new
[Group.of.nepali.translators] [Bug 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA
This bug was fixed in the package openssl - 1.1.1f-1ubuntu2.22 --- openssl (1.1.1f-1ubuntu2.22) focal-security; urgency=medium * SECURITY UPDATE: Implicit rejection for RSA PKCS#1 (LP: #2054090) - debian/patches/openssl-1.1.1-pkcs1-implicit-rejection.patch: Return deterministic random output instead of an error in case there is a padding error in crypto/cms/cms_env.c, crypto/pkcs7/pk7_doit.c, crypto/rsa/rsa_local.h, crypto/rsa/rsa_ossl.c, crypto/rsa/rsa_pk1.c, crypto/rsa/rsa_pmeth.c, doc/man1/pkeyutl.pod, doc/man1/rsautl.pod, doc/man3/EVP_PKEY_CTX_ctrl.pod, doc/man3/EVP_PKEY_decrypt.pod, doc/man3/RSA_padding_add_PKCS1_type_1.pod, doc/man3/RSA_public_encrypt.pod, include/openssl/rsa.h and test/recipes/30-test_evp_data/evppkey.txt. -- David Fernandez Gonzalez Fri, 16 Feb 2024 16:41:31 +0100 ** Changed in: openssl (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2054090 Title: Implicit rejection of PKCS#1 v1.5 RSA Status in openssl package in Ubuntu: New Status in openssl source package in Trusty: New Status in openssl source package in Xenial: New Status in openssl source package in Bionic: New Status in openssl source package in Focal: Fix Released Status in openssl source package in Jammy: Fix Released Status in openssl source package in Mantic: Fix Released Status in openssl source package in Noble: New Bug description: OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random output instead of an exception when detecting wrong padding (https://github.com/openssl/openssl/pull/13817). There are available backports already: * 3.0 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit- rejection.patch?ref_type=heads * 1.1.1 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit- rejection.patch?ref_type=heads This change is needed to fix CVE-2023-50782. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA
This bug was fixed in the package openssl - 3.0.10-1ubuntu2.3 --- openssl (3.0.10-1ubuntu2.3) mantic-security; urgency=medium * SECURITY UPDATE: Implicit rejection for RSA PKCS#1 (LP: #2054090) - debian/patches/openssl-pkcs1-implicit-rejection.patch: Return deterministic random output instead of an error in case there is a padding error in crypto/cms/cms_env.c, crypto/evp/ctrl_params_translate.c, crypto/pkcs7/pk7_doit.c, crypto/rsa/rsa_ossl.c, crypto/rsa/rsa_pk1.c, crypto/rsa/rsa_pmeth.c, doc/man1/openssl-pkeyutl.pod.in, doc/man1/openssl-rsautl.pod.in, doc/man3/EVP_PKEY_CTX_ctrl.pod, doc/man3/EVP_PKEY_decrypt.pod, doc/man3/RSA_padding_add_PKCS1_type_1.pod, doc/man3/RSA_public_encrypt.pod, doc/man7/provider-asym_cipher.pod, include/crypto/rsa.h, include/openssl/core_names.h, include/openssl/rsa.h, providers/implementations/asymciphers/rsa_enc.c and test/recipes/30-test_evp_data/evppkey_rsa_common.txt. -- David Fernandez Gonzalez Wed, 21 Feb 2024 11:45:39 +0100 ** Changed in: openssl (Ubuntu Mantic) Status: New => Fix Released ** Changed in: openssl (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2054090 Title: Implicit rejection of PKCS#1 v1.5 RSA Status in openssl package in Ubuntu: New Status in openssl source package in Trusty: New Status in openssl source package in Xenial: New Status in openssl source package in Bionic: New Status in openssl source package in Focal: Fix Released Status in openssl source package in Jammy: Fix Released Status in openssl source package in Mantic: Fix Released Status in openssl source package in Noble: New Bug description: OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random output instead of an exception when detecting wrong padding (https://github.com/openssl/openssl/pull/13817). There are available backports already: * 3.0 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit- rejection.patch?ref_type=heads * 1.1.1 https://gitlab.com/redhat/centos- stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit- rejection.patch?ref_type=heads This change is needed to fix CVE-2023-50782. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2015420] Re: motd: can't disable esm-related messages
This bug was fixed in the package update-notifier - 3.192.67 --- update-notifier (3.192.67) noble; urgency=medium * apt-check: add option to hide ESM messages from the human readable output. (LP: #2015420) -- Renan Rodrigo Barbosa Wed, 31 Jan 2024 11:40:02 -0300 ** Changed in: update-notifier (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2015420 Title: motd: can't disable esm-related messages Status in update-notifier package in Ubuntu: Fix Released Status in update-notifier source package in Xenial: In Progress Status in update-notifier source package in Bionic: In Progress Status in update-notifier source package in Focal: In Progress Status in update-notifier source package in Jammy: In Progress Bug description: [ Impact ] If ESM Infra/Apps is available for a system, users will always see messages related to those Ubuntu Pro services in their MOTDs. As stated in the original description, there have been complains on how hard it is to disable those messages - we have users who don't want Pro and don't want to be reminded of Pro all the time. The fix here is making it easier for people to disable the ESM related messages in the update-related MOTD, by giving them a way to opt-out. Users will have the option to add the --no-esm-messages flag to /etc/apt/apt.conf.d/99update-notifier, where the message generation script is executed as a hook. [ Test Plan ] Compare the messages before and after installing the new version of the package, and make sure they are exactly the same in different scenarios: - ESM status: unavailable, disabled, enabled - LTS system: yes or no - updates available: yes or no Thankfully, the unit test suite in tests/test_motd.py covers all of those scenarios functionality-wise. Manual checks on real systems may endorse the functionality. New tests were added to the suite making sure the flag hides the ESM related messages when it is present. On real systems, adding --no-esm-messages to the conf script and making sure it updates the MOTDs should remove ESM related messages for the same scenarios above. [ Where problems could occur ] - Other software may be relying on the apt-check script to generate human-readable messages. A mistake here could intefere with the message generated, changing expectation on stable releases, or causing errors. To mitigate that, the new flag is set to False as default, and all existing functionality is preserved. - Users may make mistakes when writing the new flag in the /etc/apt/apt.conf.d/99update-notifier configuration file. We will mitigate that by having comprehensible documentation with a clear explanation of what the flag does and where to put it. - If the user makes the mistake even following the documented steps, then it is out of our control. The impact of breaking the configuration file is that There will be no MOTD related to updates at all (as errors are redirected to /dev/null), or the errors themselves will appear in the apt update screen, or in the MOTD, if the user messes up the redirection. [ Other Info ] As opposed to what was in the original description, the proposed changeset does not separate esm messages from the regular updates messages - this ensures current users and potential callers get exactly the same result when checking their outputs after the change lands. As suggested in the original description, we understand that it is not easy and straightforward to add a flag to a script when compared to running a command or clicking a button. However, the messages are there for a product decision, and it is a product decision not to have a "too easy opt-out". On the other hand, users who want to disable this are capable of editing the file, and it will be way easier for them than making the changes in the python script itself - plus the configuration is kept between upgrades. If the default configuration file shipped by update-notifier changes in the future, the user may see a debconf prompt when upgrading the package - that is expected, as the user has made changes to a config file for a reason and needs to decide on keeping those or not. [ Original Description ] See https://github.com/canonical/ubuntu-pro-client/issues/2458 for the origin of the conversation. We don't think it needs to be _easy_, but it should probably be less burdensome to disable ESM update notifications in MOTD without disabling all update notifications in MOTD. One idea to accomplish this is to separate the /etc/update-motd.d/ files into two. One would print the normal update message, and the other would print the ESM message. Then, if an admin knows what they're
[Group.of.nepali.translators] [Bug 2036195] Re: Any packages installed in binary hooks are marked as manually installed - even dependencies
This bug was fixed in the package livecd-rootfs - 2.664.52 --- livecd-rootfs (2.664.52) focal; urgency=medium * fix: use correct sshd_config.d/ ordering. (LP: #2049860) livecd-rootfs (2.664.51) focal; urgency=medium [ Steve Langasek ] * The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; the latter breaks changes to /var/lib/apt/extended_states. (LP: #2036195). livecd-rootfs (2.664.50) focal; urgency=medium * Do not modify /etc/ssh/sshd_config for ubuntu-cpc project builds. (LP: #1968873) -- Thomas Bechtold Mon, 22 Jan 2024 17:08:05 +0530 ** Changed in: livecd-rootfs (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2036195 Title: Any packages installed in binary hooks are marked as manually installed - even dependencies Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: Fix Released Status in livecd-rootfs source package in Jammy: Fix Released Status in livecd-rootfs source package in Lunar: Fix Released Bug description: After much debugging trying to understand why `apt-get autoremove` was not working in a binary hook I realised that all packages installed in a binary hook are marked as manually installed - even the dependencies of packages. This is a bug. Another side affect of this is that any dependency of a package in the base chroot that is removed in a binary hook is not autoremovable in the binary hook. It is autoremovable once the image is created and launched though. This is due to how the `setup_mountpoint` function works (see https://git.launchpad.net/livecd-rootfs/tree/live- build/functions#n123) specifically ``` mount -t tmpfs none "$mountpoint/var/lib/apt" ``` Which means that inside the chroot that the binary hook works on, the `/var/lib/apt` directory is empty... including the `/var/lib/apt/extended_states` file which is used to store whether a package was auto installed or not. The same goes the other way - any changes to the `/var/lib/apt/extended_states` file inside chroot that the binary hook is changing are not reflected in the final image due to the `teardown_mountpoint` (see https://git.launchpad.net/livecd- rootfs/tree/live-build/functions#n152) not persisting any of those changes. The end result being. * If a package is removed in the binary hook then the resulting image will likely have autoremovable packages at first launch * Any package and their dependencies installed in a binary hook will all be marked as manually installed. SRU [ Impact ] * Packages installed in a binary hook are marked as manually installed - even the dependencies of packages [ Test Plan ] * Build test images and remove a package with dependencies. * Confirm that the dependencies are marked as autoremovable. * Confirm there are packages marked as auto installed [ Where problems could occur ] * Is any dependent packages are not marked as autremovable. * If no packages are marked as auto installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2036195/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2045297] Re: file root.hints needs update
This bug was fixed in the package dns-root-data - 2023112702~ubuntu0.20.04.1 --- dns-root-data (2023112702~ubuntu0.20.04.1) focal; urgency=medium [ Imre Jonk ] * update root hints to 2023112702 (LP: #2045297 Closes: #1054393) -- Christian Ehrhardt Mon, 29 Jan 2024 08:10:05 +0100 ** Changed in: dns-root-data (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2045297 Title: file root.hints needs update Status in Ubuntu Docker Images: New Status in dns-root-data package in Ubuntu: Fix Released Status in dns-root-data source package in Xenial: Triaged Status in dns-root-data source package in Bionic: Triaged Status in dns-root-data source package in Focal: Fix Released Status in dns-root-data source package in Jammy: Fix Released Status in dns-root-data source package in Mantic: Fix Released Status in dns-root-data source package in Noble: Fix Released Status in dns-root-data package in Debian: New Bug description: [ Impact ] * There was a renumbering of USC/ISI's DNS Root Servers, due to that Ubuntu users now are using servers that will go away. - https://b.root-servers.org/news/2023/05/16/new-addresses.html - https://www.lacnic.net/6868/1/lacnic/lacnic-asigna-recursos-de-numeracion-al-servidor-raiz-de-usc_isi * On one hand it is annoyance as e.g. named uses them as hints and will on start check those hints and spam you warnings to the logs. * On the other hand this will break. Mid term the old addresses will stop to work (by 2024-11-27) that is the strong deadline until this has to be updated everywhere. [ Test Plan ] * Gladly the self check on hints of named can be quite useful here $ apt install bind9 $ systemctl restart named $ systemctl status named Bad case (right now): Jan 25 09:45:16 j systemd[1]: Started BIND Domain Name Server. Jan 25 09:45:16 j named[4136]: running Jan 25 09:45:16 j named[4136]: resolver priming query complete: success Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/A (170.247.170.2) missing from hints Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/A (199.9.14.201) extra record in hints Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/ (2801:1b8:10::b) missing from hints Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/ (2001:500:200::b) extra record in hints Good case (once data files are fixed): ... Jan 25 09:47:50 n systemd[1]: Started named.service - BIND Domain Name Server. Jan 25 09:47:51 n named[1731]: managed-keys-zone: Key 20326 for zone . is now trusted (acceptance timer complete) Jan 25 09:47:51 n named[1731]: resolver priming query complete: success Warning, if your system can't connect to the root DNS info (e.g. firewall or weird things) then you will see the check fail to fetch the data for coparison and due to that the comparison can not warn you. That would look like this (or similar depending on the release): named[1659]: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out [ Where problems could occur ] * This isn't code, purely a data file for services that need to know about dns root servers. Thereby there is no code in the package itself that would fail, but potential regressions would be in the dependencies. Those are (and we can more consciously look out for those): Reverse-Recommends == * dnsmasq-base [amd64 arm64 armhf ppc64el s390x] * dnsmasq-base-lua [amd64 arm64 armhf ppc64el s390x] * ldnsutils [amd64 arm64 armhf ppc64el s390x] * libbellesip2 [amd64 arm64 armhf ppc64el s390x] * unbound * unbound-host Reverse-Depends === * bind9 * dnsviz * hash-slinger [amd64 arm64 armhf ppc64el s390x] * knot-resolver [amd64 arm64 armhf] * libgetdns10 [amd64 arm64 armhf ppc64el s390x] * libreswan [amd64 arm64 armhf ppc64el s390x] * opendkim [amd64 arm64 armhf ppc64el s390x] * pdns-recursor [amd64 arm64 ppc64el s390x] * At the same time I think we'd not need to do super advanced tests with custom setups of each of them. Those that are reverse dependencies and have tests (bind9, libreswan) will be ran by autopkgtest and given the change, that should IMHO be sufficient. [ Other Info ] * This is a native package and we are not doing anything special There also is a Debian PR [1] proposing the same just based on a different date. While we could pick the data of "today" it would not help more. By chosing the same data as proposed in Debian as well as going with backport-style versions even for the current release we - intentionally - allow this to be synced over once the Debian upload
[Group.of.nepali.translators] [Bug 2045297] Re: file root.hints needs update
This bug was fixed in the package dns-root-data - 2023112702~ubuntu0.22.04.1 --- dns-root-data (2023112702~ubuntu0.22.04.1) jammy; urgency=medium [ Imre Jonk ] * update root hints to 2023112702 (LP: #2045297 Closes: #1054393) -- Christian Ehrhardt Mon, 29 Jan 2024 08:10:05 +0100 ** Changed in: dns-root-data (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2045297 Title: file root.hints needs update Status in Ubuntu Docker Images: New Status in dns-root-data package in Ubuntu: Fix Released Status in dns-root-data source package in Xenial: Triaged Status in dns-root-data source package in Bionic: Triaged Status in dns-root-data source package in Focal: Fix Committed Status in dns-root-data source package in Jammy: Fix Released Status in dns-root-data source package in Mantic: Fix Released Status in dns-root-data source package in Noble: Fix Released Status in dns-root-data package in Debian: New Bug description: [ Impact ] * There was a renumbering of USC/ISI's DNS Root Servers, due to that Ubuntu users now are using servers that will go away. - https://b.root-servers.org/news/2023/05/16/new-addresses.html - https://www.lacnic.net/6868/1/lacnic/lacnic-asigna-recursos-de-numeracion-al-servidor-raiz-de-usc_isi * On one hand it is annoyance as e.g. named uses them as hints and will on start check those hints and spam you warnings to the logs. * On the other hand this will break. Mid term the old addresses will stop to work (by 2024-11-27) that is the strong deadline until this has to be updated everywhere. [ Test Plan ] * Gladly the self check on hints of named can be quite useful here $ apt install bind9 $ systemctl restart named $ systemctl status named Bad case (right now): Jan 25 09:45:16 j systemd[1]: Started BIND Domain Name Server. Jan 25 09:45:16 j named[4136]: running Jan 25 09:45:16 j named[4136]: resolver priming query complete: success Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/A (170.247.170.2) missing from hints Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/A (199.9.14.201) extra record in hints Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/ (2801:1b8:10::b) missing from hints Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/ (2001:500:200::b) extra record in hints Good case (once data files are fixed): ... Jan 25 09:47:50 n systemd[1]: Started named.service - BIND Domain Name Server. Jan 25 09:47:51 n named[1731]: managed-keys-zone: Key 20326 for zone . is now trusted (acceptance timer complete) Jan 25 09:47:51 n named[1731]: resolver priming query complete: success Warning, if your system can't connect to the root DNS info (e.g. firewall or weird things) then you will see the check fail to fetch the data for coparison and due to that the comparison can not warn you. That would look like this (or similar depending on the release): named[1659]: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out [ Where problems could occur ] * This isn't code, purely a data file for services that need to know about dns root servers. Thereby there is no code in the package itself that would fail, but potential regressions would be in the dependencies. Those are (and we can more consciously look out for those): Reverse-Recommends == * dnsmasq-base [amd64 arm64 armhf ppc64el s390x] * dnsmasq-base-lua [amd64 arm64 armhf ppc64el s390x] * ldnsutils [amd64 arm64 armhf ppc64el s390x] * libbellesip2 [amd64 arm64 armhf ppc64el s390x] * unbound * unbound-host Reverse-Depends === * bind9 * dnsviz * hash-slinger [amd64 arm64 armhf ppc64el s390x] * knot-resolver [amd64 arm64 armhf] * libgetdns10 [amd64 arm64 armhf ppc64el s390x] * libreswan [amd64 arm64 armhf ppc64el s390x] * opendkim [amd64 arm64 armhf ppc64el s390x] * pdns-recursor [amd64 arm64 ppc64el s390x] * At the same time I think we'd not need to do super advanced tests with custom setups of each of them. Those that are reverse dependencies and have tests (bind9, libreswan) will be ran by autopkgtest and given the change, that should IMHO be sufficient. [ Other Info ] * This is a native package and we are not doing anything special There also is a Debian PR [1] proposing the same just based on a different date. While we could pick the data of "today" it would not help more. By chosing the same data as proposed in Debian as well as going with backport-style versions even for the current release we - intentionally - allow this to be synced over once the Debian upload
[Group.of.nepali.translators] [Bug 2045297] Re: file root.hints needs update
This bug was fixed in the package dns-root-data - 2023112702~ubuntu0.23.10.1 --- dns-root-data (2023112702~ubuntu0.23.10.1) mantic; urgency=medium [ Imre Jonk ] * update root hints to 2023112702 (LP: #2045297 Closes: #1054393) -- Christian Ehrhardt Mon, 29 Jan 2024 08:10:05 +0100 ** Changed in: dns-root-data (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2045297 Title: file root.hints needs update Status in Ubuntu Docker Images: New Status in dns-root-data package in Ubuntu: Fix Released Status in dns-root-data source package in Xenial: Triaged Status in dns-root-data source package in Bionic: Triaged Status in dns-root-data source package in Focal: Fix Committed Status in dns-root-data source package in Jammy: Fix Committed Status in dns-root-data source package in Mantic: Fix Released Status in dns-root-data source package in Noble: Fix Released Status in dns-root-data package in Debian: New Bug description: [ Impact ] * There was a renumbering of USC/ISI's DNS Root Servers, due to that Ubuntu users now are using servers that will go away. - https://b.root-servers.org/news/2023/05/16/new-addresses.html - https://www.lacnic.net/6868/1/lacnic/lacnic-asigna-recursos-de-numeracion-al-servidor-raiz-de-usc_isi * On one hand it is annoyance as e.g. named uses them as hints and will on start check those hints and spam you warnings to the logs. * On the other hand this will break. Mid term the old addresses will stop to work (by 2024-11-27) that is the strong deadline until this has to be updated everywhere. [ Test Plan ] * Gladly the self check on hints of named can be quite useful here $ apt install bind9 $ systemctl restart named $ systemctl status named Bad case (right now): Jan 25 09:45:16 j systemd[1]: Started BIND Domain Name Server. Jan 25 09:45:16 j named[4136]: running Jan 25 09:45:16 j named[4136]: resolver priming query complete: success Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/A (170.247.170.2) missing from hints Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/A (199.9.14.201) extra record in hints Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/ (2801:1b8:10::b) missing from hints Jan 25 09:45:16 j named[4136]: checkhints: b.root-servers.net/ (2001:500:200::b) extra record in hints Good case (once data files are fixed): ... Jan 25 09:47:50 n systemd[1]: Started named.service - BIND Domain Name Server. Jan 25 09:47:51 n named[1731]: managed-keys-zone: Key 20326 for zone . is now trusted (acceptance timer complete) Jan 25 09:47:51 n named[1731]: resolver priming query complete: success Warning, if your system can't connect to the root DNS info (e.g. firewall or weird things) then you will see the check fail to fetch the data for coparison and due to that the comparison can not warn you. That would look like this (or similar depending on the release): named[1659]: managed-keys-zone: Unable to fetch DNSKEY set '.': timed out [ Where problems could occur ] * This isn't code, purely a data file for services that need to know about dns root servers. Thereby there is no code in the package itself that would fail, but potential regressions would be in the dependencies. Those are (and we can more consciously look out for those): Reverse-Recommends == * dnsmasq-base [amd64 arm64 armhf ppc64el s390x] * dnsmasq-base-lua [amd64 arm64 armhf ppc64el s390x] * ldnsutils [amd64 arm64 armhf ppc64el s390x] * libbellesip2 [amd64 arm64 armhf ppc64el s390x] * unbound * unbound-host Reverse-Depends === * bind9 * dnsviz * hash-slinger [amd64 arm64 armhf ppc64el s390x] * knot-resolver [amd64 arm64 armhf] * libgetdns10 [amd64 arm64 armhf ppc64el s390x] * libreswan [amd64 arm64 armhf ppc64el s390x] * opendkim [amd64 arm64 armhf ppc64el s390x] * pdns-recursor [amd64 arm64 ppc64el s390x] * At the same time I think we'd not need to do super advanced tests with custom setups of each of them. Those that are reverse dependencies and have tests (bind9, libreswan) will be ran by autopkgtest and given the change, that should IMHO be sufficient. [ Other Info ] * This is a native package and we are not doing anything special There also is a Debian PR [1] proposing the same just based on a different date. While we could pick the data of "today" it would not help more. By chosing the same data as proposed in Debian as well as going with backport-style versions even for the current release we - intentionally - allow this to be synced over once the Debian upload
[Group.of.nepali.translators] [Bug 2044657] Re: Multiple data corruption issues in zfs
This bug was fixed in the package zfs-linux - 2.2.0-0ubuntu1~23.10.2
---
zfs-linux (2.2.0-0ubuntu1~23.10.2) mantic; urgency=medium
* d/p/9b9b09f452a469458451c221debfbab944e7f081.patch Cherry-pick
"dnode_is_dirty: check dnode and its data for dirtiness" fix from
zfs-2.2.2. LP: #2044657
-- Dimitri John Ledkov Tue, 30 Jan 2024
15:54:02 +
** Changed in: zfs-linux (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2050956] Re: [SRU] Update d/control file with dependencies
This bug was fixed in the package google-guest-agent - 20231004.02-0ubuntu1~23.10.2 --- google-guest-agent (20231004.02-0ubuntu1~23.10.2) mantic-security; urgency=medium * d/control: Add a dependency on `google-compute-engine-oslogin` (LP: #2050956) -- Chloé 'kajiya' Smith Fri, 26 Jan 2024 23:49:12 + ** Changed in: google-guest-agent (Ubuntu Jammy) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2050956 Title: [SRU] Update d/control file with dependencies Status in google-guest-agent package in Ubuntu: Fix Released Status in google-guest-agent source package in Xenial: New Status in google-guest-agent source package in Bionic: New Status in google-guest-agent source package in Focal: Fix Released Status in google-guest-agent source package in Jammy: Fix Released Status in google-guest-agent source package in Mantic: Fix Released Status in google-guest-agent source package in Noble: Fix Released Bug description: [SRU] === [Impact] `google-guest-agent` is a package provided by Google for installation within guests that run on Google Compute Engine (GCE). It is part of a collection of tools and daemons that ensure that Ubuntu images published to GCE run properly on the platform. There is a diff between Google's packaged debian distro [0] `debian/control` file and what's currently in the ubuntu archive. This was originally harmless but now has caused a customer issue. Unattended upgrades caused a `google-guest-agent` update (the last release was a no-change-rebuild against `-security`) but as there was _no_ dependency on `google-compute-engine-oslogin` in the d/control file, users became locked out of their instances. This is because the creation of the `sudoers` file has moved from the PAM module to `authorized keys` (example diffs in jammy here [1][2]). It was previously in the PAM account manager stack, but since the latest update this `google-guest-agent` version doesn't try to setup an account manager stack anymore. In other words the responsibility of creating these files has changed, but without the dependency in d/control on `google-compute-engine-oslogin` the `sudoers` file is not created when a user tries OSlogin. [Test Case] When the new version of this package is uploaded to -proposed, the following will happen: * an image based on -proposed will be built for GCE and published * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. * Each test image will be launched, and we will validate: ** the package version(s) ** that the correct ssh keys have been imported ** that the google specific services are running successfully If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Additional Information] This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [3]. [0]: https://github.com/GoogleCloudPlatform/guest-agent/tree/main/packaging/debian [1]: https://launchpadlibrarian.net/709883238/google-guest-agent_20220622.00-0ubuntu2~22.04.1_20231004.02-0ubuntu1~22.04.2.diff.gz [2]: https://launchpadlibrarian.net/696732553/google-compute-engine-oslogin_20220714.00-0ubuntu1~22.04.1_20231004.00-0ubuntu1~22.04.1.diff.gz [3]: https://wiki.ubuntu.com/google-guest-agent-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2050956/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2050956] Re: [SRU] Update d/control file with dependencies
This bug was fixed in the package google-guest-agent - 20231004.02-0ubuntu1~20.04.3 --- google-guest-agent (20231004.02-0ubuntu1~20.04.3) focal-security; urgency=medium * d/control: Add a dependency on `google-compute-engine-oslogin` (LP: #2050956) -- Chloé 'kajiya' Smith Sat, 27 Jan 2024 01:44:03 + ** Changed in: google-guest-agent (Ubuntu Focal) Status: New => Fix Released ** Changed in: google-guest-agent (Ubuntu Mantic) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2050956 Title: [SRU] Update d/control file with dependencies Status in google-guest-agent package in Ubuntu: Fix Released Status in google-guest-agent source package in Xenial: New Status in google-guest-agent source package in Bionic: New Status in google-guest-agent source package in Focal: Fix Released Status in google-guest-agent source package in Jammy: Fix Released Status in google-guest-agent source package in Mantic: Fix Released Status in google-guest-agent source package in Noble: Fix Released Bug description: [SRU] === [Impact] `google-guest-agent` is a package provided by Google for installation within guests that run on Google Compute Engine (GCE). It is part of a collection of tools and daemons that ensure that Ubuntu images published to GCE run properly on the platform. There is a diff between Google's packaged debian distro [0] `debian/control` file and what's currently in the ubuntu archive. This was originally harmless but now has caused a customer issue. Unattended upgrades caused a `google-guest-agent` update (the last release was a no-change-rebuild against `-security`) but as there was _no_ dependency on `google-compute-engine-oslogin` in the d/control file, users became locked out of their instances. This is because the creation of the `sudoers` file has moved from the PAM module to `authorized keys` (example diffs in jammy here [1][2]). It was previously in the PAM account manager stack, but since the latest update this `google-guest-agent` version doesn't try to setup an account manager stack anymore. In other words the responsibility of creating these files has changed, but without the dependency in d/control on `google-compute-engine-oslogin` the `sudoers` file is not created when a user tries OSlogin. [Test Case] When the new version of this package is uploaded to -proposed, the following will happen: * an image based on -proposed will be built for GCE and published * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. * Each test image will be launched, and we will validate: ** the package version(s) ** that the correct ssh keys have been imported ** that the google specific services are running successfully If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Additional Information] This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [3]. [0]: https://github.com/GoogleCloudPlatform/guest-agent/tree/main/packaging/debian [1]: https://launchpadlibrarian.net/709883238/google-guest-agent_20220622.00-0ubuntu2~22.04.1_20231004.02-0ubuntu1~22.04.2.diff.gz [2]: https://launchpadlibrarian.net/696732553/google-compute-engine-oslogin_20220714.00-0ubuntu1~22.04.1_20231004.00-0ubuntu1~22.04.1.diff.gz [3]: https://wiki.ubuntu.com/google-guest-agent-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2050956/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2050956] Re: Update d/control file with dependencies
This bug was fixed in the package google-guest-agent - 20231004.02-0ubuntu3 --- google-guest-agent (20231004.02-0ubuntu3) noble; urgency=medium * d/control: Fix dependency version of `google-compute-engine-oslogin` to match archive (LP: #2050956) google-guest-agent (20231004.02-0ubuntu2) noble; urgency=medium * d/control: There should b a dependency on `google-compute-engine-oslogin` to match the Google managed control file (LP: #2050956) * Also updated the `Vcs-` fields and removed the `Uploaders` field. -- Chloé 'kajiya' Smith Fri, 26 Jan 2024 15:12:02 + ** Changed in: google-guest-agent (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2050956 Title: Update d/control file with dependencies Status in google-guest-agent package in Ubuntu: Fix Released Status in google-guest-agent source package in Xenial: New Status in google-guest-agent source package in Bionic: New Status in google-guest-agent source package in Focal: New Status in google-guest-agent source package in Jammy: New Status in google-guest-agent source package in Mantic: New Status in google-guest-agent source package in Noble: Fix Released Bug description: [Impact] `google-guest-agent` is a package provided by Google for installation within guests that run on Google Compute Engine (GCE). It is part of a collection of tools and daemons that ensure that Ubuntu images published to GCE run properly on the platform. There is a diff between Google's packaged debian distro [0] `debian/control` file and what's currently in the archive [1]. This was originally harmless but now has caused a customer issue where they were unable to login as they'd upgraded the `google-guest-agent` package but _not_ the `google-compute-engine-oslogin` package. The `google-guest-agent` should have a dependency on `google-compute- engine-oslogin` the same as it does in the Google managed control file. Also the `Uploaders` and `Vcs-*` fields are out of date. [Test Case] When the new version of this package is uploaded to -proposed, the following will happen: * an image based on -proposed will be built for GCE and published * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. * Each test image will be launched, and we will validate: ** the package version(s) ** that the correct ssh keys have been imported ** that the google specific services are running successfully If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Additional Information] This bug is used to track the release of this new version for all the supported suites, as per the policy mentioned here [2]. [0]: https://github.com/GoogleCloudPlatform/guest-agent/tree/main/packaging/debian [1]: https://git.launchpad.net/~cloud-images/cloud-images/+git/google-guest-agent/tree/debian/control?h=ubuntu/master [2]: https://wiki.ubuntu.com/google-guest-agent-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2050956/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2051115] Re: ubuntu pro integration interferes with dist-upgrade prompting
This bug was fixed in the package update-manager - 1:24.04.4 --- update-manager (1:24.04.4) noble; urgency=low * d/control: Depend on ubuntu-advantage-tools >= 30~. Fixes edge case whereby the program crashes upon an incomplete response from ua security-status (LP: #2049785). * The New Release dialog should take precedence over a list of updates dialog if the latter would only show Ubuntu Pro updates in an unattached system. (LP: #2051115). -- Nathan Pratta Teodosio Mon, 22 Jan 2024 08:17:25 +0100 ** Changed in: update-manager (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2051115 Title: ubuntu pro integration interferes with dist-upgrade prompting Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: New Status in update-manager source package in Bionic: New Status in update-manager source package in Focal: New Status in update-manager source package in Jammy: New Status in update-manager source package in Noble: Fix Released Bug description: The listing of Ubuntu Pro packages has been introduced in recent versions of update-manager, but as an undesired consequence, in up to date machines unattached to Ubuntu Pro, update-manager stopped prompting to upgrade to a next supported release. Ubuntu Pro packages should be merely an addition to this program and not alter its main behavior. [Test plan] ---> ua detach --assume-yes apt update apt upgrade apt install hello update-manager <--- Instead of listing Ubuntu Pro packages (the hello one, for example, always has a ESM update) that would be installable if the user attached to Ubuntu Pro, the update-manager window should simply do as it did in older versions, namely, state that software is up to date, and, if a newer LTS is available, suggest to the user to update to it. [Where problems could occur] The Pro packages should still be listed as such (i.e. under their own section, "Ubuntu Pro security updates", in the package listing) in case there is at least one upgradable package (as of 'apt list --upgradable'), whether the machine is attached, in which case the Ubuntu Pro section is sensitive, or unattached to Ubuntu Pro, in which case it is insensitive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2051115/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2046356] Re: Update URL for Support information in MOTD message
This bug was fixed in the package base-files - 10.1ubuntu2.12 --- base-files (10.1ubuntu2.12) bionic; urgency=medium * update-motd.d/10-help-text: Update support url for new Ubuntu Pro webpage (LP: #2046356) -- Lucas Moura Tue, 02 Jan 2024 14:19:18 -0300 ** Changed in: base-files (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in base-files source package in Bionic: Fix Released Status in base-files source package in Focal: Fix Released Status in base-files source package in Jammy: Fix Released Status in base-files source package in Lunar: Fix Released Status in base-files source package in Mantic: Fix Released Status in base-files source package in Noble: Fix Released Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2046356] Re: Update URL for Support information in MOTD message
This bug was fixed in the package base-files - 11ubuntu5.8 --- base-files (11ubuntu5.8) focal; urgency=medium * motd/10-help-text: Update support url for new Ubuntu Pro webpage (LP: #2046356) -- Lucas Moura Tue, 02 Jan 2024 14:12:43 -0300 ** Changed in: base-files (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in base-files source package in Bionic: Fix Released Status in base-files source package in Focal: Fix Released Status in base-files source package in Jammy: Fix Released Status in base-files source package in Lunar: Fix Released Status in base-files source package in Mantic: Fix Released Status in base-files source package in Noble: Fix Released Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2046356] Re: Update URL for Support information in MOTD message
This bug was fixed in the package base-files - 12ubuntu4.5 --- base-files (12ubuntu4.5) jammy; urgency=medium * motd/10-help-text: Update support url for new Ubuntu Pro webpage (LP: #2046356) -- Lucas Moura Tue, 02 Jan 2024 14:09:35 -0300 ** Changed in: base-files (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: base-files (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in base-files source package in Bionic: Fix Released Status in base-files source package in Focal: Fix Released Status in base-files source package in Jammy: Fix Released Status in base-files source package in Lunar: Fix Released Status in base-files source package in Mantic: Fix Released Status in base-files source package in Noble: Fix Released Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2036195] Re: Any packages installed in binary hooks are marked as manually installed - even dependencies
This bug was fixed in the package livecd-rootfs - 2.765.34 --- livecd-rootfs (2.765.34) jammy; urgency=medium * Remove comments in the debian/control dependencies as it was causing the package build to fail. livecd-rootfs (2.765.33) jammy; urgency=medium [ Steve Langasek ] * Use losetup instead of kpartx to resolve race conditions in riscv64 image builds. LP: #2045797. [ Utkarsh Gupta ] * unminimize: Use lxd-installer to install LXD itself (LP: #2036725) livecd-rootfs (2.765.32) jammy; urgency=medium [ Heinrich Schuchardt ] * arm: fix console parameter for ARM cloud-images (LP: #2036730) livecd-rootfs (2.765.31) jammy; urgency=medium [ John Chittum ] * fix: add 6.5 kernel apparmor features to livecd-rootfs based on features of 6.5 in ubuntu/mantic. This will roll as HWE. (LP: #2037567) livecd-rootfs (2.765.30) jammy; urgency=medium * Enable snap preseeding with ppc64el images where /boot/vmlinux is used instead of /boot/vmlinuz. (LP: #2038957) livecd-rootfs (2.765.29) jammy; urgency=medium [ Steve Langasek ] * The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; the latter breaks changes to /var/lib/apt/extended_states. (LP: #2036195). livecd-rootfs (2.765.28) jammy; urgency=medium * Fix unminimize to correctly list packages. (LP: #1996489) * Install LXD snap from stable/ubuntu- channel. (LP: #2036725) livecd-rootfs (2.765.27) jammy; urgency=medium [ Thomas Bechtold ] * Do not modify /etc/ssh/sshd_config for ubuntu-cpc project builds (LP: #1968873) -- Łukasz 'sil2100' Zemczak Mon, 15 Jan 2024 16:41:18 +0100 ** Changed in: livecd-rootfs (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2036195 Title: Any packages installed in binary hooks are marked as manually installed - even dependencies Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: Fix Committed Status in livecd-rootfs source package in Jammy: Fix Released Status in livecd-rootfs source package in Lunar: Fix Released Bug description: After much debugging trying to understand why `apt-get autoremove` was not working in a binary hook I realised that all packages installed in a binary hook are marked as manually installed - even the dependencies of packages. This is a bug. Another side affect of this is that any dependency of a package in the base chroot that is removed in a binary hook is not autoremovable in the binary hook. It is autoremovable once the image is created and launched though. This is due to how the `setup_mountpoint` function works (see https://git.launchpad.net/livecd-rootfs/tree/live- build/functions#n123) specifically ``` mount -t tmpfs none "$mountpoint/var/lib/apt" ``` Which means that inside the chroot that the binary hook works on, the `/var/lib/apt` directory is empty... including the `/var/lib/apt/extended_states` file which is used to store whether a package was auto installed or not. The same goes the other way - any changes to the `/var/lib/apt/extended_states` file inside chroot that the binary hook is changing are not reflected in the final image due to the `teardown_mountpoint` (see https://git.launchpad.net/livecd- rootfs/tree/live-build/functions#n152) not persisting any of those changes. The end result being. * If a package is removed in the binary hook then the resulting image will likely have autoremovable packages at first launch * Any package and their dependencies installed in a binary hook will all be marked as manually installed. SRU [ Impact ] * Packages installed in a binary hook are marked as manually installed - even the dependencies of packages [ Test Plan ] * Build test images and remove a package with dependencies. * Confirm that the dependencies are marked as autoremovable. * Confirm there are packages marked as auto installed [ Where problems could occur ] * Is any dependent packages are not marked as autremovable. * If no packages are marked as auto installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2036195/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2038957] Re: ppcel64 images unpack to /boot/vmlinux not /boot/vmlinuz leading to kernel feature mismatch
This bug was fixed in the package livecd-rootfs - 2.765.34
---
livecd-rootfs (2.765.34) jammy; urgency=medium
* Remove comments in the debian/control dependencies as it was causing the
package build to fail.
livecd-rootfs (2.765.33) jammy; urgency=medium
[ Steve Langasek ]
* Use losetup instead of kpartx to resolve race conditions in riscv64
image builds. LP: #2045797.
[ Utkarsh Gupta ]
* unminimize: Use lxd-installer to install LXD itself (LP: #2036725)
livecd-rootfs (2.765.32) jammy; urgency=medium
[ Heinrich Schuchardt ]
* arm: fix console parameter for ARM cloud-images (LP: #2036730)
livecd-rootfs (2.765.31) jammy; urgency=medium
[ John Chittum ]
* fix: add 6.5 kernel apparmor features to livecd-rootfs based on
features of 6.5 in ubuntu/mantic. This will roll as HWE. (LP: #2037567)
livecd-rootfs (2.765.30) jammy; urgency=medium
* Enable snap preseeding with ppc64el images where /boot/vmlinux is used
instead of /boot/vmlinuz. (LP: #2038957)
livecd-rootfs (2.765.29) jammy; urgency=medium
[ Steve Langasek ]
* The chroot tmpfs mount should only be /var/lib/apt/lists, not
/var/lib/apt; the latter breaks changes to /var/lib/apt/extended_states.
(LP: #2036195).
livecd-rootfs (2.765.28) jammy; urgency=medium
* Fix unminimize to correctly list packages. (LP: #1996489)
* Install LXD snap from stable/ubuntu- channel. (LP: #2036725)
livecd-rootfs (2.765.27) jammy; urgency=medium
[ Thomas Bechtold ]
* Do not modify /etc/ssh/sshd_config for ubuntu-cpc
project builds (LP: #1968873)
-- Łukasz 'sil2100' Zemczak Mon, 15 Jan
2024 16:41:18 +0100
** Changed in: livecd-rootfs (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2038957
Title:
ppcel64 images unpack to /boot/vmlinux not /boot/vmlinuz leading to
kernel feature mismatch
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Xenial:
Won't Fix
Status in livecd-rootfs source package in Bionic:
Won't Fix
Status in livecd-rootfs source package in Focal:
Won't Fix
Status in livecd-rootfs source package in Jammy:
Fix Released
Status in livecd-rootfs source package in Lunar:
Won't Fix
Status in livecd-rootfs source package in Mantic:
Fix Released
Status in livecd-rootfs source package in Noble:
Fix Released
Bug description:
In a build of a ppcel64 image, snap_validate_seed fails to find the
installed kernel to pick a matching apparmor feature set to mount.
from the log
```
+ [ -e chroot/boot/vmlinuz ]
+ [ -e chroot/var/lib/snapd/seed/seed.yaml ]
+ snap debug validate-seed chroot/var/lib/snapd/seed/seed.yaml
+ realpath chroot
+ /usr/lib/snapd/snap-preseed --reset /build/chroot
ubuntu classic preseeding
unmounting: /build/chroot/tmp/snapd-preseed
ubuntu classic preseeding
unmounting: /tmp/snapd-preseed
+ realpath chroot
+ /usr/lib/snapd/snap-preseed /build/chroot
ubuntu classic preseeding
```
This corresponds to line 772 in livecd-rootfs/live-build/functions
snap_validate_seed() {
local CHROOT_ROOT=$1
local kern_major_min=undefined
if [ -e ${CHROOT_ROOT}/boot/vmlinuz ]; then
ppcel64 however unpacks to /boot/vmlinux. For history:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358920
for ppcel64 images, this function needs to be updated to check for
`/boot/vmlinux`.
This will require an SRU 23.10 (post-release) and 22.04
SRU
[ Impact ]
* ppc64el Users of the 6.5 kernel will have un-optimized first boot
experiences due to snaps not preseeding with the correct apparmor
setup. This directly affects clouds, leading to boot speed degradation
of anywhere from 10-30s (depending on snaps installed)
[ Test Plan ]
* Build test ppc64el images and test that preseeding was correctly
applied for the 6.5 kernel
[ Where problems could occur ]
* If the optimized preseeding of the snaps for ppc64el continues to
fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2038957/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2046356] Re: Update URL for Support information in MOTD message
This bug was fixed in the package base-files - 12.3ubuntu2.1 --- base-files (12.3ubuntu2.1) lunar; urgency=medium * motd/10-help-text: Update support url for new Ubuntu Pro webpage (LP: #2046356) -- Lucas Moura Tue, 02 Jan 2024 14:37:38 -0300 ** Changed in: base-files (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Committed Status in base-files source package in Focal: Fix Committed Status in base-files source package in Jammy: Fix Committed Status in base-files source package in Lunar: Fix Released Status in base-files source package in Mantic: Fix Released Status in base-files source package in Noble: Fix Released Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2046356] Re: Update URL for Support information in MOTD message
This bug was fixed in the package base-files - 13ubuntu2.1 --- base-files (13ubuntu2.1) mantic; urgency=medium * motd/10-help-text: Update support url for new Ubuntu Pro webpage (LP: #2046356) -- Lucas Moura Tue, 02 Jan 2024 10:25:08 -0300 ** Changed in: base-files (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Committed Status in base-files source package in Focal: Fix Committed Status in base-files source package in Jammy: Fix Committed Status in base-files source package in Lunar: Fix Released Status in base-files source package in Mantic: Fix Released Status in base-files source package in Noble: Fix Released Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2045918] Re: [SRU] Fix crash caused by updating update-manager from inside itself
This bug was fixed in the package update-manager - 1:22.04.18 --- update-manager (1:22.04.18) jammy; urgency=medium * Add back removed widgets to UI file to fix crash when updating Upgrade Manager from inside itself (LP: #2045918). -- Nathan Pratta Teodosio Fri, 08 Dec 2023 11:23:26 +0100 ** Changed in: update-manager (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2045918 Title: [SRU] Fix crash caused by updating update-manager from inside itself Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: New Status in update-manager source package in Bionic: New Status in update-manager source package in Focal: New Status in update-manager source package in Jammy: Fix Released Status in update-manager source package in Mantic: Won't Fix Bug description: Impact -- LP:1990450 introduced Ubuntu Pro updates and news to update-manager, but also a bug whereby updating update-manager itself while update- manager is running replaces its UI files with a version incompatible with the already running handle of update-manager, subsequently causing a crash when the latter references an widget existing only in the old UI file. In other words, update-manager crashes if the user tries installing the new update-manager release from inside itself. Even though updates would have been installed successfully at that point and subsequent runs of update-manager would not crash, the user is none the wiser and is most likely left worried about his resulting system state. Test case - 1. Have the old version of Update Manager installed and the proposed version available in the Apt database, such that, in Jammy for example, 'apt install --dry-run --verbose-versions' would report update-manager (1:22.04.9 => 1:22.04.18) 2. Start update-manager from a terminal. 3. Make sure 'Software Updater' is selected in the list. We don't care about any other package for this test. 4. Click 'Install now'. The installation must complete successfully and the view must be automatically recalculated. Verify that the application didn't crash (no tracebacks in the terminal window) and confirm with 'apt policy update-manager' that the new version was indeed installed. To note --- The recalculated view will not include references to Ubuntu Pro (neither news pane nor Ubuntu Pro updates section), as it is still the old version of the program that is running. Regression potential GTK is very finicky about its *.ui files; We must look out for other widgets failing to map or being relocated. Original report --- The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:22.04.17, the problem page at https://errors.ubuntu.com/problem/7b4facc926a743e632733dcc290e7cd5623b6eb0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2045918/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2043001] Re: Please update the package to 20231004.00
This bug was fixed in the package google-compute-engine-oslogin - 20231004.00-0ubuntu1~22.04.1 --- google-compute-engine-oslogin (20231004.00-0ubuntu1~22.04.1) jammy; urgency=medium * No-change rebuild for Jammy. google-compute-engine-oslogin (20231004.00-0ubuntu1) noble; urgency=medium * New upstream version 20231004.00. (LP: #2043001) * d/links: Update links w/ respective .so shipped -- Utkarsh Gupta Wed, 08 Nov 2023 11:33:39 +0200 ** Changed in: google-compute-engine-oslogin (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2043001 Title: Please update the package to 20231004.00 Status in google-compute-engine-oslogin package in Ubuntu: Fix Released Status in google-compute-engine-oslogin source package in Xenial: New Status in google-compute-engine-oslogin source package in Bionic: New Status in google-compute-engine-oslogin source package in Focal: Fix Released Status in google-compute-engine-oslogin source package in Jammy: Fix Released Status in google-compute-engine-oslogin source package in Lunar: Fix Released Status in google-compute-engine-oslogin source package in Mantic: Fix Released Bug description: [Impact] Google-compute-engine-oslogin is provided by Google for installation within guests that run on Google Compute Engine. It part of the collection of tools and daemons originally packaged as gce-compute- image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating google-compute-engine-oslogin to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of google-compute-engine-oslogin is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. * Each test image will be launched, and we will validate: * the package version(s) * that the correct ssh keys have been imported * that the google specific services are running successfully If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2043001/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2043001] Re: Please update the package to 20231004.00
This bug was fixed in the package google-compute-engine-oslogin - 20231004.00-0ubuntu1~23.04.1 --- google-compute-engine-oslogin (20231004.00-0ubuntu1~23.04.1) lunar; urgency=medium * No-change rebuild for Lunar. google-compute-engine-oslogin (20231004.00-0ubuntu1) noble; urgency=medium * New upstream version 20231004.00. (LP: #2043001) * d/links: Update links w/ respective .so shipped -- Utkarsh Gupta Wed, 08 Nov 2023 11:31:07 +0200 ** Changed in: google-compute-engine-oslogin (Ubuntu Lunar) Status: Fix Committed => Fix Released ** Changed in: google-compute-engine-oslogin (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2043001 Title: Please update the package to 20231004.00 Status in google-compute-engine-oslogin package in Ubuntu: Fix Released Status in google-compute-engine-oslogin source package in Xenial: New Status in google-compute-engine-oslogin source package in Bionic: New Status in google-compute-engine-oslogin source package in Focal: Fix Released Status in google-compute-engine-oslogin source package in Jammy: Fix Released Status in google-compute-engine-oslogin source package in Lunar: Fix Released Status in google-compute-engine-oslogin source package in Mantic: Fix Released Bug description: [Impact] Google-compute-engine-oslogin is provided by Google for installation within guests that run on Google Compute Engine. It part of the collection of tools and daemons originally packaged as gce-compute- image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating google-compute-engine-oslogin to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of google-compute-engine-oslogin is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. * Each test image will be launched, and we will validate: * the package version(s) * that the correct ssh keys have been imported * that the google specific services are running successfully If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2043001/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2043001] Re: Please update the package to 20231004.00
This bug was fixed in the package google-compute-engine-oslogin - 20231004.00-0ubuntu1~23.10.1 --- google-compute-engine-oslogin (20231004.00-0ubuntu1~23.10.1) mantic; urgency=medium * No-change rebuild for Mantic. google-compute-engine-oslogin (20231004.00-0ubuntu1) noble; urgency=medium * New upstream version 20231004.00. (LP: #2043001) * d/links: Update links w/ respective .so shipped -- Utkarsh Gupta Wed, 08 Nov 2023 11:29:09 +0200 ** Changed in: google-compute-engine-oslogin (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2043001 Title: Please update the package to 20231004.00 Status in google-compute-engine-oslogin package in Ubuntu: Fix Released Status in google-compute-engine-oslogin source package in Xenial: New Status in google-compute-engine-oslogin source package in Bionic: New Status in google-compute-engine-oslogin source package in Focal: Fix Released Status in google-compute-engine-oslogin source package in Jammy: Fix Released Status in google-compute-engine-oslogin source package in Lunar: Fix Released Status in google-compute-engine-oslogin source package in Mantic: Fix Released Bug description: [Impact] Google-compute-engine-oslogin is provided by Google for installation within guests that run on Google Compute Engine. It part of the collection of tools and daemons originally packaged as gce-compute- image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating google-compute-engine-oslogin to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. [Test Case] When a new version of google-compute-engine-oslogin is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. * Each test image will be launched, and we will validate: * the package version(s) * that the correct ssh keys have been imported * that the google specific services are running successfully If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-compute-engine-oslogin/+bug/2043001/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1938208] Re: No CI testing for the case that cloud-init is installed but not in use
This bug was fixed in the package ubuntu-advantage-tools - 30~16.04 --- ubuntu-advantage-tools (30~16.04) xenial; urgency=medium * Backport new upstream release to xenial (LP: #2038461) ubuntu-advantage-tools (30) noble; urgency=medium * d/control: - add python3-apt as a build dependency - add the new ubuntu-pro-client-l10n binary package - recommend installing ubuntu-pro-client-l10n * d/po/*: - Makefile to build localization files to debian/po/usr/share/locale/ - update POTFILES.in to cover all translatable messages - remove old unused pot file - add new complete pot file for "ubuntu-pro" domain - add first Brazilian Portuguese translations * d/rules: - add step to build the translations * d/tests/control: - mark autopkgtests as superficial (GH: #2609) * d/ubuntu-advantage-tools.maintscript: - remove /etc/ubuntu-advantage/help_data.yaml * d/ubuntu-pro-client-l10n.install: - add install file for the new binary package * New upstream release 30 (LP: #2038461) - api: + add new backwards compatible plan steps to the v1 fix plan endpoints + improve information returned from the fix plan endpoints + new endpoint: u.pro.security.fix.cve.execute.v1 + new endpoint: u.pro.security.fix.usn.execute.v1 - apt: improve performance and consistency by refactoring the code to use the apt_pkg module - auto-attach: add newline to the MOTD message to separate it from other MOTD messages - contract: send information about variants to the contracts server - enable: update only service specific apt sources when enabling a service (GH: #1311) (GH: #1482) - esm: create static files to pin packages from esm-infra and esm-apps with higher priority (GH: #2580) - disable: + (experimental) add the --purge flag to the disable command, so users can remove all service related packages when disabling a service + show extra warnings when kernels are involved in the purge operation - files: Reduce race window when creating new files (LP: #2024204) - fips: add support to Jammy to prepare for when it is available - fips-preview: + add fips-preview as a new entitlement - github: add issue templates (GH: #2646) - internationalization: + add general internationalization support and templates + add initial sentence set for Brazilian Portuguese - logging: + add journald logging for the daemon and systemd timer + remove daemon and timer log files + standardize the logging calls through the codebase (GH: #2632) - systemd: change ubuntu-advantage.service type from 'notify' to 'simple', dropping the dependency on python3-systemd (LP: #2038417) (GH: #2692) - tests: + add scenarios where cloud-init is present but disabled (LP: #1938208) + change 'permission' to 'priority' when checking apt priority in tests (GH: #2719) -- Renan Rodrigo Tue, 07 Nov 2023 16:23:34 +0200 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1938208 Title: No CI testing for the case that cloud-init is installed but not in use Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Lunar: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Original description ] [ Impact ] As discovered in regression bug 1936833, current CI doesn't cover the case that the cloud-init package is installed but not in use. In general, it's acceptable for _any_ package to be installed but not in use, and behaviour should never break because of this. Perhaps this needs adding to your CI test matrix, and or the test plan in https://wiki.ubuntu.com/UbuntuAdvantageToolsUpdates adjusted to verify this. [ Test Plan ] The change is adding a test itself - running it should validate this bug. The test will be executed as part of the SRU process validation, to address https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+bug/2038461 [ Where problems could occur ] If the test would implement something wrong and make assumptions on how cloud-init works, we could be relying on something that does not match reality when checking if it does not work. Reviews in the test by cloud-init people helped us ensure this risk is
[Group.of.nepali.translators] [Bug 2024204] Re: Hardcoded path in /tmp written to by root
This bug was fixed in the package ubuntu-advantage-tools - 30~16.04 --- ubuntu-advantage-tools (30~16.04) xenial; urgency=medium * Backport new upstream release to xenial (LP: #2038461) ubuntu-advantage-tools (30) noble; urgency=medium * d/control: - add python3-apt as a build dependency - add the new ubuntu-pro-client-l10n binary package - recommend installing ubuntu-pro-client-l10n * d/po/*: - Makefile to build localization files to debian/po/usr/share/locale/ - update POTFILES.in to cover all translatable messages - remove old unused pot file - add new complete pot file for "ubuntu-pro" domain - add first Brazilian Portuguese translations * d/rules: - add step to build the translations * d/tests/control: - mark autopkgtests as superficial (GH: #2609) * d/ubuntu-advantage-tools.maintscript: - remove /etc/ubuntu-advantage/help_data.yaml * d/ubuntu-pro-client-l10n.install: - add install file for the new binary package * New upstream release 30 (LP: #2038461) - api: + add new backwards compatible plan steps to the v1 fix plan endpoints + improve information returned from the fix plan endpoints + new endpoint: u.pro.security.fix.cve.execute.v1 + new endpoint: u.pro.security.fix.usn.execute.v1 - apt: improve performance and consistency by refactoring the code to use the apt_pkg module - auto-attach: add newline to the MOTD message to separate it from other MOTD messages - contract: send information about variants to the contracts server - enable: update only service specific apt sources when enabling a service (GH: #1311) (GH: #1482) - esm: create static files to pin packages from esm-infra and esm-apps with higher priority (GH: #2580) - disable: + (experimental) add the --purge flag to the disable command, so users can remove all service related packages when disabling a service + show extra warnings when kernels are involved in the purge operation - files: Reduce race window when creating new files (LP: #2024204) - fips: add support to Jammy to prepare for when it is available - fips-preview: + add fips-preview as a new entitlement - github: add issue templates (GH: #2646) - internationalization: + add general internationalization support and templates + add initial sentence set for Brazilian Portuguese - logging: + add journald logging for the daemon and systemd timer + remove daemon and timer log files + standardize the logging calls through the codebase (GH: #2632) - systemd: change ubuntu-advantage.service type from 'notify' to 'simple', dropping the dependency on python3-systemd (LP: #2038417) (GH: #2692) - tests: + add scenarios where cloud-init is present but disabled (LP: #1938208) + change 'permission' to 'priority' when checking apt priority in tests (GH: #2719) -- Renan Rodrigo Tue, 07 Nov 2023 16:23:34 +0200 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2024204 Title: Hardcoded path in /tmp written to by root Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Lunar: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] Several race conditions were found in the u-a-t code, some where a file was being written in a hardcoded path in /tmp. This could leave way for attackers to insert malicious code in the client. [ Test Plan ] Functionality-wise, writing files is tested in the unit and integrations tests for ubuntu-advantage-tools, and should be covered in the verification of https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+bug/2038461 As for this specific bug, one can verify that the /tmp path does not exist anymore, and check the change in the code to see how the race condition was addressed. [ Where problems could occur ] The race conditions were addressed with try-except blocks in python, so it is low risk as any exploit would be against python itself. The other problematic parts of the code is removed/moved and functionality is covered by tests, so no problem there. The risk we considered is that other flaws may be present and we may have not catched those as part of the
[Group.of.nepali.translators] [Bug 2038417] Re: missing dependency on python3-systemd
This bug was fixed in the package ubuntu-advantage-tools - 30~16.04 --- ubuntu-advantage-tools (30~16.04) xenial; urgency=medium * Backport new upstream release to xenial (LP: #2038461) ubuntu-advantage-tools (30) noble; urgency=medium * d/control: - add python3-apt as a build dependency - add the new ubuntu-pro-client-l10n binary package - recommend installing ubuntu-pro-client-l10n * d/po/*: - Makefile to build localization files to debian/po/usr/share/locale/ - update POTFILES.in to cover all translatable messages - remove old unused pot file - add new complete pot file for "ubuntu-pro" domain - add first Brazilian Portuguese translations * d/rules: - add step to build the translations * d/tests/control: - mark autopkgtests as superficial (GH: #2609) * d/ubuntu-advantage-tools.maintscript: - remove /etc/ubuntu-advantage/help_data.yaml * d/ubuntu-pro-client-l10n.install: - add install file for the new binary package * New upstream release 30 (LP: #2038461) - api: + add new backwards compatible plan steps to the v1 fix plan endpoints + improve information returned from the fix plan endpoints + new endpoint: u.pro.security.fix.cve.execute.v1 + new endpoint: u.pro.security.fix.usn.execute.v1 - apt: improve performance and consistency by refactoring the code to use the apt_pkg module - auto-attach: add newline to the MOTD message to separate it from other MOTD messages - contract: send information about variants to the contracts server - enable: update only service specific apt sources when enabling a service (GH: #1311) (GH: #1482) - esm: create static files to pin packages from esm-infra and esm-apps with higher priority (GH: #2580) - disable: + (experimental) add the --purge flag to the disable command, so users can remove all service related packages when disabling a service + show extra warnings when kernels are involved in the purge operation - files: Reduce race window when creating new files (LP: #2024204) - fips: add support to Jammy to prepare for when it is available - fips-preview: + add fips-preview as a new entitlement - github: add issue templates (GH: #2646) - internationalization: + add general internationalization support and templates + add initial sentence set for Brazilian Portuguese - logging: + add journald logging for the daemon and systemd timer + remove daemon and timer log files + standardize the logging calls through the codebase (GH: #2632) - systemd: change ubuntu-advantage.service type from 'notify' to 'simple', dropping the dependency on python3-systemd (LP: #2038417) (GH: #2692) - tests: + add scenarios where cloud-init is present but disabled (LP: #1938208) + change 'permission' to 'priority' when checking apt priority in tests (GH: #2719) -- Renan Rodrigo Tue, 07 Nov 2023 16:23:34 +0200 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2038417 Title: missing dependency on python3-systemd Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Lunar: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Bug description: [ Impact ] Users running systems which don't include the python3-systemd package (like in minimal installations) will see errors when executing ubuntu-advantage.service. This happens because of a call to systemd.daemon.notify() in the python code. The solution is to remove this call and set the service type to 'simple' instead. [ Test Case ] For the SRU verification, when the package is in proposed: On an Ubuntu machine: - uninstall the python3-systemd package - try to run ubuntu-advantage.service, and see it fail - install the package from proposed - see that ubuntu-advantage.service runs fine Results from executing these steps will be added to the bug once done. Besides that, the ubuntu-advantage-tools CI includes many acceptance tests which cover possible regressions on this change - those will be executed as part of the verification of https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+bug/2038461 [ Where problems could occur ] Using type=simple for the u-a.service tells systemd
[Group.of.nepali.translators] [Bug 2038461] Re: [SRU] ubuntu-advantage-tools (29.4 -> 30) Xenial, Bionic, Focal, Jammy, Lunar, Mantic
This bug was fixed in the package ubuntu-advantage-tools - 30~16.04 --- ubuntu-advantage-tools (30~16.04) xenial; urgency=medium * Backport new upstream release to xenial (LP: #2038461) ubuntu-advantage-tools (30) noble; urgency=medium * d/control: - add python3-apt as a build dependency - add the new ubuntu-pro-client-l10n binary package - recommend installing ubuntu-pro-client-l10n * d/po/*: - Makefile to build localization files to debian/po/usr/share/locale/ - update POTFILES.in to cover all translatable messages - remove old unused pot file - add new complete pot file for "ubuntu-pro" domain - add first Brazilian Portuguese translations * d/rules: - add step to build the translations * d/tests/control: - mark autopkgtests as superficial (GH: #2609) * d/ubuntu-advantage-tools.maintscript: - remove /etc/ubuntu-advantage/help_data.yaml * d/ubuntu-pro-client-l10n.install: - add install file for the new binary package * New upstream release 30 (LP: #2038461) - api: + add new backwards compatible plan steps to the v1 fix plan endpoints + improve information returned from the fix plan endpoints + new endpoint: u.pro.security.fix.cve.execute.v1 + new endpoint: u.pro.security.fix.usn.execute.v1 - apt: improve performance and consistency by refactoring the code to use the apt_pkg module - auto-attach: add newline to the MOTD message to separate it from other MOTD messages - contract: send information about variants to the contracts server - enable: update only service specific apt sources when enabling a service (GH: #1311) (GH: #1482) - esm: create static files to pin packages from esm-infra and esm-apps with higher priority (GH: #2580) - disable: + (experimental) add the --purge flag to the disable command, so users can remove all service related packages when disabling a service + show extra warnings when kernels are involved in the purge operation - files: Reduce race window when creating new files (LP: #2024204) - fips: add support to Jammy to prepare for when it is available - fips-preview: + add fips-preview as a new entitlement - github: add issue templates (GH: #2646) - internationalization: + add general internationalization support and templates + add initial sentence set for Brazilian Portuguese - logging: + add journald logging for the daemon and systemd timer + remove daemon and timer log files + standardize the logging calls through the codebase (GH: #2632) - systemd: change ubuntu-advantage.service type from 'notify' to 'simple', dropping the dependency on python3-systemd (LP: #2038417) (GH: #2692) - tests: + add scenarios where cloud-init is present but disabled (LP: #1938208) + change 'permission' to 'priority' when checking apt priority in tests (GH: #2719) -- Renan Rodrigo Tue, 07 Nov 2023 16:23:34 +0200 ** Changed in: ubuntu-advantage-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2038461 Title: [SRU] ubuntu-advantage-tools (29.4 -> 30) Xenial, Bionic, Focal, Jammy, Lunar, Mantic Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-advantage-tools source package in Bionic: Fix Released Status in ubuntu-advantage-tools source package in Focal: Fix Released Status in ubuntu-advantage-tools source package in Jammy: Fix Released Status in ubuntu-advantage-tools source package in Lunar: Fix Released Status in ubuntu-advantage-tools source package in Mantic: Fix Released Status in ubuntu-advantage-tools source package in Noble: Fix Released Bug description: [Impact] This is for the release of the latest upstream version of the Ubuntu Pro Client, which contain new features that are desirable on all releases. 30 has several notable features: - Add internationalization support to ubuntu-advantage-tools: + now our CLI interaction can be translated, and the first pt_BR translations are started + We have a new binary shipped from the u-a-t source, to bring the translation files (ubuntu-pro-client-l10n) - Added two new api endpoints: + u.pro.security.fix.cve.execute.v1 + u.pro.security.fix.usn.execute.v1 - Improve the client performance by implementing apt operations with apt_pkg - Improve performance when enabling services by only updating the service's respective apt list - pin the esm package repositories to a higher version than the archive, so the packages would be preferred - add --purge option to the disable operation, so users can remove
[Group.of.nepali.translators] [Bug 2036195] Re: Any packages installed in binary hooks are marked as manually installed - even dependencies
This bug was fixed in the package livecd-rootfs - 2.828.3 --- livecd-rootfs (2.828.3) lunar; urgency=medium [ Heinrich Schuchardt ] * arm: fix console parameter for ARM cloud-images (LP: #2036730) livecd-rootfs (2.828.2) lunar; urgency=medium [ Steve Langasek ] * The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; the latter breaks changes to /var/lib/apt/extended_states. (LP: #2036195). livecd-rootfs (2.828.1) lunar; urgency=medium * Fix unminimize to correctly list packages. (LP: #1996489) * Install LXD snap from stable/ubuntu- channel. (LP: #2036725) -- Steve Langasek Thu, 07 Dec 2023 08:51:51 -0800 ** Changed in: livecd-rootfs (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2036195 Title: Any packages installed in binary hooks are marked as manually installed - even dependencies Status in livecd-rootfs package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in livecd-rootfs source package in Focal: Fix Committed Status in livecd-rootfs source package in Jammy: Fix Committed Status in livecd-rootfs source package in Lunar: Fix Released Bug description: After much debugging trying to understand why `apt-get autoremove` was not working in a binary hook I realised that all packages installed in a binary hook are marked as manually installed - even the dependencies of packages. This is a bug. Another side affect of this is that any dependency of a package in the base chroot that is removed in a binary hook is not autoremovable in the binary hook. It is autoremovable once the image is created and launched though. This is due to how the `setup_mountpoint` function works (see https://git.launchpad.net/livecd-rootfs/tree/live- build/functions#n123) specifically ``` mount -t tmpfs none "$mountpoint/var/lib/apt" ``` Which means that inside the chroot that the binary hook works on, the `/var/lib/apt` directory is empty... including the `/var/lib/apt/extended_states` file which is used to store whether a package was auto installed or not. The same goes the other way - any changes to the `/var/lib/apt/extended_states` file inside chroot that the binary hook is changing are not reflected in the final image due to the `teardown_mountpoint` (see https://git.launchpad.net/livecd- rootfs/tree/live-build/functions#n152) not persisting any of those changes. The end result being. * If a package is removed in the binary hook then the resulting image will likely have autoremovable packages at first launch * Any package and their dependencies installed in a binary hook will all be marked as manually installed. SRU [ Impact ] * Packages installed in a binary hook are marked as manually installed - even the dependencies of packages [ Test Plan ] * Build test images and remove a package with dependencies. * Confirm that the dependencies are marked as autoremovable. * Confirm there are packages marked as auto installed [ Where problems could occur ] * Is any dependent packages are not marked as autremovable. * If no packages are marked as auto installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2036195/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2046356] Re: Update URL for Support information in MOTD message
This bug was fixed in the package base-files - 13ubuntu6 --- base-files (13ubuntu6) noble; urgency=medium * motd/10-help-text: Update support url for new Ubuntu Pro webpage (LP: #2046356) -- Lucas Moura Tue, 02 Jan 2024 10:25:08 -0300 ** Changed in: base-files (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2046356 Title: Update URL for Support information in MOTD message Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: New Status in base-files source package in Bionic: New Status in base-files source package in Focal: New Status in base-files source package in Jammy: New Status in base-files source package in Mantic: New Status in base-files source package in Noble: Fix Released Bug description: [Impact] When users see the MOTD message, they are currently seeing an outdated url under the support information. Even though the outdated url redirects to new Ubuntu Pro webpage, we believe the users should still see the correct url from the start [Test Case] - Launch a LXD container for any of the affected releases - Install the package with this fix applied - Install `update-motd` package - Run `update-motd` and confirm the Support url is now the correct one [Regression Potential] If users are parsing MOTD for some reason, the url change might break that logic now. However, parsing MOTD messages is not a supported flow, so we believe regression potential is low here. [Discussion] Since we want users to be aware of what Ubuntu Pro is, we should highlight the right product name on any place that is still using the old "advantage" name. Updating the support URL here is a step into this direction [Original Bug Description] On the file 10-help-text, we are printing the following line on MOTD: * Support: https://ubuntu.com/advantage We should update the url to https://ubuntu.com/pro instead, as this will the default url for support information now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2041662] Re: Add/Update Ubuntu 24.04 Noble Numbat
This bug was fixed in the package distro-info - 1.5ubuntu0.23.10.1 --- distro-info (1.5ubuntu0.23.10.1) mantic; urgency=medium * Update tests for distro-info-data 0.58ubuntu0.2, which adjusted Debian 7's EoL (LP: #2041662) -- Benjamin Drung Tue, 28 Nov 2023 13:05:33 +0100 ** Changed in: distro-info (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2041662 Title: Add/Update Ubuntu 24.04 Noble Numbat Status in distro-info package in Ubuntu: Fix Released Status in distro-info-data package in Ubuntu: Fix Released Status in distro-info source package in Trusty: Invalid Status in distro-info-data source package in Trusty: New Status in distro-info source package in Xenial: Invalid Status in distro-info-data source package in Xenial: New Status in distro-info source package in Bionic: Invalid Status in distro-info-data source package in Bionic: New Status in distro-info source package in Focal: Invalid Status in distro-info-data source package in Focal: Fix Released Status in distro-info source package in Jammy: Fix Released Status in distro-info-data source package in Jammy: Fix Released Status in distro-info source package in Lunar: Fix Released Status in distro-info-data source package in Lunar: Fix Released Status in distro-info source package in Mantic: Fix Released Status in distro-info-data source package in Mantic: Fix Released Bug description: [ Impact ] Several tools rely on distro-info to tell them which releases are available. This package just contains data, with no format changes. Bug #2040193 only added the codename noble, but not the animal name. [ Regression Potential ] Minimal, if we are only adding new entries. We do this every release. [ Test Case ] "ubuntu-distro-info -df" should name the release in full: Ubuntu 23.10 "Noble Numbat" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/2041662/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2041662] Re: Add/Update Ubuntu 24.04 Noble Numbat
This bug was fixed in the package distro-info - 1.1ubuntu0.2 --- distro-info (1.1ubuntu0.2) jammy; urgency=medium * Update tests for distro-info-data 0.52ubuntu0.6, which adjusted Debian 7's EoL (LP: #2041662) -- Benjamin Drung Tue, 28 Nov 2023 13:18:32 +0100 ** Changed in: distro-info-data (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2041662 Title: Add/Update Ubuntu 24.04 Noble Numbat Status in distro-info package in Ubuntu: Fix Released Status in distro-info-data package in Ubuntu: Fix Released Status in distro-info source package in Trusty: Invalid Status in distro-info-data source package in Trusty: New Status in distro-info source package in Xenial: Invalid Status in distro-info-data source package in Xenial: New Status in distro-info source package in Bionic: Invalid Status in distro-info-data source package in Bionic: New Status in distro-info source package in Focal: Invalid Status in distro-info-data source package in Focal: Fix Released Status in distro-info source package in Jammy: Fix Released Status in distro-info-data source package in Jammy: Fix Released Status in distro-info source package in Lunar: Fix Released Status in distro-info-data source package in Lunar: Fix Released Status in distro-info source package in Mantic: Fix Committed Status in distro-info-data source package in Mantic: Fix Released Bug description: [ Impact ] Several tools rely on distro-info to tell them which releases are available. This package just contains data, with no format changes. Bug #2040193 only added the codename noble, but not the animal name. [ Regression Potential ] Minimal, if we are only adding new entries. We do this every release. [ Test Case ] "ubuntu-distro-info -df" should name the release in full: Ubuntu 23.10 "Noble Numbat" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/2041662/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2041662] Re: Add/Update Ubuntu 24.04 Noble Numbat
This bug was fixed in the package distro-info-data - 0.43ubuntu1.15 --- distro-info-data (0.43ubuntu1.15) focal; urgency=medium * Add animal name to Ubuntu 24.04 LTS Noble Numbat (LP: #2041662) * Clean .pyc files and mypy cache * Correct Ubuntu 6.10 EOL date to 2008-04-25 * Correct Ubuntu 16.04 ESM begin to 2021-04-30 * Move Ubuntu 12.04 ESM end date back to Friday, 2019-04-26 * Correct Debian 3.1 EOL date to 2008-03-31 * Correct Debian 7 EOL date to 2016-04-25 * Move Debian 9 EOL to the 9.13 release date 2020-07-18 * Move Debian 10 EOL to the 10.13 release date 2022-09-10 -- Benjamin Drung Thu, 16 Nov 2023 19:53:11 +0100 ** Changed in: distro-info-data (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2041662 Title: Add/Update Ubuntu 24.04 Noble Numbat Status in distro-info package in Ubuntu: Fix Released Status in distro-info-data package in Ubuntu: Fix Released Status in distro-info source package in Trusty: Invalid Status in distro-info-data source package in Trusty: New Status in distro-info source package in Xenial: Invalid Status in distro-info-data source package in Xenial: New Status in distro-info source package in Bionic: Invalid Status in distro-info-data source package in Bionic: New Status in distro-info source package in Focal: Invalid Status in distro-info-data source package in Focal: Fix Released Status in distro-info source package in Jammy: Fix Released Status in distro-info-data source package in Jammy: Fix Released Status in distro-info source package in Lunar: Fix Released Status in distro-info-data source package in Lunar: Fix Released Status in distro-info source package in Mantic: Fix Committed Status in distro-info-data source package in Mantic: Fix Released Bug description: [ Impact ] Several tools rely on distro-info to tell them which releases are available. This package just contains data, with no format changes. Bug #2040193 only added the codename noble, but not the animal name. [ Regression Potential ] Minimal, if we are only adding new entries. We do this every release. [ Test Case ] "ubuntu-distro-info -df" should name the release in full: Ubuntu 23.10 "Noble Numbat" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/2041662/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2041662] Re: Add/Update Ubuntu 24.04 Noble Numbat
This bug was fixed in the package distro-info - 1.5ubuntu0.23.04.1 --- distro-info (1.5ubuntu0.23.04.1) lunar; urgency=medium * Update tests for distro-info-data 0.57ubuntu0.3, which adjusted Debian 7's EoL (LP: #2041662) -- Benjamin Drung Tue, 28 Nov 2023 13:15:14 +0100 ** Changed in: distro-info-data (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2041662 Title: Add/Update Ubuntu 24.04 Noble Numbat Status in distro-info package in Ubuntu: Fix Released Status in distro-info-data package in Ubuntu: Fix Released Status in distro-info source package in Trusty: Invalid Status in distro-info-data source package in Trusty: New Status in distro-info source package in Xenial: Invalid Status in distro-info-data source package in Xenial: New Status in distro-info source package in Bionic: Invalid Status in distro-info-data source package in Bionic: New Status in distro-info source package in Focal: Invalid Status in distro-info-data source package in Focal: Fix Released Status in distro-info source package in Jammy: Fix Released Status in distro-info-data source package in Jammy: Fix Released Status in distro-info source package in Lunar: Fix Released Status in distro-info-data source package in Lunar: Fix Released Status in distro-info source package in Mantic: Fix Committed Status in distro-info-data source package in Mantic: Fix Released Bug description: [ Impact ] Several tools rely on distro-info to tell them which releases are available. This package just contains data, with no format changes. Bug #2040193 only added the codename noble, but not the animal name. [ Regression Potential ] Minimal, if we are only adding new entries. We do this every release. [ Test Case ] "ubuntu-distro-info -df" should name the release in full: Ubuntu 23.10 "Noble Numbat" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/2041662/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2041662] Re: Add/Update Ubuntu 24.04 Noble Numbat
This bug was fixed in the package distro-info-data - 0.57ubuntu0.3 --- distro-info-data (0.57ubuntu0.3) lunar; urgency=medium * Add animal name to Ubuntu 24.04 LTS Noble Numbat (LP: #2041662) * Clean .pyc files and mypy cache * Correct Ubuntu 6.10 EOL date to 2008-04-25 * Correct Ubuntu 16.04 ESM begin to 2021-04-30 * Move Ubuntu 12.04 ESM end date back to Friday, 2019-04-26 * Correct Debian 3.1 EOL date to 2008-03-31 * Correct Debian 7 EOL date to 2016-04-25 * Move Debian 9 EOL to the 9.13 release date 2020-07-18 * Move Debian 10 EOL to the 10.13 release date 2022-09-10 -- Benjamin Drung Thu, 16 Nov 2023 19:35:28 +0100 ** Changed in: distro-info (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2041662 Title: Add/Update Ubuntu 24.04 Noble Numbat Status in distro-info package in Ubuntu: Fix Released Status in distro-info-data package in Ubuntu: Fix Released Status in distro-info source package in Trusty: Invalid Status in distro-info-data source package in Trusty: New Status in distro-info source package in Xenial: Invalid Status in distro-info-data source package in Xenial: New Status in distro-info source package in Bionic: Invalid Status in distro-info-data source package in Bionic: New Status in distro-info source package in Focal: Invalid Status in distro-info-data source package in Focal: Fix Released Status in distro-info source package in Jammy: Fix Released Status in distro-info-data source package in Jammy: Fix Released Status in distro-info source package in Lunar: Fix Released Status in distro-info-data source package in Lunar: Fix Released Status in distro-info source package in Mantic: Fix Committed Status in distro-info-data source package in Mantic: Fix Released Bug description: [ Impact ] Several tools rely on distro-info to tell them which releases are available. This package just contains data, with no format changes. Bug #2040193 only added the codename noble, but not the animal name. [ Regression Potential ] Minimal, if we are only adding new entries. We do this every release. [ Test Case ] "ubuntu-distro-info -df" should name the release in full: Ubuntu 23.10 "Noble Numbat" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/2041662/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2041662] Re: Add/Update Ubuntu 24.04 Noble Numbat
This bug was fixed in the package distro-info-data - 0.58ubuntu0.2 --- distro-info-data (0.58ubuntu0.2) mantic; urgency=medium * Add animal name to Ubuntu 24.04 LTS Noble Numbat (LP: #2041662) * Clean .pyc files and mypy cache * Correct Ubuntu 6.10 EOL date to 2008-04-25 * Correct Ubuntu 16.04 ESM begin to 2021-04-30 * Move Ubuntu 12.04 ESM end date back to Friday, 2019-04-26 * Correct Debian 3.1 EOL date to 2008-03-31 * Correct Debian 7 EOL date to 2016-04-25 * Move Debian 9 EOL to the 9.13 release date 2020-07-18 * Move Debian 10 EOL to the 10.13 release date 2022-09-10 -- Benjamin Drung Thu, 16 Nov 2023 19:27:44 +0100 ** Changed in: distro-info-data (Ubuntu Mantic) Status: Fix Committed => Fix Released ** Changed in: distro-info (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2041662 Title: Add/Update Ubuntu 24.04 Noble Numbat Status in distro-info package in Ubuntu: Fix Released Status in distro-info-data package in Ubuntu: Fix Released Status in distro-info source package in Trusty: Invalid Status in distro-info-data source package in Trusty: New Status in distro-info source package in Xenial: Invalid Status in distro-info-data source package in Xenial: New Status in distro-info source package in Bionic: Invalid Status in distro-info-data source package in Bionic: New Status in distro-info source package in Focal: Invalid Status in distro-info-data source package in Focal: Fix Released Status in distro-info source package in Jammy: Fix Released Status in distro-info-data source package in Jammy: Fix Released Status in distro-info source package in Lunar: Fix Released Status in distro-info-data source package in Lunar: Fix Released Status in distro-info source package in Mantic: Fix Committed Status in distro-info-data source package in Mantic: Fix Released Bug description: [ Impact ] Several tools rely on distro-info to tell them which releases are available. This package just contains data, with no format changes. Bug #2040193 only added the codename noble, but not the animal name. [ Regression Potential ] Minimal, if we are only adding new entries. We do this every release. [ Test Case ] "ubuntu-distro-info -df" should name the release in full: Ubuntu 23.10 "Noble Numbat" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/distro-info/+bug/2041662/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1990450] Re: Show potential Ubuntu Pro updates and apt news messages
This bug was fixed in the package update-manager - 1:20.04.10.18 --- update-manager (1:20.04.10.18) focal; urgency=medium * Fix incorrect available version for Ubuntu Pro updates in unattached case (LP: #2043425). update-manager (1:20.04.10.17) focal; urgency=medium * Ubuntu Pro (LP: #1990450): - fix another linter error which was created while fixing a missing space in the previous upload... update-manager (1:20.04.10.16) focal; urgency=medium * Ubuntu Pro (LP: #1990450): - Address linter errors that cause autopkgtest to fail. update-manager (1:20.04.10.15) focal; urgency=medium * Ubuntu Pro (LP: #1990450): - Show Ubuntu Pro packages, whether the system is attached to Ubuntu Pro or not. - Replace Install now button by Enable Ubuntu Pro button when only Ubuntu Pro packages are available and the machine is not attached. - Fix checkbox and expander widget from overlapping. - Add News pane in a expander. - Replace notebook with Description and Changes tabs by a pane. update-manager (1:20.04.10.14) focal; urgency=medium * Fix Ubuntu Pro updates checkbox and expander widget from overlapping (LP: #1990450) update-manager (1:20.04.10.13) focal; urgency=medium * Update of the parsing for pro client changes (lp: #1990450) update-manager (1:20.04.10.12) focal; urgency=medium * Show pending Ubuntu pro packages (LP: #1990450) -- Nathan Pratta Teodosio Wed, 15 Nov 2023 11:28:54 +0100 ** Changed in: update-manager (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1990450 Title: Show potential Ubuntu Pro updates and apt news messages Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Committed Status in update-manager source package in Bionic: Fix Committed Status in update-manager source package in Focal: Fix Released Status in update-manager source package in Jammy: Fix Released Status in update-manager source package in Kinetic: Fix Released Status in update-manager source package in Lunar: Won't Fix Status in update-manager source package in Mantic: Won't Fix Status in update-manager source package in Noble: Fix Released Bug description: [Impact] Show the Ubuntu Pro (aka Ubuntu Advantage) updates that would be enabled if you attached this machine. This information is not currently shown. The new revision also update the reference to the Software Properties' Livepatch tab which doesn't exist anymore since bug #2003527 and was replaced by Ubuntu Pro. There is also a new section 'News' showing the apt-news messages if there are any available and some layout changes to accommodate for the new section [Test Case] 1. Do fresh install of Ubuntu with available updates 2. Check there are updates available by running: $ pro security-status Note that updates are only available for older LTS releases. If there are no Pro specific updates available, install any package listed in https://esm.ubuntu.com/apps/ubuntu/dists/jammy-apps-security/main/binary-amd64/Packages (without attaching your machine!) 3. Open update-manager -> There should be a 'Ubuntu Pro security updates (Enable in Settings...)' section at the bottom of the updates list showing disabled and including under it the name of the packages that would be available if pro was enabled 4. start software-properties, go to the ubuntu pro tab and attach to a pro account 5. close software-properties and restart update-manager -> There should be a 'Ubuntu Pro security updates' section at the bottom of the updates list showing enabled and including under it packages updated provided by pro that can be installed 6. Check the top of the update-manager dialog If there is a message available on the server $ curl https://motd.ubuntu.com/aptnews.json with a timestamp older than one month then a 'news' section should be displayed including the message if there isn't a recent post on the server it can be tested locally with the steps from #31 [Regression Potential] Possibility of introducing new bugs. The new livepatch->ubuntu pro string change will not be translated until the next language pack refresh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1990450/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 2043425] Re: Details pane against unavailable Pro updates is misleading
This bug was fixed in the package update-manager - 1:20.04.10.18 --- update-manager (1:20.04.10.18) focal; urgency=medium * Fix incorrect available version for Ubuntu Pro updates in unattached case (LP: #2043425). update-manager (1:20.04.10.17) focal; urgency=medium * Ubuntu Pro (LP: #1990450): - fix another linter error which was created while fixing a missing space in the previous upload... update-manager (1:20.04.10.16) focal; urgency=medium * Ubuntu Pro (LP: #1990450): - Address linter errors that cause autopkgtest to fail. update-manager (1:20.04.10.15) focal; urgency=medium * Ubuntu Pro (LP: #1990450): - Show Ubuntu Pro packages, whether the system is attached to Ubuntu Pro or not. - Replace Install now button by Enable Ubuntu Pro button when only Ubuntu Pro packages are available and the machine is not attached. - Fix checkbox and expander widget from overlapping. - Add News pane in a expander. - Replace notebook with Description and Changes tabs by a pane. update-manager (1:20.04.10.14) focal; urgency=medium * Fix Ubuntu Pro updates checkbox and expander widget from overlapping (LP: #1990450) update-manager (1:20.04.10.13) focal; urgency=medium * Update of the parsing for pro client changes (lp: #1990450) update-manager (1:20.04.10.12) focal; urgency=medium * Show pending Ubuntu pro packages (LP: #1990450) -- Nathan Pratta Teodosio Wed, 15 Nov 2023 11:28:54 +0100 ** Changed in: update-manager (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/2043425 Title: Details pane against unavailable Pro updates is misleading Status in update-manager package in Ubuntu: Fix Released Status in update-manager source package in Xenial: Fix Committed Status in update-manager source package in Bionic: Fix Committed Status in update-manager source package in Focal: Fix Released Status in update-manager source package in Jammy: Fix Released Status in update-manager source package in Noble: Fix Released Bug description: * Impact If Pro is not enabled, then the details pane against a Pro update misleads the user into believing that there is no update available. Example of someone being misled: https://inteltechniques.com/blog/2023/11/12/ubuntu-pro-shenanigans/ Expected results: either no details presented, or the actual details of the potential Pro update presented Actual results: a message that implies that there is no update available for this package, Pro or not. * Test Case Install the update on a system not attached to Pro, select an update in the Pro section, check the 'Version available' string, it should reflect the version that would be installed if pro was enabled * Regression potential The change is in the code getting the available version to display, if the logic was wrong it could lead to have the 'available version' label being missing or incorrect. The code could hit an exception if there was not non expected value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/2043425/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
