** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1990586
Title:
22.04: python3* mismatched phasing breaks dist-upgrades
Status in apt package
This bug was fixed in the package apt - 2.4.8
---
apt (2.4.8) jammy; urgency=medium
* edsp: Add support for phased updates (test in LP#1990586)
* Check state of dependency, not dependee in dependency keep back
(LP: #1990684)
* full-upgrade: Mark phased upgrades for keep befo
This bug was fixed in the package apt - 2.5.3
---
apt (2.5.3) unstable; urgency=medium
[ Povilas Kanapickas ]
* doc: Explain that apt-get download ensures package authenticity
[ David Kalnischkies ]
* Keep color disabled if APT::Color was set to false
* Don't reuse filename
Sure my concern was the SRUs coming while apt is still phasing and
creating another issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1990586
Title:
22.04: python3* mismat
@Brian Phasing apt is not an issue, it's only when multiple SRUs depend
on each other that the issues being fixed here actually happen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/
When releasing this to -updates it seems to me like we should fully
phase the update rather than having it phase and risking more issues.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.ne
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1990586
Title:
22.04: python3* mismatched phasing breaks dist-upgrades
Status in apt package i
Tests have passed successfully for 2.4.8 on all architectures (except
i386, which is expected):
(276/290) Testcase test-ubuntu-bug-1990586: W: Ignoring failure of dpkg
--add-architecture as it is likely due to pkg-config-dpkghook (see #824774)
P P
** Tags removed: verification-needed verifica
In terms of risk, touching apt is always going to be high risk because
users need apt to revert or upgrade away from any regression. QA is
therefore essential. Normally I'd like this to "bake" in the development
release first, but given the nature of the bug, that's probably not
going to give us an
** Description changed:
Impact
--
Users who manually run sudo apt dist-upgrade without paying attention can
remove essential parts of their system
- Test Case
+ Test Plan
-
+ autopkgtests run the integration test suite. We have added a simplified
version of the EDSP file a
** Tags added: foundtations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1990586
Title:
22.04: python3* mismatched phasing breaks dist-upgrades
Status in apt package i
I have the fix ready in https://salsa.debian.org/apt-
team/apt/-/merge_requests/262, as well as adding support for phased
updates to EDSP, I'm just working on adding test cases (basically
minimizing the EDSP and dumping it in the dir tbh).
** Changed in: apt (Ubuntu)
Status: Incomplete => I
** Attachment added: "lp1990586.edsp"
https://bugs.launchpad.net/ubuntu/+source/python3.10/+bug/1990586/+attachment/5618167/+files/lp1990586.edsp
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.
I attached the edsp file. Hope it helps.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1990586
Title:
22.04: python3* mismatched phasing breaks dist-upgrades
Status in apt p
python3{.10,-defaults,-stdlib-extensions} have all had their phasing set
to 100% now to avoid this issue.
** Changed in: python3-defaults (Ubuntu)
Status: Triaged => Fix Released
** Changed in: python3-stdlib-extensions (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: pytho
I've been thinking about both some more and I believe we can fix this
more easily than I thought earlier, but I'd still like the data to be
able to reproduce this.
Because obviously no such issues occured during testing.
In the meantime could SRU team please pull the python3.10 update, or
phase i
Same issue as [Bug 1990525] [NEW] E: Internal Error, AutoRemover broke
stuff. See the comment there.
** Changed in: apt (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubun
** Description changed:
Impact
--
Users who manually run sudo apt dist-upgrade without paying attention can
remove essential parts of their system
Test Case
-
This test case won't work as well if phasing is set to 0% or 100%
- Set /etc/machine-id to 2c030cfce3b4487f9
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1990586
Title:
22.04: python3* mismatched phasing breaks dist-upgrades
Status in apt package in
19 matches
Mail list logo